On Thu, 21 Sep 2006 13:39:18 -0700, mabbas wrote: > I can fix the patch to do just that if we agree on that.
Well, we need a flag indicating whether we are associated or not. I don't know about such a flag in WE (hopefully we will have that in nl80211). Now we have two possibilities: (a) If a fixed BSSID is set (via SIOCSIWAP), return it from SIOCGIWAP. There is no way to find out whether we are associated or not. The behaviour is also inconsistent with the case when no fixed BSSID is set - SIOCGIWAP returns all zeros or some (random from our POV) BSSID then. So, when you get a BSSID from SIOCGIWAP, to determine what that means you need to know if there was a fixed BSSID set. To do that you need to get a BSSID from SIOCGIWAP. The chicken and egg problem? (b) SIOCSIWAP returns zeros when we are not associated, BSSID otherwise. There is no way to find out if you set a fixed BSSID or not. If you accidentally set a fixed BSSID you will have a hard time finding out why your card is not associating. Jean, are there any other possibilities? If not, (b) seems much more reasonable to me, because: - The value returned from SIOCGIWAP has a well-defined meaning independent of the current configuration of the interface. - Dan wants that. Jiri -- Jiri Benc SUSE Labs - 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
