From: Jan Rychter <jan@ry...> - 2006-01-30 11:11:07
I'm using madwifi-ng together with wpa_supplicant (oh, the pain). My
access points are a/b/g and my card is capable of a/b/g too. However, it
seems that when scanning, 802.11b channels are scanned first, so my
computer happily associates using 802.11g instead of 802.11a, which is
also present, with the same ESSID.
Is it possible to prioritize 802.11a so that it's scanned first, but
fall back onto 802.11b/g if we can't find anything on the 802.11a
From a quick look at wpa_supplicant sources it seems that it hands off
scanning to the madwifi driver and this is a madwifi issue.
Additionally, I'm getting total freezes when trying to modify parameters
via "iwpriv ath0 mode X" when the interface is active and scanning. Is
this expected, or should I report it as a bug?