Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34389 - [netcfg, udev] renaming of multiple interfaces: several race conditions
Attached to Project:
Arch Linux
Opened by Alexandre Kandalintsev (exe2) - Wednesday, 20 March 2013, 20:59 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 17 April 2013, 19:57 GMT
Opened by Alexandre Kandalintsev (exe2) - Wednesday, 20 March 2013, 20:59 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 17 April 2013, 19:57 GMT
|
DetailsDescription:
I'm using arch linux AMD64 with all updates in virtual machine with two interfaces. And here is what I have: 1) netcfg[179]: :: ext up Interface ext does not exist 2) error changing net interface name eth0 to ext: Device or resource busy Here is some pieces of log (the complete log is attached): Mar 20 20:44:53 b00 ifplugd[182]: Using interface eth0 with driver <e1000> (version: 7.3.21-k8-NAPI) Mar 20 20:44:53 b00 ifplugd[182]: Using detection mode: SIOCETHTOOL Mar 20 20:44:53 b00 ifplugd[182]: Initialization complete, link beat not detected. ... Mar 20 20:44:53 b00 kernel: e1000 0000:00:03.0 eth0: (PCI:33MHz:32-bit) 52:54:16:12:34:66 Mar 20 20:44:53 b00 kernel: e1000 0000:00:03.0 eth0: Intel(R) PRO/1000 Network Connection Mar 20 20:44:53 b00 kernel: input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3 Mar 20 20:44:53 b00 kernel: piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb100, revision 0 Mar 20 20:44:53 b00 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready ... Mar 20 20:44:53 b00 netcfg[179]: :: ext up Interface ext does not exist Mar 20 20:44:53 b00 netcfg[179]: [fail] ... Mar 20 20:44:53 b00 kernel: e1000 0000:00:04.0 eth1: (PCI:33MHz:32-bit) 52:54:16:18:b9:e7 Mar 20 20:44:53 b00 kernel: e1000 0000:00:04.0 eth1: Intel(R) PRO/1000 Network Connection Mar 20 20:44:53 b00 systemd-udevd[116]: error changing net interface name eth0 to ext: Device or resource busy Mar 20 20:44:53 b00 systemd-udevd[117]: renamed network interface eth1 to int Mar 20 20:44:54 b00 ifplugd[182]: Link beat detected. Mar 20 20:44:55 b00 kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Mar 20 20:44:55 b00 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Mar 20 20:44:55 b00 ifplugd[182]: Executing '/etc/ifplugd/netcfg.action eth0 up'. Mar 20 20:44:55 b00 ifplugd[182]: client: up Additional info: * package version(s) systemd 198-1 ifplugd 0.28-13 netcfg 3.0-1 linux 3.8.3-2 * config and/or log files etc. # cat /etc/udev/rules.d/70-persistent-net.rules: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:16:12:34:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="ext" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:16:18:b9:e7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="int" Steps to reproduce: Give a virtual machine two interfaces, assign them new names and try to get this working. 
boot_log
(34.3 KiB)
|
This task depends upon
Closed by Tom Gundersen (tomegun)
Wednesday, 17 April 2013, 19:57 GMT
Reason for closing: None
Additional comments about closing: netcfg is gone, appears to work with netctl
Wednesday, 17 April 2013, 19:57 GMT
Reason for closing: None
Additional comments about closing: netcfg is gone, appears to work with netctl
/etc/udev/rules.d/*network*
Because this is a horrible idea. The interface names should be meaningful. When you have just one interface it doesn't matter how it is called. But if you have more than one interface it's better to assign the names wisely. In other words, I had hard-to-track troubles several times when I confused internal and external NICs in bridge and iptables.
An alternative would be to use networkmanager, which does this correctly afaik.
Tried to add to autostart (this seems is not documented):
~~~
# systemctl enable netctl@ext
The unit files have no [Install] section.
~~~
I added "WantedBy=multi-user.target" in [Install] to /usr/lib/systemd/system/netctl@.service. Unfortunately I've got the same problem:
Mar 27 12:58:01 b00 network[177]: Starting network profile 'ext'...
Mar 27 12:58:01 b00 network[177]: Interface 'ext' does not exist
Mar 27 12:58:01 b00 network[177]: Failed to bring the network up for profil...t'
[root@b00 ~]#
Seems the same problem
If you need to mess with the code, you're probably doing something wrong.