linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Steven Bateman <steven@fndtn.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: Issue with authentication to Aerohive APs
Date: Thu, 23 Jan 2014 16:59:02 +0100	[thread overview]
Message-ID: <1390492742.4142.35.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CF02A704.17362%steven@fndtn.com>

On Mon, 2014-01-20 at 16:27 +0000, Steven Bateman wrote:
> 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.

Ohh. Ok. Yeah then it's most likely a driver bug. Hmm. I vaguely
remember bugs like this but I thought they were all fixed.

Is there any chance you could try to put the particular AP into 2.4 GHz?
Although I guess you have similar APs on 2.4 GHz channels that work?
Could you (or the user actually running into the problem) collect
tracing maybe?
http://wireless.kernel.org/en/developers/Documentation/mac80211/tracing

johannes


  reply	other threads:[~2014-01-23 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 16:27 Issue with authentication to Aerohive APs Steven Bateman
2014-01-23 15:59 ` Johannes Berg [this message]
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=1390492742.4142.35.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=steven@fndtn.com \
    /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).