On Thu, Sep 21, 2006 at 03:55:14PM -0700, Jean Tourrilhes wrote: > > Jean, are there any other possibilities? > > Yes, dropping SIOCSIWAP (set) entirely, and keep only > SIOCGIWAP (get).
I don't think that this would be acceptable. > We need to be pragmatic. Very few people need to set a fixed > BSSID. I would even venture to say that in the case of most people > setting a fixed BSSID, it's an error and they should not do it (it > kills roaming, which is a desirable feature). I've yet to find a card > which scanning is broken to the point that you need to fudge the > BSSID. Maybe very few _people_ use it directly, but please keep in mind that programs like wpa_supplicant may control roaming and do it by using this SIOCSIWAP. In addition, being able to limit AP selection to one specific BSSID can be quite useful for number of uses. > There are some drivers that don't support SIOCSIWAP (set), and > it's usually not a problem, users are not complaining about it. That's > why I claim we could drop the (set) support. Of course, we can't do it > because one PhD student at Berkeley need the feature ;-) There's more than one PhD student needing this and I would be very much against removing it. -- Jouni Malinen PGP id EFC895FA - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
