#1842: DRIVER=="*?" in network udev rules breaks for some cards --------------------------------------------+------------------------------- Reporter: [EMAIL PROTECTED] | Owner: [email protected] Type: task | Status: new Priority: high | Milestone: 6.2 Component: Book | Version: SVN Severity: major | Resolution: Keywords: | --------------------------------------------+------------------------------- Comment (by [EMAIL PROTECTED]):
Proposed action: * In the example rules, remove DRIVER=="?*" part * Remove the paragraph starting with "The DRIVER=="?*" key prevents Udev" * Add the following at the end of Section 7.13.1 "Creating stable names for network interfaces": ---- The example rules above don't work for every setup. For example, MAC-based rules break when [http://linux-net.osdl.org/index.php/Bridge bridges] or [http://www.candelatech.com/~greear/vlan/vlan.html VLANs] are used, because bridges and VLANs have the same MAC address as the network card. One wants to rename only the network card interface, not the bridge or VLAN interface, but the example rule matches both. If you use such virtual interfaces, you have two potential solutions. One is to add the DRIVER=="?*" key after SUBSYSTEM=="net" in MAC-based rules, so that they stop matching the virtual interfaces (but this is known not to work with some older Ethernet cards because they don't have the DRIVER variable in the uevent and thus the rule matches nothing with such cards). Another solution is to switch to the rules that use the bus position as a key. The second known non-working case is with wireless cards using the [http://madwifi.org/wiki MadWifi] driver, because it creates at least two interfaces (athX and wifiX, where X is a digit) with the same MAC address and bus position. To disambiguate, add SYSFS{type}=="zzz" after SUBSYSTEM=="net" for each interface that is handled by that driver, where zzz is the output of "cat /sys/class/net/interface_name/type". There may be other cases where the rules above don't work. Currently, bugs on this topic are still being reported to Linux distributions, and no 100% bullet proof solution is known. ---- -- Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/1842> LFS Trac <http://wiki.linuxfromscratch.org/lfs/> Linux From Scratch: Your Distro, Your Rules. -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
