From: Larry Finger <larry.finger@lwfinger.net>
To: Dan Williams <dcbw@redhat.com>
Cc: netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Paul Marks <pmarks@purdue.edu>
Subject: Re: Hidden SSID's
Date: Sun, 28 Jan 2007 16:18:01 -0600 [thread overview]
Message-ID: <45BD2119.2000209@lwfinger.net> (raw)
In-Reply-To: <1169899689.25670.3.camel@localhost.localdomain>
Dan Williams wrote:
> On Fri, 2007-01-26 at 21:48 -0600, Larry Finger wrote:
>> Is there a convention regarding the information that a wireless MAC layer should provide when
>> reporting scan data from an AP with a hidden SSID?
>>
>> In ieee80211, the software inserts the string "<hidden>" for such an AP, which seems to give
>> wpa_supplicant fits because it rejects the SSID before even looking at the encryption data. Is this
>> the normal convention?
>
> No. It's wrong. It is not normal convention. The one and only
> _correct_ way of reporting a hidden SSID is to not report the SSID at
> all. The only item that needs to be reported with WEXT is the BSSID,
> and the client app assumes that if the SSID is not received for a given
> scan result, that the driver doesn't have an SSID for that BSSID.
>
> I really, really don't know why ieee80211 uses <hidden>, but it's a pain
> in the ass and should NOT be done for d80211. I don't know if we can
> ever remove it from ieee80211 though for backwards compat reasons.
Is there something funny about Cisco APs with hidden SSID? I made a patch for ieee80211 and softmac
that works on my AP when its SSID is hidden. It also works for Paul Marks on his personal AP, but
fails for the Cisco units at Purdue. His interface is a 4311 and there may be a signal strength
issue, but we are not sure.
My patch fixes ieee80211 without breaking the previous behavior.
Larry
next prev parent reply other threads:[~2007-01-28 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 3:48 Hidden SSID's Larry Finger
2007-01-27 12:08 ` Dan Williams
2007-01-27 15:29 ` Larry Finger
2007-01-28 21:28 ` Johannes Berg
2007-01-29 13:00 ` Dan Williams
2007-01-30 3:09 ` Jouni Malinen
2007-01-30 3:36 ` Dan Williams
2007-01-30 4:52 ` Larry Finger
2007-01-30 5:08 ` Jouni Malinen
2007-01-30 7:08 ` Larry Finger
2007-01-30 22:56 ` Jouni Malinen
2007-01-31 2:35 ` Larry Finger
2007-02-01 18:46 ` Jouni Malinen
2007-01-28 22:18 ` Larry Finger [this message]
2007-01-30 22:53 ` Jouni Malinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45BD2119.2000209@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmarks@purdue.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).