From: "John W. Linville" <linville@tuxdriver.com>
To: Abhijeet Kolekar <abhijeet.kolekar@intel.com>,
linux-wireless@vger.kernel.org
Cc: Dana R <dana.r.ferguson@intel.com>,
Dan Williams <dcbw@redhat.com>,
ipw3945-devel <ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 2.6.23.RC9] wpa_supplicant didn't work w/ wpa_secured hidden AP
Date: Wed, 10 Oct 2007 16:24:23 -0400 [thread overview]
Message-ID: <20071010202422.GN5962@tuxdriver.com> (raw)
In-Reply-To: <1192040814.12399.4.camel@abhi-desktop>
On Wed, Oct 10, 2007 at 11:26:54AM -0700, Abhijeet Kolekar wrote:
> This patch fixes the problem of associating with wpa_secured hidden
> ap.Please try out.
>
> The original author of this patch is Bill Moss<bmoss@clemson.edu>
>
> Signed-off-by: Abhijeet Kolekar <abhijeet.kolekar@intel.com>
Wow...that is one busted patch... Please avoid using editors that
convert tabs to whitespace. Probably also need to account for existing
IEEE80211_SCAN_MATCH_SSID behavior...?
Still, the general idea looks fine and I'd really like to make
wpa_supplicant and mac80211 work together with hidden APs. I'll fix-up
the patch and post it as a follow-up to this message...
John
P.S. Is limiting this to STA mode correct? Would wpa_supplicant
ever set that flag for an IBSS?
--
John W. Linville
linville@tuxdriver.com
next parent reply other threads:[~2007-10-10 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1192040814.12399.4.camel@abhi-desktop>
2007-10-10 20:24 ` John W. Linville [this message]
2007-10-11 8:42 ` [PATCH 2.6.23.RC9] wpa_supplicant didn't work w/ wpa_secured hidden AP Johannes Berg
2007-10-12 9:16 ` [ipw3945-devel] " dragoran
2007-10-12 12:51 ` John W. Linville
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=20071010202422.GN5962@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=abhijeet.kolekar@intel.com \
--cc=dana.r.ferguson@intel.com \
--cc=dcbw@redhat.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
/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.