On Fri, Mar 24, 2006 at 10:57:22AM -0500, Dan Williams wrote: > <hidden> this is something that ieee80211 does that's completely wrong. > Drivers need to report the _exact_ ESSID from the air in their scan > results. It's up to the user space app to deal with ESSID length of 0.
I agree that "<hidden>" should not be used, but this is bit more complex than just reporting zero-length SSID. By the way, can we try to start getting rid of calling this ESSID; it's SSID and ESSID never made it to the IEEE 802.11 standard. Whatever component processes Probe Response frames, has to provide information from them to user space. If this is done in the kernel code, the BSS table should probably report multiple <BSSID,SSID> pairs even for the same BSSID in case of multi-SSID support in the AP. This is needed to handle cases where SSIDs use different security policy and this requires that active scan was used to probe for specific SSID(s). If this information is not available, reporting an empty SSID sounds like a good policy. -- 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
