On Tue, Jan 30, 2007 at 08:35:18PM -0600, Larry Finger wrote:
> If one does the equivalent of 'iwlist eth1 scan essid myssid', then a probe
> response with
> NETWORK_EMPTY_ESSID set in the network flags will have 'myssid' returned in
> the SSID field of the
> returned buffer. If the input comman
Jouni Malinen wrote:
> On Tue, Jan 30, 2007 at 01:08:29AM -0600, Larry Finger wrote:
>
>> Any AP with a hidden SSID will only respond to probe requests that specify
>> its SSID, and will ignore
>> any other probes. In addition, the response will have an empty SSID field.
>> These responses are t
On Sun, Jan 28, 2007 at 04:18:01PM -0600, Larry Finger wrote:
> Is there something funny about Cisco APs with hidden SSID?
Yes, there is.. Or well, "hidden SSID" is funny concept in itself, but
anyway.. Some APs set the SSID IE to an array of 0x00 octets with the
length of the original SSID when
On Tue, Jan 30, 2007 at 01:08:29AM -0600, Larry Finger wrote:
> Any AP with a hidden SSID will only respond to probe requests that specify
> its SSID, and will ignore
> any other probes. In addition, the response will have an empty SSID field.
> These responses are the
> only ones in which a sub
Jouni Malinen wrote:
> On Mon, Jan 29, 2007 at 10:52:20PM -0600, Larry Finger wrote:
>
>> When an AP has a hidden SSID, ieee80211 fails, at least with wpa_supplicant,
>> which searches through the scan data looking for a particular ssid. Because
>> ieee80211 has substituted a false ssid, namely ""
On Mon, Jan 29, 2007 at 10:52:20PM -0600, Larry Finger wrote:
> When an AP has a hidden SSID, ieee80211 fails, at least with wpa_supplicant,
> which searches through the scan data looking for a particular ssid. Because
> ieee80211 has substituted a false ssid, namely "", wpa_supplicant
> cannot au
Dan Williams wrote:
> On Mon, 2007-01-29 at 19:09 -0800, Jouni Malinen wrote:
>> On Mon, Jan 29, 2007 at 08:00:11AM -0500, Dan Williams wrote:
>>
>>> Well, there's no way a userspace program could depend on all hidden SSID
>>> APs having the tag, since if you stick in another,
>>> non-ieee80211-st
On Mon, Jan 29, 2007 at 08:00:11AM -0500, Dan Williams wrote:
> Well, there's no way a userspace program could depend on all hidden SSID
> APs having the tag, since if you stick in another,
> non-ieee80211-stack card it won't be like that. So I don't think we
> should care about in d80211, but
On Mon, 2007-01-29 at 19:09 -0800, Jouni Malinen wrote:
> On Mon, Jan 29, 2007 at 08:00:11AM -0500, Dan Williams wrote:
>
> > Well, there's no way a userspace program could depend on all hidden SSID
> > APs having the tag, since if you stick in another,
> > non-ieee80211-stack card it won't be li
On Sun, 2007-01-28 at 22:28 +0100, Johannes Berg wrote:
> On Sat, 2007-01-27 at 07:08 -0500, Dan Williams wrote:
>
> > I really, really don't know why ieee80211 uses , 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
On Sat, 2007-01-27 at 07:08 -0500, Dan Williams wrote:
> I really, really don't know why ieee80211 uses , 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.
Ugh. /me makes a note for the cfg8
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 "" for such an
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 "" for such an
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 "" for such an AP,
> which seems to give
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 "" for such an AP, which
seems to give
wpa_supplicant fits because it rejects the SSID before even lookin
15 matches
Mail list logo
