From: Dave <kilroyd@googlemail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [RFC 0/4] orinoco: use cfg80211 for key manipulation
Date: Fri, 07 Aug 2009 21:42:32 +0100 [thread overview]
Message-ID: <4A7C91B8.2010106@gmail.com> (raw)
In-Reply-To: <1249504372-17063-1-git-send-email-kilroyd@googlemail.com>
David Kilroy wrote:
> First attempt at connect/disconnect, join_ibss/leave_ibss, and add_key
> etc. These patches rely on the series I just sent, but conflict with
> Holgers set_channel patch. Simple to resolve, and I'll do that in my
> next update.
>
> This doesn't work yet*, but I've a number of questions.
FYI, I've got this kinda working with wpa_supplicant in wext mode.
First: on it's own wpa_supplicant keeps doing the 4 way handshake, while
cfg80211 pumps out the following:
------------[ cut here ]------------
WARNING: at net/wireless/sme.c:451 __cfg80211_roamed+0x9a/0x1a5 [cfg80211]()
Hardware name: Latitude C600
Modules linked in: orinoco_cs orinoco cfg80211 michael_mic snd_maestro3
aty128fb [last unloaded: cfg80211]
Pid: 5, comm: events/0 Tainted: G M W 2.6.31-rc4-wl #87
Call Trace:
[<c101ca51>] warn_slowpath_common+0x60/0x90
[<c101ca8e>] warn_slowpath_null+0xd/0x10
[<d1521659>] __cfg80211_roamed+0x9a/0x1a5 [cfg80211]
[<d15139a9>] cfg80211_event_work+0x104/0x1bc [cfg80211]
[<c102b39c>] worker_thread+0x15e/0x208
[<d15138a5>] ? cfg80211_event_work+0x0/0x1bc [cfg80211]
[<c102e5d5>] ? autoremove_wake_function+0x0/0x33
[<c102b23e>] ? worker_thread+0x0/0x208
[<c102e261>] kthread+0x66/0x6b
[<c102e1fb>] ? kthread+0x0/0x6b
[<c1003053>] kernel_thread_helper+0x7/0x10
---[ end trace 12e5dbe2024c37ae ]---
Cfg80211 is trying to select the bss we've authenticated against.
Unfortunately the BSS list is empty.
If before starting wpa_supplicant I run:
iw dev eth1 scan ssid <SSID>
Then wpa_supplicant connects fine. The AP in question is configured with
a hidden SSID.
Any suggestions as to how I need to address this?
Regards,
Dave.
next prev parent reply other threads:[~2009-08-07 20:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 20:32 [RFC 0/4] orinoco: use cfg80211 for key manipulation David Kilroy
2009-08-05 20:32 ` [RFC 1/4] orinoco: add cfg80211 connect and disconnect David Kilroy
2009-08-06 7:47 ` Johannes Berg
2009-08-05 20:32 ` [RFC 2/4] orinoco: add cfg80211 join_ibss and leave_ibss David Kilroy
2009-08-05 20:32 ` [RFC 3/4] orinoco: implement cfg80211 key manipulation functions David Kilroy
2009-08-05 20:32 ` [RFC 4/4] orinoco: do WE via cfg80211 David Kilroy
2009-08-06 7:40 ` [RFC 0/4] orinoco: use cfg80211 for key manipulation Johannes Berg
2009-08-06 17:34 ` Dave
2009-08-07 20:42 ` Dave [this message]
2009-08-07 21:23 ` Dan Williams
2009-08-07 21:38 ` Dave
2009-08-07 21:50 ` Johannes Berg
2009-08-07 21:54 ` 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=4A7C91B8.2010106@gmail.com \
--to=kilroyd@googlemail.com \
--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 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).