Quoting Andrew Lunn <andrew.lunn@xxxxxxxx>:
I suggest that you check in the monitor mode that there are indeed
beacons sent with this MAC address. Maybe they are not. It's quite
possible. MadWifi has an option to disable beacons for some virtual
APs.
Well, other devices are seeing it, eg other Atheros devices and intel
IPW2200. So somehow i doubt it is not sending beacons.
What I have found is that there are beacons for every ESSID, but
scanning finds only one ESSID. I tested that with orinoco driver,
which doesn't depend on mac80211.
Maybe mac80211 decided to do a passive scan, perhaps due to your country
regulations?
CH has no such regulations...
You are right, it's more like the opposite is happening. It looks
like mac80211 relies only on probe requests and not on beacons.
It's quite possible that b43 will associate if you set the ESSID
correctly. Maybe you'll need to set "ap" with iwconfig as well.
I hacked the madwifi driver a little, to disable the wme_ie and the
ath_ie IEs in the beacon and probe response messages. Only then did
the b43 device list the Atheros device in its scan list. However i
could not get it to associate. Authentication always failed. The b43
driver gives error messages and the MadWifi driver never received the
Authentication request messages.
It seems to me that the problem is on the MadWifi side. Changing the
code may be irrelevant. MadWifi replied to probe requests only on one
virtual interface, and this time it was the interface you needed (for
whatever reason). Maybe it switched back when you tried to associate.
In the end i gave up. I have another machine with an ipw2100 card
which worked first time and i don't see any point using the B43 device
when it causes me to much pain.
Maybe b43 does something different, so that the trick with virtual
devices doesn't work. But it looks like some problems don't even need
b43 on the client side.
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
