On Fri, Mar 26, 2010 at 07:02:40PM -0700, Jouni Malinen wrote: > On Fri, 2010-03-26 at 16:16 -0700, Pavel Roskin wrote: > > I confirm that scan_freq is accepted by the current wpa_supplicant but > > has no reliable effect. Both ath5k and ath9k connected to an AP on the > > channel 6 when "scan_freq=2412" was in the configuration file. > > scan_freq is not supposed to limit the association to specific channels; > it is only to limit scan requests made by wpa_supplicant. You may still > find BSSes on other channels either due to scan requests made by other > programs or by receiving Beacon/Probe Response frames on another > channel. > > If there is interest for limiting the association to specific channels, > it should be trivial addition to wpa_supplicant (with nl80211). I don't > know whether I would fully agree on this being a useful thing for > general use, but I can understand it at least as a testing tool (which > people may then misuse for other things ;-).
We could add a new command to disable a channel. That would take care of custom channel configurations. Luis _______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
