All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Albert <jal2@gmx.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: mac80211: reassociate in STA mode after AP was power-cycled
Date: Fri, 21 Aug 2009 23:11:41 +0200	[thread overview]
Message-ID: <4A8F0D8D.7000508@gmx.de> (raw)

I had a ar9170usb device in STA mode associated to an AP and power-cycled the AP - slowly enough to get the
STA disassociated. 

I wonder why the STA doesn't re-associate again to the AP once it's up again. Waited for 5+ minutes.

I see the AP in the output of "iwlist wlan1 scan" and after "ifconfig wlan1 down; ifconfig wlan1 up"
the STA associates quickly.

wireless-testing from today, v2.6.31-rc6-31653-g0dfdb6f.

Some lines from syslog, between "ifconfig wlan1 up" and powering off the AP:

Aug 21 22:55:33 nc10 kernel: [ 1854.824443] wlan1: direct probe to AP 00:30:f1:d5:2e:69 (try 1)
Aug 21 22:55:33 nc10 kernel: [ 1854.826914] wlan1 direct probe responded
Aug 21 22:55:33 nc10 kernel: [ 1854.826930] wlan1: authenticate with AP 00:30:f1:d5:2e:69 (try 1)
Aug 21 22:55:33 nc10 kernel: [ 1854.830003] wlan1: authenticated
Aug 21 22:55:33 nc10 kernel: [ 1854.837585] wlan1: associate with AP 00:30:f1:d5:2e:69 (try 1)
Aug 21 22:55:33 nc10 kernel: [ 1854.839656] wlan1: RX AssocResp from 00:30:f1:d5:2e:69 (capab=0x421 status=0 aid=5)
Aug 21 22:55:33 nc10 kernel: [ 1854.839670] wlan1: associated
Aug 21 22:55:33 nc10 kernel: [ 1854.847296] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Aug 21 22:55:45 nc10 kernel: [ 1867.500169] No probe response from AP 00:30:f1:d5:2e:69 after 500ms, disconnecting.

Regards,
Jörg.

             reply	other threads:[~2009-08-21 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 21:11 Joerg Albert [this message]
2009-08-21 21:23 ` mac80211: reassociate in STA mode after AP was power-cycled Johannes Berg
2009-08-21 23:15   ` Joerg Albert

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=4A8F0D8D.7000508@gmx.de \
    --to=jal2@gmx.de \
    --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.