On Tue, 2006-08-29 at 16:01 -0700, Michael Wu wrote: > On Tuesday 29 August 2006 15:50, Michael Wu wrote: > > On Tuesday 29 August 2006 15:28, Mohamed Abbas wrote: > > > SIOCGIWAP will always report the bssid no > > > matter what the status of our link. > > > > That is not the case at the moment. Were you planning to change that? > > > Opps, it looks like it is the case. Ignore that. > > Perhaps we should make SIOCGIWAP always reflect the AP we're currently > associated to, and 00:00:00:00:00:00 if there is none. > > -Michael Wu
Um, that's how it's supposed to work, and that's how it's always worked. If you're associated with an access point, its BSSID is returned from SIOCGIWAP. If you are not associated, 00:00:00:00:00:00 is returned. Please don't break that. The driver should also send the appropriate netlink IWAP events when it gets disconnected or when a successful connection occurs using wireless_send_event(). If a valid BSSID is returned from an SIOCGIWAP, it's assumed that that access point will allow your traffic to pass, i.e. all required association and authentication has successfully completed. SIOCGIWAP behavior does _not_ necessarily reflect what BSSID is set with SIOCSIWAP. Dan - 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
