All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Steven Bateman <steven@fndtn.com>,
	Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: FW: Issue with authentication to Aerohive APs
Date: Thu, 09 Jan 2014 13:29:44 -0600	[thread overview]
Message-ID: <52CEF8A8.2050803@lwfinger.net> (raw)
In-Reply-To: <CEF450DF.167F3%steven@fndtn.com>

On 01/09/2014 01:13 PM, Steven Bateman wrote:
> From: Steven Bateman <steven@fndtn.com>
> Date: Thursday, January 9, 2014 11:34 AM
> To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
> "ilw@linux.intel.com"
>   <ilw@linux.intel.com>
> Subject: Issue with authentication to Aerohive APs
>
>
>
>
> Hello,
>
>
> 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.
>
> http://community.aerohive.com/aerohive/topics/issue_with_linux_connectivity
> _in_a_high_density_wlan
>
> We seem to have narrowed it down to a possible driver or firmware bug, but
> I'm reliant on the user to provide me requested information. At the moment
> I'm requesting that the user upgrade or downgrade his firmware or kernel in
>   case that changes the behavior.
>
> I'd like to submit this to this group for review, and to see if you can
> elucidate what might be happening so I that I can work towards a solution
> with these users.
>

For completeness, what device/driver pair(s) and kernel versions are the Linux 
user(s) running?

Larry


  reply	other threads:[~2014-01-09 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CEF439BF.167DB%steven@fndtn.com>
     [not found] ` <CEF44F30.167EB%steven@fndtn.com>
2014-01-09 19:13   ` FW: Issue with authentication to Aerohive APs Steven Bateman
2014-01-09 19:29     ` Larry Finger [this message]
2014-01-20 10:33     ` 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=52CEF8A8.2050803@lwfinger.net \
    --to=larry.finger@lwfinger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.