BROADCOM Wireless device name switch

finarfin · 2011-01-30 11:07:40

Hi all,
i have a broadcom wireless card,
i installed it using instruction on the wiki, and it works fine,

se i have the problem of interfaces swapping every time, i read the solution in the wiki.
But it seems to don't work.
In fact i edited the file /etc/udev/rules.d/10-network.rules
with that:

SUBSYSTEM=="net", ATTR{address}=="00:22:64:7F:E8:7C", NAME="eth0"
SUBSYSTEM=="net", ATTR{address}=="00:21:00:9B:3C:6D", NAME="eth1"

but it seems to ignore it!!!!
I have the interfaces swapped every time.
(i had a similar problem with other udev rules, seems that every rules that i writ is ignored!!!)

Any idea?

Last edited by finarfin (2011-01-30 13:16:20)

.:B:. · 2011-01-30 12:48:04

If the above is not working then there's something wrong with those rules... You should add your own udev rules file rather than edit the existing ones, since those will be replaced when there's a udev upgrade.

I have this:

$ grep net /etc/udev/rules.d/05-personal.rules 
ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{type}=="801", NAME="wmaster0"
ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{type}=="1", NAME="intel"
ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="marvell"

MAC addresses in the first two lines should be identical. I renamed my interfaces to their respective vendors to keep. Not sure if the first line is still needed (there used to be a wmaster0 interface way back), but it doesn't hurt either, so I left it in.

And please use [ code ] tags for better readability.

finarfin · 2011-01-30 18:06:09

Ok,
i tried to modify my file /etc/udev/rules.d/10-network.rules with your suggestion, but nothing.

I don't see any new device created.
It seems that it ignore my rules.

.:B:. · 2011-01-30 18:51:52

You're using ACTION=="add" right?

Remove your network driver, restart udev, run

# udevadm monitor

and reload your network driver. Check the output of udevadm to see where it goes wrong, if your interface does not get renamed.

finarfin · 2011-01-30 19:47:49

Hi,

i tried to do that:

[root@azraphel ProgettiVari]# /etc/rc.d/network stop
[root@azraphel ProgettiVari]# rmmod wl 
[root@azraphel ProgettiVari]# udevadm control restart
[root@azraphel ProgettiVari]# udevadm monitor

and then reloaded wl driver, restarted the network and the result in udevadm monitor is:

monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1296414915.340764] add      /module/wl (module)
UDEV  [1296414915.341407] add      /module/wl (module)
KERNEL[1296414915.363371] add      /devices/pci0000:00/0000:00:09.0/0000:06:00.0/net/eth1 (net)
KERNEL[1296414915.367708] add      /devices/pci0000:00/0000:00:09.0/0000:06:00.0/net/eth1/queues/rx-0 (queues)
KERNEL[1296414915.552115] add      /bus/pci/drivers/wl (drivers)
UDEV  [1296414915.552919] add      /bus/pci/drivers/wl (drivers)
UDEV  [1296414915.629185] add      /devices/pci0000:00/0000:00:09.0/0000:06:00.0/net/eth1 (net)
UDEV  [1296414915.631069] add      /devices/pci0000:00/0000:00:09.0/0000:06:00.0/net/eth1/queues/rx-0 (queues)

It seems that my rules is ignored!!!
A question: i need to launch a specific service to have udev rules parsed? Or specific permissions?

.:B:. · 2011-01-30 21:36:16

No, just restarting udev should be the trick. I don't know how the wl module works though, that's Broadcom proprietary, and I'm guessing it doesn't use the mac80211 stack. That would explain why regular udev rules don't work.

How did you set up your rules? Just by looking at examples or by actually gathering output and turning that into a rule? If it's the former, try http://reactivated.net/writing_udev_rules.html

litemotiv · 2011-01-30 22:31:53

I've used the same setup with wl until a few weeks back, the static network naming example in the wiki should work without issues. If not, something else must be wrong.

