All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Association often fails first time when roaming with 802.11r.
Date: Tue, 12 Nov 2013 17:23:59 -0800	[thread overview]
Message-ID: <5282D4AF.7070704@candelatech.com> (raw)
In-Reply-To: <5282AA36.2070703@candelatech.com>

On 11/12/2013 02:22 PM, Ben Greear wrote:

> I think it must have something to do with the ath9k driver resetting
> itself or maybe going to sleep when it notices no other stations are associated.  If I add
> a second station (in this case, I am roaming between two APs on the
> same channel), then the roam time is reliably < 50ms, usually around 40ms.
> 
> When I have a single station, I see kernel logs such as this
> below (I added timestamps to logging messages).
> 
> I'm dropping hostapd mailing from any further replies, as this does not
> seem to be an issue with it's logic...


Oh, my...found the problem.

I had serial console logging on, and all those extra regulatory messages makes
the difference :P

Disabled serial console and now it roams in about 13-14ms :P

/me slaps self in head with wet fish.

Thanks,
Ben



-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2013-11-13  1:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 19:36 Association often fails first time when roaming with 802.11r Ben Greear
2013-11-12 19:46 ` Johannes Berg
2013-11-12 20:05   ` Ben Greear
2013-11-12 20:10     ` Johannes Berg
2013-11-12 20:36       ` Ben Greear
2013-11-12 22:22         ` Ben Greear
2013-11-13  1:23           ` Ben Greear [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=5282D4AF.7070704@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=hostap@lists.shmoo.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 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.