#5746 HIGH Retriag: msh0 interface with a bogus name (msh0_rename)
Zarro Boogs per Child
bugtracker at laptop.org
Thu Jan 10 15:13:30 EST 2008
#5746: msh0 interface with a bogus name (msh0_rename)
----------------------+-----------------------------------------------------
Reporter: carrano | Owner: dwmw2
Type: defect | Status: new
Priority: high | Milestone: Retriage, Please!
Component: distro | Version:
Resolution: | Keywords: review?
Verified: 0 | Blocking:
Blockedby: |
----------------------+-----------------------------------------------------
Changes (by dsd):
* keywords: => review?
* milestone: Future Release => Retriage, Please!
Comment:
The problem is that the newer udev contains some new rules for persistent
interface naming based on MAC address, and tries to rename all network
interfaces.
udev generates the following rule for the XO:
{{{SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:17:c4:05:26:1f", ATTR{type}=="1", NAME="eth0"}}}
This functionality does not play too nicely with our case, where we have 2
interfaces with the same MAC address.
As per the above rule, udev tries to rename both eth0 and msh0 to "eth0".
Only one can win, obviously. msh0 fails to be renamed. I'm not sure why
udev adds the _rename prefix before the final rename, but presumably there
is a reason.
The presence of msh0_rename rather than msh0 is breaking NetworkManager,
see ticket #5931.
I suggest adding a simple udev rule to disable network interface renaming.
--
Ticket URL: <http://dev.laptop.org/ticket/5746#comment:3>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list