linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH, take 2] libertas: implement SSID scanning for SIOCSIWSCAN
Date: Tue, 04 Mar 2008 09:04:10 -0500	[thread overview]
Message-ID: <1204639450.7183.22.camel@localhost.localdomain> (raw)
In-Reply-To: <200803040738.19911.hs4233@mail.mn-solutions.de>

On Tue, 2008-03-04 at 07:38 +0100, Holger Schurig wrote:
> > However, it never found the hidden AP I was using (ie, it
> > never replaced the blank SSID in the iwlist scan results with
> > the actual SSID as I'd expect).  I haven't tracked that down
> > quite yet, but it might be an issue in the scan result
> > handling code or it could be firmware.
> 
> Do you mean that 
> 
> 00:1D:60:14:33:2B   <empty SSID>
> 00:1D:60:14:33:2B   WLAN
> 
> should be unified into
> 
> 00:1D:60:14:33:2B   WLAN
> 
> ???

_If and only if_ the BSSID and all security and flags match, then yes.  

But that wasn't the issue; the issue was that even after doing 'iwlist
eth1 scan ssid hidden-test' the SSID 'hidden-test' was never returned in
the scan results, but the AP's BSSID without an SSID was.  So, assuming
that I know 00:1D:60:14:33:2B is an AP with an ssid of 'hidden-test':

----------------------------------------
iwlist eth1 scan

00:1D:60:14:33:2B   <empty SSID>

iwlist eth1 scan essid hidden-test

00:1D:60:14:33:2B   <empty SSID>

iwlist eth1 scan essid hidden-test

00:1D:60:14:33:2B   <empty SSID>

(repeat...)
----------------------------------------

I need to do some more investigation inside libertas though, because I'm
not confident where the bug may lie.  If it's something in the firmware,
there's not much we can do of course.

> First I wanted to do that, but then I thought that maybe this is 
> erraneous. An AP can have several SSIDs, one of them could be 
> hidden, the other ones not hidden. E.g. this is easy to setup on 
> a Cisco 123x or Cisco 124x access-point.

Right.  I've done that :)

> I also have a "take 3" of this patch now, because I adapted 
> (after a chat with David on IRC) the outstanding patches from 
> libertas-2.6 to wireless-testing. Two of the patches touched 
> scan.c as well, so I rewrote my scan-for-specific-ssid patch to 
> apply on top of the 5 David-Woodhouse-patches.

Yeah, was going to ask that you rebase your patch on top of the ones you
posted from libertas-2.6.

Thanks,
Dan



  reply	other threads:[~2008-03-04 14:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 14:22 [PATCH, take 2] libertas: implement SSID scanning for SIOCSIWSCAN Holger Schurig
2008-02-26 15:44 ` Marc Pignat
2008-02-28  2:28 ` Dan Williams
2008-02-28  6:35   ` Holger Schurig
2008-02-28 14:05     ` John W. Linville
2008-03-03 19:18 ` Dan Williams
2008-03-04  6:38   ` Holger Schurig
2008-03-04 14:04     ` Dan Williams [this message]
2008-03-04 19:38 ` Dan Williams

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=1204639450.7183.22.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).