blob: fca6760435592000c78389166110a515e1deef45 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] network interface renaming not working anymore
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20network%20interface%20renaming%20not%20working%20anymore&In-Reply-To=%3Calpine.LMD.2.02.1208162242170.8379%40zem.cjw.nep%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="018205.html">
<LINK REL="Next" HREF="018207.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] network interface renaming not working anymore</H1>
<B>Christiaan Welvaart</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20network%20interface%20renaming%20not%20working%20anymore&In-Reply-To=%3Calpine.LMD.2.02.1208162242170.8379%40zem.cjw.nep%3E"
TITLE="[Mageia-dev] network interface renaming not working anymore">cjw at daneel.dyndns.org
</A><BR>
<I>Thu Aug 16 22:55:19 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018205.html">[Mageia-dev] network interface renaming not working anymore
</A></li>
<LI>Next message: <A HREF="018207.html">[Mageia-dev] [changelog] [RPM] cauldron nonfree/release kmod-nvidia-current-295.71-2.mga3.nonfree
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18206">[ date ]</a>
<a href="thread.html#18206">[ thread ]</a>
<a href="subject.html#18206">[ subject ]</a>
<a href="author.html#18206">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Thu, 16 Aug 2012, Colin Guthrie wrote:
><i> 'Twas brillig, and Christiaan Welvaart at 16/08/12 20:30 did gyre and
</I>><i> gimble:
</I>>><i> hi,
</I>>><i>
</I>>><i> When I finally rebooted a cauldron system that acts as a router, it
</I>>><i> turned out the network interfaces eth0 and eth1 were switched, exposing
</I>>><i> "internal" services to the outside world and leaving me without internet
</I>>><i> access. Syslog contains:
</I>>><i> Aug 15 22:48:29 zem systemd-udevd[404]: error changing net interface
</I>>><i> name eth0 to eth1: File exists
</I>>><i> Aug 15 22:48:29 zem systemd-udevd[404]: error changing net interface
</I>>><i> name eth1 to eth0: File exists
</I>>><i>
</I>>><i> Of course this has worked for years, so it breaking is not something
</I>>><i> anyone would expect. It also seems to be unneeded. After some looking
</I>>><i> around I could (temporarily) fix it quite easily by adding:
</I>>><i> ifrename -i eth0 -n rename0
</I>>><i> ifrename -i eth1 -n rename1
</I>>><i> ifrename -i rename0
</I>>><i> ifrename -i rename1
</I>>><i> to /etc/init.d/network and describing the mapping in /etc/iftab . So now
</I>>><i> I have two questions:
</I>>><i> - Has anyone else seen this?
</I>>><i> - What change is causing this: kernel, udev/systemd, or something else?
</I>>><i>
</I>>><i> The network devices use the same driver so there is no other way to
</I>>><i> distinguish them than by MAC address or PCI ID.
</I>><i>
</I>><i> Yeah this is no longer supported upstream as it was apparently very
</I>><i> hacky. Last time I asked Kay about it, there was something else to
</I>><i> replace it but I've not followed up what that is recently. I'll ask him
</I>><i> again next time we're chatting.
</I>
So it's udev (I tried to install an old udev but that didn't work). Commit
looks to be:
<A HREF="http://cgit.freedesktop.org/systemd/systemd/commit/src/udev?id=97595710b77aa162ca5e20da57d0a1ed7355eaad">http://cgit.freedesktop.org/systemd/systemd/commit/src/udev?id=97595710b77aa162ca5e20da57d0a1ed7355eaad</A>
Waiting 90s hoping the interface name becomes available is no fun of
course but in fact this works fine when the user configured it properly:
it did exactly what I now use as workaround only without global control.
So we could simply revert it but I wonder why this change was considered
necessary. So far I have not found any discussion about it.
Christiaan
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018205.html">[Mageia-dev] network interface renaming not working anymore
</A></li>
<LI>Next message: <A HREF="018207.html">[Mageia-dev] [changelog] [RPM] cauldron nonfree/release kmod-nvidia-current-295.71-2.mga3.nonfree
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18206">[ date ]</a>
<a href="thread.html#18206">[ thread ]</a>
<a href="subject.html#18206">[ subject ]</a>
<a href="author.html#18206">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
