From 3a234c0a82218253d42beb698c76da97052b34f2 Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Sun, 30 Jul 2006 23:03:21 +0000 Subject: Fix explanation of udev rules for drivers that create multiple interfaces git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.2/BOOK@7720 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter07/network.xml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/chapter07/network.xml b/chapter07/network.xml index 5e9d615d3..83bbd0baa 100644 --- a/chapter07/network.xml +++ b/chapter07/network.xml @@ -90,12 +90,11 @@ EOF the bus position as a key. The second known non-working case is with wireless cards using the - MadWifi or HostAP drivers, because they create at least two interfaces - with the same MAC address and bus position. For example, the Madwifi driver + MadWifi or HostAP drivers, because they create at least two interfaces with + the same MAC address and bus position. For example, the Madwifi driver creates both an athX and a wifiX interface where X is a digit. To - disambiguate these cases, 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. + differentiate these interfaces, add an appropriate KERNEL parameter such as + KERNEL=="ath*" after SUBSYSTEM=="net". 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 -- cgit v1.2.3-54-g00ecf