Dan Williams <dcbw@xxxxxxxxxx> writes: > On Fri, 2009-01-09 at 09:55 +0200, Kalle Valo wrote: >> Dan Williams <dcbw@xxxxxxxxxx> writes: >> >> > 1) A 'frequency' config item that works in infrastructure mode too, >> > ignoring any AP not matching that frequency >> >> Just out of curiosity, why this feature is needed? I can understand >> hard-coding bssid, but I don't understand the use for hard-coding the >> frequency. > > If the user wishes to lock the connection to a specific frequency, > irregardless of other values. I guessed that part :) But I wanted to ask why would user want to do this? I don't see any benefits from that. > Maybe you're right and we don't really care about it, but one other > thing that would be nice is a "band" argument for a network block to > differentiate A vs. B/G APs that might have the same SSID and > security settings, but where the user only wants to use the A-side > for example. This would be nice to have, most probably I would immediately disable A band just to get faster scanning. I don't use 802.11a anywhere, for me it's useless. -- Kalle Valo -- 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
