From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org
Subject: Re: Problem authenticating using WPA with bcm43xx-softmac
Date: Sun, 11 Jun 2006 20:11:31 -0500 [thread overview]
Message-ID: <448CBF43.6000200@lwfinger.net> (raw)
In-Reply-To: <1149867292.3864.30.camel@johannes.berg>
Johannes Berg wrote:
> On Fri, 2006-06-09 at 10:31 -0500, Larry Finger wrote:
>
>> Do you mean a special dump, or is the kernel debug output and wpa_supplicant debug output sufficient?
>
> I was thinking of packet dumps but earlier you said you couldn't create
> any so I'm out of ideas for now.
I was finally able to get my second laptop running with bcm43xx so I could get packet dumps. When I
analyzed them, the Association Response packet contained the following information:
"Association denied due to requesting station not supporting short preamble operation (0x0013)"
I think this is a bug in the code on my WRT54G V5 and I will report it to Linksys; however, in the
meantime, I am able to connect using the following _ugly_ hack to softmac_assoc_req and
softmac_reassoc_req:
diff --git a/net/ieee80211/softmac/ieee80211softmac_io.c b/net/ieee80211/softmac/ieee80211softmac_io.c
index cc6cd56..a1d0c10 100644
--- a/net/ieee80211/softmac/ieee80211softmac_io.c
+++ b/net/ieee80211/softmac/ieee80211softmac_io.c
@@ -199,6 +199,8 @@ ieee80211softmac_assoc_req(struct ieee80
(*pkt)->capability |= mac->ieee->short_slot ?
cpu_to_le16(WLAN_CAPABILITY_SHORT_SLOT_TIME) : 0;
*/
+ /* add short preamble operation capability */
+ (*pkt)->capability |= cpu_to_le16(WLAN_CAPABILITY_SHORT_PREAMBLE);
(*pkt)->capability |= mac->ieee->sec.level ? cpu_to_le16(WLAN_CAPABILITY_PRIVACY) : 0;
/* Fill in Listen Interval (?) */
(*pkt)->listen_interval = cpu_to_le16(10);
@@ -247,6 +249,8 @@ ieee80211softmac_reassoc_req(struct ieee
(*pkt)->capability |= mac->ieee->short_slot ?
cpu_to_le16(WLAN_CAPABILITY_SHORT_SLOT_TIME) : 0;
*/
+ /* add short preamble operation capability */
+ (*pkt)->capability |= cpu_to_le16(WLAN_CAPABILITY_SHORT_PREAMBLE);
(*pkt)->capability |= mac->ieee->sec.level ?
cpu_to_le16(WLAN_CAPABILITY_PRIVACY) : 0;
I expect that softmac should be listening to the driver as to whether this capability is available;
however, I'm now up and running once again.
Larry
next prev parent reply other threads:[~2006-06-12 1:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 19:24 Problem authenticating using WPA with bcm43xx-softmac Larry Finger
2006-06-07 12:10 ` Johannes Berg
2006-06-07 15:47 ` Larry Finger
2006-06-07 15:51 ` Johannes Berg
2006-06-07 15:57 ` Johannes Berg
2006-06-07 17:29 ` Dan Williams
2006-06-07 18:12 ` Larry Finger
2006-06-07 19:36 ` Dan Williams
2006-06-07 19:46 ` Larry Finger
2006-06-09 11:44 ` Johannes Berg
2006-06-09 15:31 ` Larry Finger
2006-06-09 15:34 ` Johannes Berg
2006-06-09 16:24 ` Larry Finger
2006-06-12 1:11 ` Larry Finger [this message]
2006-06-13 8:40 ` Johannes Berg
2006-06-07 16:01 ` Sam Leffler
2006-06-07 16:06 ` Johannes Berg
2006-06-07 16:30 ` Larry Finger
2006-06-07 17:07 ` Larry Finger
2006-06-07 16:09 ` Larry Finger
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=448CBF43.6000200@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=netdev@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).