network-manager doesn't work with renamed eth devices
Bug #35726 reported by
Bas Zoetekouw
This bug report is a duplicate of:
Bug #32213: Doesn't handle devices with unusual names.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
network-manager doesn't seem to work correctly with renamed eth devices.
To distingish more easily between lan and wlan device, my eth devices were renamed using udev like this:
KERNEL=="eth*", SYSFS{device}
KERNEL=="eth*", SYSFS{device}
However, this caused network-manager not to recognize them: the nm-applet simply said that there were no network connections available. I had to reset the names to the original eth0/eth1 to get network-manager to work.
I've been looking through the network-manager souce to see if it maybe filters on ethN or so, but I haven't been able to find anything.
(this is on Dapper btw, using network-manager 0.5.1-0ubuntu19 and dbus 0.60-6ubuntu4).
Revision history for this message
| Lionel Dricot (ploum-deactivatedaccount) wrote | #1 |
| Changed in network-manager: | |
| status: | Unconfirmed → Needs Info |
Revision history for this message
| Bas Zoetekouw (baszoetekouw) wrote | #2 |
Download full text (4.5 KiB)
| Changed in network-manager: | |
| status: | Needs Info → Unconfirmed |
| Changed in network-manager: | |
| status: | Unconfirmed → Confirmed |
To post a comment you must log in.
Could you please test with the last version :
https:/
Please follow instructions (nothing in /etc/network/
Thank you :-)