On Thu, 01 Sep 2005 19:16:05 +0100, Pedro Ramalhais wrote: > > Of > > course you may sometimes want to force reassociation manually - and > > there should be some call available for this. (Maybe setting BSSID while > > the card is running should force reassociation?) > > That's the kind of hackish solution that brings confusion. We should > separate things: wireless configuration and wireless association. This > way you won't have to do those hackish approaches and special cases. > What i mean is that if you want to associate, tell the card to do so, > don't send -1 as the channel or send 0 as the essid_len, or resend the > previously configured essid.
I probably didn't explain well what I thought, sorry. Imagine following situation: we have an AP with BSSID1 and another one with BSSID2, both in the same ESS. When you set just the ESSID, somebody (kernel or daemon, I'm still not decided on this) tell the driver to associate to one of the APs - e.g. to BSSID1. When conditions change, the driver is told to reassociate (to BSSID2). And so on. When you manually set BSSID2 (while we are associated to BSSID1), it surely means that the user wants to reassociate to BSSID2 - there is nothing hackish in that. But you're right anyway. -- 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
