On Wed, Oct 10, 2007 at 10:36:43AM -0400, Dan Williams wrote: > On Wed, 2007-10-10 at 11:02 +0200, Johannes Berg wrote: > > On Tue, 2007-10-09 at 19:49 -0400, John W. Linville wrote: > > > From: John W. Linville <linville@xxxxxxxxxxxxx> > > > > > > Some AP equipment "in the wild" services multiple SSIDs using the > > > same BSSID. This patch changes the key of sta_bss_list to include > > > the SSID as well as the BSSID and the channel so as to prevent one > > > SSID from eclipsing another SSID with the same BSSID. > > The "standard" (which is a stretch) was that only _one_ SSID can be > broadcast in beacons, and the rest of the supported SSIDs must be > hidden. Is that the case? Or is the AP you're referring to actually > pushing out multiple beacons with different not-hidden SSIDs and the > same BSSID? My impression is that the standard is not particularly clear on this, hence the variety of behaviors. Can you cite specific wording? My research indicates the existance of both "1 beacon, N-1 hidden" and "N beacons" behaviors. Either way, the sta_bss_list can be populated not just from beacons but also from probe responses. So even if N-1 SSIDs are hidden, we still need to be able to record information about them. Unfortunately I don't have any hardware that behaves in this fashion. I discovered references to this behavior while researching the preceding "same BSSID on different frequencies" patch. Having become aware of this behavior, I figured it was worth fixing at the same time to avoid future bug reports. Hth! John -- John W. Linville linville@xxxxxxxxxxxxx - 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
