On Tue, Sep 02, 2008 at 09:38:56AM +0800, Zhu Yi wrote: > On Mon, 2008-09-01 at 19:07 +0300, Michael S. Tsirkin wrote: > > [16482.909453] eth1: associate with AP XX:XX:XX:XX:XX:XX > > [16482.918553] eth1: RX ReassocResp from XX:XX:XX:XX:XX:XX > > (capab=0x411 status=0 aid=1) > > [16482.918564] eth1: associated > > [16492.920224] eth1: disassociating by local choice (reason=3) > > [16492.920986] eth1: disassociating by local choice (reason=3) > > It is exactly 10 seconds the local STA sends the deauth_leaving frame > before associated everytime. I wonder if it is the timeout for some > wireless config tools. NM? Not network manager, I'm using wpa_supplicant. > What did you do to make it reassociate after resume? If you are using > some automatic config tools, I think that resume scripts try to do is up the interface, and network scripts run wpa supplicant (or rather, wpa_cli which talks to wpa_supplicant). Same thing happens if I run wpa_supplicant manually as well. > can you try iwconfig manually instead? > > Thanks, > -yi I could try, but I have wpa ... -- MST -- 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
