From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Zhao, Shanyu" <shanyu.zhao@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/1] cfg80211: wext: set bssid to NULL in SIOCIWESSID
Date: Mon, 1 Feb 2010 16:29:19 -0500 [thread overview]
Message-ID: <20100201212918.GF4952@tuxdriver.com> (raw)
In-Reply-To: <1265059504.29119.1.camel@johannes.local>
On Mon, Feb 01, 2010 at 10:25:04PM +0100, Johannes Berg wrote:
> On Mon, 2010-02-01 at 14:47 -0500, John W. Linville wrote:
>
> > > > iwconfig wlan0 essid "foo"
> > > > This will make the station associate with the first AP with essid
> > > > "foo".
> > > >
> > > > iwconfig wlan0 ap "00:...:ff"
> > > > This will disassociate from the previous AP, and then associate with
> > > > the first AP with MAC "00:...:ff".
> > > >
> > > > Am I missing anything here?
> > >
> > > No, I missed something. The problem will only occur when the SSID is
> > > hidden as well, because the connect code will not have the SSID and not
> > > know what to scan for, or which SSID to choose (there are Cisco APs that
> > > use the same BSSID for multiple hidden SSIDs).
> >
> > Well, in the confusion I deleted the original post. Could you
> > (i.e. Shanyu Zhao) resend it to me?
>
> Sorry -- I wasn't clear. My mail missed something in describing the
> problem, but that doesn't change the fact that the patch will break it.
OK, thanks for clarifying! :-)
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-02-01 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 23:39 [PATCH 1/1] cfg80211: wext: set bssid to NULL in SIOCIWESSID shanyu.zhao
2010-01-30 8:37 ` Johannes Berg
2010-02-01 18:57 ` Zhao, Shanyu
2010-02-01 19:27 ` Johannes Berg
2010-02-01 19:47 ` John W. Linville
2010-02-01 21:25 ` Johannes Berg
2010-02-01 21:29 ` John W. Linville [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=20100201212918.GF4952@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=shanyu.zhao@intel.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).