From: Julian Wollrath <jwollrath@web.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: WARNING: at net/wireless/mlme.c:517
Date: Thu, 3 Jan 2013 10:31:50 +0100 [thread overview]
Message-ID: <20130103103150.21ed1269@ilfaris> (raw)
In-Reply-To: <50E467C4.6030602@lwfinger.net>
> I have not looked at detail at the debug listing, but I do have
> additional questions. None of your Emails on this subject mention
> anything about the AP. What make/model is it? What firmware is it
> running? Is it 802.11g or 802.11n? What are the details of the
> encryption? The device authenticates but is never able to associate
> after that.
One device is a NETGEAR WN3000RP and it uses WPA-PSK and TKIP as cipher
but similar problems accured at university where WPA2 is used and the
AP are probably not the same there (I can check it next monday). Here
is the output of "iw dev wlan0 scan", which hopefully answers your
questions which I did not answer above:
BSS xx:xx:xx:xx:xx:xx (on wlan0)
freq: 2462
beacon interval: 100
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -48.00 dBm
last seen: 143 ms ago
Information elements from Probe Response frame:
SSID: xxx
Supported rates: 1.0* 2.0* 5.5 11.0 18.0 24.0 36.0 54.0
DS Parameter set: channel 11
ERP: Use_Protection Barker_Preamble_Mode
Extended supported rates: 6.0 9.0 12.0 48.0
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Selected Registrar: 0x0
* Response Type: 3 (AP)
* UUID: xxx
* Manufacturer: NETGEAR, Inc.
* Model: WN3000RP
* Model Number: WN3000RP
* Serial Number: 01
* Primary Device Type: 6-0050f204-1
* Device name: WN3000RP
* Config methods: Label, PBC
* RF Bands: 0x1
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP
* Authentication suites: PSK
* Capabilities: 16-PTKSA-RC (0x000c)
WMM: * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
If it does not answer all of your questions, a hint, how to find the
answers without access (physical or otherwise) to the AP would be
appreciated.
With best regards,
Julian
next prev parent reply other threads:[~2013-01-03 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 14:45 WARNING: at net/wireless/mlme.c:517 Julian Wollrath
2013-01-01 18:06 ` Larry Finger
2013-01-01 22:15 ` Julian Wollrath
2013-01-01 22:28 ` Larry Finger
2013-01-02 11:00 ` Julian Wollrath
2013-01-02 17:00 ` Larry Finger
2013-01-03 9:31 ` Julian Wollrath [this message]
2013-01-07 15:06 ` Julian Wollrath
2013-01-04 13:30 ` Johannes Berg
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=20130103103150.21ed1269@ilfaris \
--to=jwollrath@web.de \
--cc=Larry.Finger@lwfinger.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).