From: Larry Finger <larry.finger@lwfinger.net>
To: Dan Williams <dcbw@redhat.com>
Cc: Michael Wu <flamingice@sourmilk.net>, linux-wireless@vger.kernel.org
Subject: WPA does not connect to bcm43xx-mac80211 when using NetworkManager
Date: Sun, 01 Apr 2007 22:50:17 -0500 [thread overview]
Message-ID: <46107D79.3060706@lwfinger.net> (raw)
In-Reply-To: <1175388624.10282.0.camel@localhost.localdomain>
Dan,
My bcm43xx-mac80211 system generates the following log entries when trying to connect using WPA-PSK
TKIP controlled by NetworkManager. The same configuration works with bcm43xx-softmac.
eth1: Initial auth_alg=0
eth1: authenticate with AP 00:14:bf:85:49:fa
eth1: RX authentication from 00:14:bf:85:49:fa (alg=0 transaction=2 status=0)
eth1: authenticated
eth1: associate with AP 00:14:bf:85:49:fa
eth1: RX AssocResp from 00:14:bf:85:49:fa (capab=0x31 status=0 aid=2)
eth1: associated
wmaster0: Added STA 00:14:bf:85:49:fa
eth1: RX deauthentication from 00:14:bf:85:49:fa (reason=15)
eth1: deauthenticated
eth1: set_encrypt - unknown addr 00:00:00:00:00:00
eth1: authenticate with AP 00:14:bf:85:49:fa
eth1: RX authentication from 00:14:bf:85:49:fa (alg=0 transaction=2 status=0)
eth1: authenticated
eth1: associate with AP 00:14:bf:85:49:fa
eth1: RX ReassocResp from 00:14:bf:85:49:fa (capab=0x31 status=0 aid=2)
eth1: associated
eth1: starting scan
It does the original open authentication and associates, but the final WPA authentication times out.
I'm using Michael Buesch's "mb" tree with the "mac80211: use IWEVGENIE" and "mac80211: set enc_capa"
patches by Michael Wu. My distro is openSUSE 10.2 on an x86_64 system.
Please advise on any further information I should provide.
Thanks,
Larry
next prev parent reply other threads:[~2007-04-02 3:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 9:36 mac80211 does not support WPA when used with wext dragoran
2007-03-31 10:00 ` Johannes Berg
2007-03-31 10:11 ` dragoran
2007-03-31 11:19 ` dragoran
2007-03-31 16:37 ` Michael Buesch
2007-03-31 16:39 ` Michael Buesch
2007-03-31 17:57 ` Dan Williams
2007-03-31 17:48 ` Dan Williams
2007-03-31 17:59 ` Jouni Malinen
2007-03-31 18:09 ` Larry Finger
2007-03-31 19:03 ` Michael Wu
[not found] ` <f6ca9fed0703311256m1b14ec35p836a62de532dd804@mail.gmail.com>
2007-03-31 21:00 ` Michael Wu
2007-04-01 0:50 ` Dan Williams
2007-04-02 3:50 ` Larry Finger [this message]
2007-04-02 4:12 ` WPA does not connect to bcm43xx-mac80211 when using NetworkManager Dan Williams
2007-04-03 14:26 ` Larry Finger
2007-04-02 5:26 ` Michael Wu
2007-04-01 8:18 ` mac80211 does not support WPA when used with wext Johannes Berg
[not found] ` <f6ca9fed0704081445u5536e596m4ca4caeb44f7f87@mail.gmail.com>
2007-04-08 21:54 ` Michael Wu
[not found] ` <f6ca9fed0704081527j641a4ecat44151e107cab7342@mail.gmail.com>
2007-04-10 7:13 ` dragoran
2007-04-10 12:25 ` Dan Williams
2007-04-10 14:34 ` dragoran dragoran
2007-04-10 14:39 ` Larry Finger
2007-04-10 14:44 ` dragoran dragoran
2007-04-01 0:55 ` Dan Williams
2007-04-01 1:21 ` Michael Wu
2007-04-01 4:51 ` 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=46107D79.3060706@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=flamingice@sourmilk.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 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).