I am just wondering what is going on with all this device names renaming. hostap always used to use wlanX device names.. but well in F8 this is some kind of different - at least on SMP system, the kernel asks for device wlan0 to be renamed to eth1. I thought it is udev magic, so I played with 70-persistent-net.rules, but it has no efect. Then I tried the udevmonitor and I see: UEVENT[1203878535.039740] add /module/hostap (module) UDEV [1203878535.042915] add /module/hostap (module) UEVENT[1203878535.057209] add /module/hostap_pci (module) UEVENT[1203878535.057845] add /bus/pci/drivers/hostap_pci (drivers) UEVENT[1203878535.058343] add /class/net/wifi1 (net) UDEV [1203878535.066578] add /bus/pci/drivers/hostap_pci (drivers) UDEV [1203878535.069191] add /module/hostap_pci (module) UDEV [1203878535.212557] add /class/net/wifi1 (net) UEVENT[1203878535.269178] add /class/net/wlan0 (net) UEVENT[1203878535.278823] move /class/net/eth1 (net) UDEV [1203878539.946245] add /class/net/eth1 (net) UDEV [1203878539.994233] move /class/net/eth1 (net) So this has nothing to do with udev, it''s kernel who is asking for device to be renamed. But why? Some details: http://forums.fedoraforum.org/showthread.php?p=968699 Adam Pribyl
On Wed, Feb 27, 2008 at 11:18:17AM +0100, Adam Pribyl wrote:> I am just wondering what is going on with all this device names renaming. > > hostap always used to use wlanX device names.. but well in F8 this is some > kind of different - at least on SMP system, the kernel asks for device > wlan0 to be renamed to eth1. I thought it is udev magic, so I played with > 70-persistent-net.rules, but it has no efect. Then I tried the udevmonitor > and I see: > > UEVENT[1203878535.039740] add /module/hostap (module) > UDEV [1203878535.042915] add /module/hostap (module) > UEVENT[1203878535.057209] add /module/hostap_pci (module) > UEVENT[1203878535.057845] add /bus/pci/drivers/hostap_pci (drivers) > UEVENT[1203878535.058343] add /class/net/wifi1 (net) > UDEV [1203878535.066578] add /bus/pci/drivers/hostap_pci (drivers) > UDEV [1203878535.069191] add /module/hostap_pci (module) > UDEV [1203878535.212557] add /class/net/wifi1 (net) > UEVENT[1203878535.269178] add /class/net/wlan0 (net) > UEVENT[1203878535.278823] move /class/net/eth1 (net) > UDEV [1203878539.946245] add /class/net/eth1 (net) > UDEV [1203878539.994233] move /class/net/eth1 (net) > > So this has nothing to do with udev, it''s kernel who is asking for device > to be renamed. But why? > > Some details: http://forums.fedoraforum.org/showthread.php?p=968699In that thread you indicated that you had previously used orinoco, which would have given you an ethX name for that same MAC address. So somewhere that association has stuck. Perhaps you are using an HWADDR line in /etc/sysconfig/network-scripts/ifcfg-eth1? John -- John W. Linville linville@redhat.com
On Wed, 2008-02-27 at 09:36 -0500, John W. Linville wrote:> In that thread you indicated that you had previously used orinoco, > which would have given you an ethX name for that same MAC address. > So somewhere that association has stuck. Perhaps you are using an > HWADDR line in /etc/sysconfig/network-scripts/ifcfg-eth1?It could also be the /etc/udev/rules.d/70-persistent-net.rules file. This bit me recently when I couldn''t tell for the life of me why interfaces constantly showed up as eth1 or eth2 instead of eth0 no matter how hard I tried. Editing the ifcfg-ethX files didn''t matter since udev was whacking it first. Nuke 70-persistent-net.rules (it will be recreated so don''t lose any sleep) and you may be in business. -- David Hollis <dhollis@davehollis.com>
On Wed, 27 Feb 2008, John W. Linville wrote:>> Some details: http://forums.fedoraforum.org/showthread.php?p=968699 > > In that thread you indicated that you had previously used orinoco, > which would have given you an ethX name for that same MAC address. > So somewhere that association has stuck. Perhaps you are using an > HWADDR line in /etc/sysconfig/network-scripts/ifcfg-eth1?This seems to be the trick. I have both ifcfg-wlan0 and ifcfg-eth1 with same HWADDR. I played with both persistant-net.rules and ifcfg-* but probably never got the right combinatin. I hope it will now really persist during reboots, because that was somehow not that persistent - when I removed persisten-net.rules but had correct ifcfg-wlan0 on next reboot the device was again eth1 and persistent-net-generator created again the rule with eth1 rename and the interface was not configured. This time I left persistent-net.rules where I changed eth1 to wlan0 and removed ifcfg-eth1. Thanks for the answers.> John > -- > John W. Linville > linville@redhat.comAdam Pribyl