[PATCH] libertas: automatically re-associate
Holger Schurig
hs4233 at mail.mn-solutions.de
Wed Oct 10 15:00:14 EDT 2007
> so in libertas_mac_event_disconnected() it should to be something like
> the following:
...
I'll look in some of the next days again into this. Today and tomorrow
I'm busy with other things.
Oh, and BTW, today I found by chance another reason why auto-reassoc is
helpful and necessary :-) On a Cisco 1231 AP I played a bit with the
command interface. And there was a command to check how busy all the
channels are. When I issued this command, I saw in the log of the Cisco
(I'm sending it to the console) and also in the syslog of the machine
running the libertas driver that the Cisco IOS sent an disassociation
to all clients. Then it went checking for busy channels and gave me
some output. After this, two client (one libertas, one other)
automatically re-associated and things continued as if nothing would
have happened.
Now, in a Cisco AP you can specify the channel for the AP. And you can
also say "Use least congested Frequency". This makes the AP does this
channel scanning --- that I issued manually --- do automatically. With
the current current code, my libertas driven card would have been
stuck ...
As for WPA driven environments: you can operate WPA supplicant in two
modes. In one modes does WPA does the work of selecting which AP to
use. It also sends the equivalent of "iwconfig ethX ap
xx:XX:XX:XX:XX:XX" to the card.
In the other mode (I think it is "ap_scan=2"), wpa_supplicant just
reacts to a re-association that the driver did without further fuzz.
I guess that your issues are with the first mode?
More information about the libertas-dev
mailing list