199512 2007-11-18 11:54 0000 No need for udev to rename interface with net-wireless/iwlwifi-1.1.21 2008-02-10 12:59:27 0000 1 1 1 Unclassified Gentoo Linux Ebuilds unspecified AMD64 Linux RESOLVED FIXED P2 normal --- 1 arturogarcia@onetel.com compnerd@gentoo.org jakub@gentoo.org pacho@condmat1.ciencias.uniovi.es arturogarcia@onetel.com 2007-11-18 11:54:35 0000 /etc/udev/rules.d/70-persistent-net.rules shipped with udev-115-r1 is doing the following: # PCI device 0x8086:0x4222 (ipw3945) SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:22:b5:d3", NAME="eth1" There is no need to do this anymore as iwlwifi-1.1.21 provides a proper named interface calles wlan0. In fact, the rename is not working properly and renames wmaster0. The ebuild needs to either communicate the user, or make a RDEPEND on a newer fixed version of udev. Reproducible: Always Steps to Reproduce: 1. Make sure you are running sys-fs/udev-115-r1 (stable on amd64) 2. USE="ipw3945" emerge iwlwifi 3. modprobe iwl3945 Actual Results: Your interface eth1 has no wireless extensions, and this is the one you need to configure. eth1 is in fact low-level wmaster0. Expected Results: Your interface should have wireless extensions. iwlwifi provides now wlan0 and there is no need to make the rename. jakub@gentoo.org 2007-11-18 11:59:53 0000 That rule is generated, not shipped w/ udev or iwlwifi. If you don't want that any more, then delete the rule from the file. What exactly are you requesting here? iwlwifi shouldn't create the bogus wmaster0 device in the first place. arturogarcia@onetel.com 2007-11-18 12:06:16 0000 I was just replying now... see below... Sorry guys, I'm talking crap. The problem was when upgrading straight from ipw3945 to iwlwifi via rmmod ipw3945/modprobe iwl3945. The persistent rules made the rename confused. If you delete the rules and do the process all over again it works as expected... Shall the ebuild make sure/communicate this to the user??? I leave to you to reject or leave as new... compnerd@gentoo.org 2007-11-22 21:05:04 0000 Added an elog message. jakub@gentoo.org 2008-02-10 12:59:27 0000 *** Bug 209513 has been marked as a duplicate of this bug. ***