From: Steven Bateman <steven@fndtn.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: Issue with authentication to Aerohive APs
Date: Mon, 20 Jan 2014 16:27:22 +0000 [thread overview]
Message-ID: <CF02A704.17362%steven@fndtn.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]
You're right, I did accidentally filter out acks. I have an updated
filtered capture attached.
It could be either, but I'm going off of wpa_supplicant instructing to
transmit the 2nd EAPOL frame, but it never showing up in the air. The
consultations I've received so far indicated that it would more likely be
a driver/firmware issue, but I don't have enough experience with Linux
supplicants to be sure about that.
Steve Bateman
Wireless Engineer
________________________________________
The FoundationGet Back To Work.
311 North 7th Avenue
Minneapolis, MN 55401
612.465.0700 Main
612.787.3202 Direct
612.338.9322 Faxhttp://www.fndtn.com <http://www.fndtn.com/>
Facebook <http://www.facebook.com/thefndtn> | Twitter
<http://twitter.com/thefndtn> | LinkedIn
<http://www.linkedin.com/companies/276539>
On 1/20/14 4:33 AM, "Johannes Berg" <johannes@sipsolutions.net> wrote:
>On Thu, 2014-01-09 at 19:13 +0000, Steven Bateman wrote:
>
>> I'm writing on behalf of about 4 or 5 users that are having issues
>> connecting to a WLAN that I manage. The majority of the information can
>>be
>> found at the following link, including relevant logs. I've enclosed the
>> packet capture from next to the station with failed authentications.
>
>How did you capture/filter the attached file? It shows no
>acknowledgement of the EAPOL packets, but no retries either, so you
>probably filtered out the acknowledgements. That leads me to believe
>that maybe there was something wrong with those EAPOL frames, maybe
>wpa_supplicant didn't get or didn't expect them?
>
>What makes you so sure it's a driver/firmware bug rather than a bug
>related to wpa_supplicant or interaction with it?
>
>johannes
>
[-- Attachment #2: bf4a73 updated.pcap --]
[-- Type: application/octet-stream, Size: 10990 bytes --]
next reply other threads:[~2014-01-20 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 16:27 Steven Bateman [this message]
2014-01-23 15:59 ` Issue with authentication to Aerohive APs Johannes Berg
2014-01-24 2:28 ` Liu, Bopeng
2014-01-24 7:28 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2014-01-09 19:36 Steven Bateman
2014-01-09 19:52 ` 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=CF02A704.17362%steven@fndtn.com \
--to=steven@fndtn.com \
--cc=johannes@sipsolutions.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).