From: Hugh Dickins <hugh.dickins@tiscali.co.uk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-wireless@vger.kernel.org
Subject: Re: 2.6.31-git wireless broken
Date: Thu, 24 Sep 2009 19:14:25 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0909241859020.25022@sister.anvils> (raw)
In-Reply-To: <1253813740.3868.324.camel@johannes.local>
Many thanks for your rapid response.
On Thu, 24 Sep 2009, Johannes Berg wrote:
> On Thu, 2009-09-24 at 18:18 +0100, Hugh Dickins wrote:
> >
> > I expect you'll need a lot more info from me: please do ask
> > (but bear in mind that I'm wireless and network ignorant).
>
> Thanks. I'm not sure why you'd get the warning there every few seconds,
> but I suppose we don't really care all that much.
>
> I think you're probably running afoul of a bugfix that I did while at
> the wireless summit, and then the fix to it made it in, but not yet the
> fix to the fix :(
>
> Are you using an encrypted network, or an open one?
I've been working under the belief that it's WPA encrypted.
> If it's open, can you try this patch?
But I could try the patch, in case I've been fooled.
> http://johannes.sipsolutions.net/patches/kernel/all/2009-09-24-17%3a32/010-cfg80211-fix-wpas-open.patch
However, all the trees I'm working with (Linus latest, or the bisect
result, or a week old mmotm) have cfg80211_mgd_wext_connect saying:
if (!netif_running(wdev->netdev))
return 0;
wdev->wext.connect.ie = wdev->wext.ie;
wdev->wext.connect.ie_len = wdev->wext.ie_len;
wdev->wext.connect.privacy = wdev->wext.default_key != -1;
if (wdev->wext.keys) {
wdev->wext.keys->def = wdev->wext.default_key;
wdev->wext.keys->defmgmt = wdev->wext.default_mgmt_key;
}
if (!wdev->wext.connect.ssid_len)
return 0;
which is not consistent with the fix your patch is making.
But I do believe I'm encrypted anyway.
Hugh
next prev parent reply other threads:[~2009-09-24 18:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 17:18 2.6.31-git wireless broken Hugh Dickins
2009-09-24 17:35 ` Johannes Berg
2009-09-24 18:14 ` Hugh Dickins [this message]
2009-09-24 18:23 ` Johannes Berg
2009-09-24 19:45 ` Hugh Dickins
2009-09-25 5:20 ` Johannes Berg
2009-09-25 8:06 ` Hugh Dickins
2009-09-25 8:43 ` Johannes Berg
2009-09-25 14:15 ` Hugh Dickins
2009-09-26 13:00 ` Johannes Berg
2009-09-26 14:03 ` Johannes Berg
2009-09-26 15:06 ` Sven-Haegar Koch
2009-09-26 15:33 ` Hugh Dickins
2009-09-27 11:08 ` Johannes Berg
2009-09-27 11:15 ` Johannes Berg
2009-09-26 15:31 ` Hugh Dickins
2009-09-26 15:58 ` Larry Finger
2009-09-25 8:45 ` Holger Schurig
2009-09-25 14:56 ` Christian Lamparter
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=Pine.LNX.4.64.0909241859020.25022@sister.anvils \
--to=hugh.dickins@tiscali.co.uk \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@sisk.pl \
/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