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. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
