All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Wade Berrier <wberrier@gmail.com>,
	Michael Wu <flamingice@sourmilk.net>,
	linux-wireless@vger.kernel.org
Subject: Re: realtek 8185
Date: Fri, 19 Oct 2007 02:38:09 -0400	[thread overview]
Message-ID: <1192775889.14897.29.camel@localhost.localdomain> (raw)
In-Reply-To: <20071018174108.GC8510@tuxdriver.com>

On Thu, 2007-10-18 at 13:41 -0400, John W. Linville wrote:
> On Thu, Oct 18, 2007 at 11:13:00AM -0600, Wade Berrier wrote:
> > On 10/17/07, Michael Wu <flamingice@sourmilk.net> wrote:
> > > On Wednesday 17 October 2007 18:52:28 Wade Berrier wrote:
> > > > Another thing I'm noticing is that I can't connect to an 802.11b open
> > > > network with a hidden essid.
> > > >
> > > For those, you should specify the channel, and bssid in one iwconfig command,
> > > and then ssid in another command. Everything needs to be specified for hidden
> > > networks. Never tried connecting to hidden networks with network manager so I
> > > dunno if that's suppose to work.
> > 
> > I've been able to connect to this hidden network via network manager.
> > >From a users experience, I enter in the essid from the "Connect to
> > other wireless network" dialog, and it connects.  I'm not sure how
> > networkmanager makes the connection between the essid and the ap.
> 
> If anything, I usually find that I can connect to the hidden networks
> using iwconfig but _not_ with NetworkManager.  FWIW, mac80211 will
> send probe requests for unknown SSIDs when trying to associate.

NM always uses wpa_supplicant for connections, so whatever
wpa_supplicant is (not) doing is probably the culprit here.
wpa_supplicant does use IW_SCAN_THIS_ESSID, but only a few drivers
implement that.  I was also not able to consistently connect to a
non-broadcasting AP with plain wpa_supplicant and an ipw2200 (which
AFAIK does support IW_SCAN_THIS_ESSID).

What _should_ be happening here is that, if the SSID doesn't show up in
the scan list that wpa_supplicant has, it will ask the driver to scan
with the specific SSID it wants to connect to using IW_SCAN_THIS_ESSID.
The driver should then send out active probe requests on all channels
for that SSID.  If it gets a result it should notify userspace via
SIOCGIWSCAN events, but with only _one_ event after the entire scan is
complete.  If the SSID was found, wpa_supplicant will get the new scan
result and connect to the previously hidden SSID that is now known to
the driver.

FWIW, Bill Moss reports that disabling hardware scan on iwl3945 (with
the module parameter) lets NM connect to hidden networks with high
success.

Dan

> Unfortunately, I'm not really sure how this relates to the problem
> you are having.  Perhaps probe responses are being lost somehow?
> 
> John


      parent reply	other threads:[~2007-10-19  6:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bbbeeccd0710160658p7f127bb9if2239287bee33d6c@mail.gmail.com>
     [not found] ` <bbbeeccd0710162220u3b276506s68457b4220bec8ae@mail.gmail.com>
     [not found]   ` <bbbeeccd0710171552x37986f68m906a603e793c7996@mail.gmail.com>
     [not found]     ` <200710171938.48414.flamingice@sourmilk.net>
2007-10-18 17:13       ` realtek 8185 Wade Berrier
2007-10-18 17:41         ` John W. Linville
2007-10-19  4:54           ` Wade Berrier
2007-10-19  6:32             ` Dan Williams
2007-10-19  6:38           ` Dan Williams [this message]

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=1192775889.14897.29.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=flamingice@sourmilk.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=wberrier@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.