evan foss wrote:
> On Nov 12, 2007 2:05 PM, Larry Finger <[EMAIL PROTECTED]> wrote:
>> evan foss wrote:
>>> I can wlist wlan0_rename scan but it has issues and seems to alter
>>> eth1. Now I haven't yet tried this at a location with good signal
>>> quality. I just want to understand what is happening with the
>>> interface name(s).
>> The device renaming is probably handled in directory /etc/udev/rules.d by a
>> rule with "persistent"
>> and "net" in its name. On my openSUSE 10.3 system, it is called
>> 70-persistent-net.rules. On 10.2, it
>> was 30-xxxxxxx. In this file, you should see statements like
>>
>> # PCI device 0x10de:0x0269 (forcedeth)
>> SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:16:d3:17:07:2e",
>> NAME="eth0"
>>
>> # PCI device 0x14e4:0x4311 (b43, b43legacy, b43legacy)
>> SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1a:73:04:1d:e5",
>> ATTR{type}=="1", NAME="eth1"
>>
>> Your rule for the wireless device should have your MAC address
>> (00:14:a5:b7:54:15) in the address
>> field. These rules leave the name of wmaster0 alone, at least on the version
>> of udev that I'm using.
>>
>> Larry
>>
>
> Mine was under 70-persistent-net.rules
> I commented out the following line.
>
> # PCI device 0x14e4:0x4311 (bcm43xx)
> #SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:14:a5:b7:54:15",
> NAME="eth1"
>
> Then reloaded the module. Which caused udev to add this.
>
> # PCI device 0x14e4:0x4311 (b43-pci-bridge)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:14:a5:b7:54:15",
> ATTR{type}=="1", NAME="wlan0"
>
> Which seems to work fine. Except that I still get wmaster0 with wlan0.
> wlan0 gets the correct mac address but won't let me set essid. It does
> scan (iwlist). But I think wmaster0 is causing problems it has the
> same mac address as wlan0 only with a few extra zeros at the end. I
> suspect that wmaster0 is interfering with wlan0.
Whatever problems you are having, they are not caused by wmaster0. It is a
"feature" of mac80211,
and we all have wmaster0 and a separate wlan0, or eth1. It does not get in the
way.
Are you running iwconfig as root when you are trying to set essid? Setting
anything requires
privilege. If you are root, what is the error message?
Larry
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
