linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
Cc: Sujith Manoharan <sujith@msujith.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: start auth/assoc timeout on frame status
Date: Wed, 13 Feb 2013 17:13:33 +0100	[thread overview]
Message-ID: <1360772013.8868.27.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <511BB425.2030400@neratec.com>

On Wed, 2013-02-13 at 16:41 +0100, Wojciech Dubowik wrote:
> On 02/13/2013 04:36 PM, Sujith Manoharan wrote:
> > Wojciech Dubowik wrote:
> >> I don't see anymore timeouts. Sometimes station tries to authenticate,
> >> sends direct probe, timeouts and then goes again with auth message.
> > If you are using ath9k_rate_control, can you check if you still see the issue
> > with minstrel_ht ?
> I am using minstrel.
> 
> The above problem actually came from my  setup. I was using
> my hostpad with trial support for ap_scan=2, that's what I am
> trying to work on now. My test scripts are not very mature yet...
> 
> With stock hostapd and ap_scan=1 it seems to work quite
> fine.

Ok. Can I add your tested-by?

johannes


      reply	other threads:[~2013-02-13 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 13:28 [PATCH] mac80211: start auth/assoc timeout on frame status Johannes Berg
2013-02-04 15:43 ` Johannes Berg
2013-02-13 13:41   ` Wojciech Dubowik
2013-02-13 14:21     ` Johannes Berg
2013-02-13 14:23       ` Wojciech Dubowik
2013-02-13 14:32         ` Johannes Berg
2013-02-13 14:39           ` Johannes Berg
2013-02-13 15:20             ` Wojciech Dubowik
2013-02-13 15:36               ` Sujith Manoharan
2013-02-13 15:41                 ` Wojciech Dubowik
2013-02-13 16:13                   ` Johannes Berg [this message]

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=1360772013.8868.27.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Wojciech.Dubowik@neratec.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sujith@msujith.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).