finarfin · 2011-01-31 10:49:49

I tried the example on the wiki.

But it seems that the rule is ignored!
I tried also to add new devices as suggested, but same result, nothing happen.

It is like that new udev rules are simply ignored.

To enable udev rules, i need some specific services?

eduardo.eae · 2011-01-31 11:23:05

I remember that it was announced in the Arch mail list a while back: NAME rules was was removed from udev.

.:B:. · 2011-01-31 11:30:06

Still working fine here...

finarfin · 2011-01-31 18:49:47

Here is my situation, i have the following rules in /etc/udev/rules.d:

-rw-r--r-- 1 root root  104 Oct 26 05:39 10-cups-usb.rules
-rw-r--r-- 1 root root  132 Jan 30 20:10 10-network.rules
-rw-r--r-- 1 root root  462 Jan  3 23:14 75-cd-aliases-generator.rules.optional
-rw-r--r-- 1 root root 3981 Jan  3 23:14 75-persistent-net-generator.rules.optional

The rule 10-network.rules is the one that i created following the example on the wiki.
here is the code:

SUBSYSTEM=="net", ATTR{address}=="00:22:64:7f:e8:7c", NAME="eth1"
SUBSYSTEM=="net", ATTR{address}=="00:21:00:9b:3c:6d", NAME="eth0"

And the actual ifconfig is:

eth0      Link encap:Ethernet  HWaddr 00:21:00:9B:3C:6D  
          inet addr:192.168.1.237  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::221:ff:fe9b:3c6d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24016 errors:0 dropped:0 overruns:0 frame:2481
          TX packets:16701 errors:6 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:30104092 (28.7 Mb)  TX bytes:1935694 (1.8 Mb)
          Interrupt:17 

eth1      Link encap:Ethernet  HWaddr 00:22:64:7F:E8:7C  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:16

As you can see the two device are switched.

Maybe the rule should have the executable flag set?

Inxsible · 2011-01-31 18:52:06

I don't see them as switched. They are mapped exactly as you have it in the 10-network.conf file.

finarfin wrote:

SUBSYSTEM=="net", ATTR{address}=="00:22:64:7f:e8:7c", NAME="eth1"
SUBSYSTEM=="net", ATTR{address}=="00:21:00:9b:3c:6d", NAME="eth0"

eth0      Link encap:Ethernet  HWaddr 00:21:00:9B:3C:6D

eth1      Link encap:Ethernet  HWaddr 00:22:64:7F:E8:7C

litemotiv · 2011-01-31 18:53:52

finarfin · 2011-01-31 20:21:42

d'oh!!!!
I only wanted to check you are paying attention!

Arch Linux

#1 2011-01-30 11:07:40

BROADCOM Wireless device name switch

#2 2011-01-30 12:48:04

Re: BROADCOM Wireless device name switch

#3 2011-01-30 18:06:09

Re: BROADCOM Wireless device name switch

#4 2011-01-30 18:51:52

Re: BROADCOM Wireless device name switch

#5 2011-01-30 19:47:49

Re: BROADCOM Wireless device name switch

#6 2011-01-30 21:36:16

Re: BROADCOM Wireless device name switch

#7 2011-01-30 22:31:53

Re: BROADCOM Wireless device name switch

#8 2011-01-31 10:49:49

Re: BROADCOM Wireless device name switch

#9 2011-01-31 11:23:05

Re: BROADCOM Wireless device name switch

#10 2011-01-31 11:30:06

Re: BROADCOM Wireless device name switch

#11 2011-01-31 18:49:47

Re: BROADCOM Wireless device name switch

#12 2011-01-31 18:52:06

Re: BROADCOM Wireless device name switch

#13 2011-01-31 18:53:52

Re: BROADCOM Wireless device name switch

#14 2011-01-31 20:21:42

Re: BROADCOM Wireless device name switch

Board footer