Skip to contentSkip to conversation

2.6.29+ ath5k connect disconnect cycles?

DISCUSSION Soeren Sonnenburg 4 participants 8 messages Apr 6, 2009 – Apr 9, 2009

lore
Share & tools
lore
#0 lore raw

Dear all,

does anyone else observer strange connect disconnect cycles with ath5k? I have two different notebooks here one with an AR5414 and one with some 2424 (?) chipset both having the same problems to connect...

Soeren

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
#1 lore raw
Quoted 3 lines · Soeren Sonnenburg

does anyone else observer strange connect disconnect cycles with ath5k? I have two different notebooks here one with an AR5414 and one with some 2424 (?) chipset both having the same problems to connect...

Hello Soeren,

Is there any information from dmesg?

Signature · 1 line
Tulio Magno
#2 lore raw
Quoted 8 lines · Tulio Magno Quites Machado Filho
Quoted 3 lines · Soeren Sonnenburg

does anyone else observer strange connect disconnect cycles with ath5k? I have two different notebooks here one with an AR5414 and one with some 2424 (?) chipset both having the same problems to connect...

Hello Soeren,

Is there any information from dmesg?

I am seeing cycles of

airport: deauthenticated (Reason: 2)
airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1
airport direct probe responded
airport: authenticate with AP XX:XX:XX:XX:XX:XX
airport: authenticated
airport: associate with AP XX:XX:XX:XX:XX:XX
airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0 aid=79)
airport: associated
airport: deauthenticated (Reason: 2)
airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1
airport direct probe responded
airport: authenticate with AP XX:XX:XX:XX:XX:XX
airport: authenticated
airport: associate with AP XX:XX:XX:XX:XX:XX
airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0 aid=81)
airport: associated
airport: deauthenticated (Reason: 2)
airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1
airport direct probe responded
airport: authenticate with AP XX:XX:XX:XX:XX:XX
airport: authenticated
airport: associate with AP XX:XX:XX:XX:XX:XX
airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0 aid=82)
airport: associated
airport: deauthenticated (Reason: 2)
...

Not sure about the involvement of network-manager here... but I see that the device gets a valid IP via dhcp.

Soeren

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
#3 lore raw
Quoted 46 lines
Quoted 2 lines · Tulio Magno Quites Machado Filho
Quoted 1 line · Soeren Sonnenburg

does anyone else observer strange connect disconnect cycles with

ath5k?

Quoted 1 line
Quoted 1 line

I have two different notebooks here one with an AR5414 and one with

some

Quoted 5 lines
Quoted 1 line

2424 (?) chipset both having the same problems to connect...

Hello Soeren,

Is there any information from dmesg?

I am seeing cycles of

airport: deauthenticated (Reason: 2)
airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1 airport direct probe responded
airport: authenticate with AP XX:XX:XX:XX:XX:XX
airport: authenticated
airport: associate with AP XX:XX:XX:XX:XX:XX
airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0 aid=79)
airport: associated
airport: deauthenticated (Reason: 2)
airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1 airport direct probe responded
airport: authenticate with AP XX:XX:XX:XX:XX:XX
airport: authenticated
airport: associate with AP XX:XX:XX:XX:XX:XX
airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0 aid=81)
airport: associated
airport: deauthenticated (Reason: 2)
airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1 airport direct probe responded
airport: authenticate with AP XX:XX:XX:XX:XX:XX
airport: authenticated
airport: associate with AP XX:XX:XX:XX:XX:XX
airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0 aid=82)
airport: associated
airport: deauthenticated (Reason: 2)
...

Quoted 3 lines

Not sure about the involvement of network-manager here... but I see that the device gets a valid IP via dhcp.

I've seen such cycles also with intel ipw5300 WLAN and using ifconfig to start the network. To get WLAN working again, I have to ifdown wlan0 , unload and reload the driver module and finally ifup wlan0. So it's probably neither a ath5k nor a network-manager problem.

#4 lore raw
Quoted 6 lines · Markus Koßmann
Quoted 6 lines
Quoted 2 lines · Tulio Magno Quites Machado Filho
Quoted 1 line · Soeren Sonnenburg

does anyone else observer strange connect disconnect cycles with

ath5k?

Quoted 1 line
Quoted 1 line

I have two different notebooks here one with an AR5414 and one with

Quoted 8 lines
Quoted 8 lines

some

Quoted 5 lines
Quoted 1 line

2424 (?) chipset both having the same problems to connect...

Hello Soeren,

Is there any information from dmesg?

I am seeing cycles of

[connecting and reconnecting]

Quoted 4 lines
Quoted 3 lines

Not sure about the involvement of network-manager here... but I see that the device gets a valid IP via dhcp.

I've seen such cycles also with intel ipw5300 WLAN and using ifconfig to start the network. To get WLAN working again, I have to ifdown wlan0 , unload and reload the driver module and finally ifup wlan0. So it's probably neither a ath5k nor a network-manager problem.

A rmmod ath5k / reload didn't help in my case.

Soeren

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
#5 lore raw
In reply to Soeren Sonnenburg
Quoted 7 lines · Soeren Sonnenburg

Dear all,

does anyone else observer strange connect disconnect cycles with ath5k? I have two different notebooks here one with an AR5414 and one with some 2424 (?) chipset both having the same problems to connect...

Soeren

I use latest -git of wireless-testing, and AR2425.
Thanks to hard work of ath5k developers, it works better and better. Yet phy seems to die when loaded with traffic, but its reset brings is back alive. ath5k does a reset every 10 seconds.

If you use WPA, then you might have bigger problems, I mean, during the period when phy is dead, AP might ask for group rekey, but ath5k won't hear this, and continue using old keys. This causes much longer delays, and sometimes reconnect cycles you see.

Best regards,
Maxim Levitsky

#6 lore raw
Quoted 14 lines · Maxim Levitsky
Quoted 7 lines · Soeren Sonnenburg

Dear all,

does anyone else observer strange connect disconnect cycles with ath5k? I have two different notebooks here one with an AR5414 and one with some 2424 (?) chipset both having the same problems to connect...

Soeren

I use latest -git of wireless-testing, and AR2425.
Thanks to hard work of ath5k developers, it works better and better. Yet phy seems to die when loaded with traffic, but its reset brings is back alive. ath5k does a reset every 10 seconds.

Quoted 4 lines

If you use WPA, then you might have bigger problems, I mean, during the period when phy is dead, AP might ask for group rekey, but ath5k won't hear this, and continue using old keys. This causes much longer delays, and sometimes reconnect cycles you see.

Unfortunately, this happened with a open network. But YMMV as it seems to work very reliably in other locations (even with WPA)... with both the 2425 and 5414 chipset.

Soeren

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
#7 lore raw
In reply to Maxim Levitsky
Quoted 14 lines · Maxim Levitsky
Quoted 7 lines · Soeren Sonnenburg

Dear all,

does anyone else observer strange connect disconnect cycles with ath5k? I have two different notebooks here one with an AR5414 and one with some 2424 (?) chipset both having the same problems to connect...

Soeren

I use latest -git of wireless-testing, and AR2425.
Thanks to hard work of ath5k developers, it works better and better. Yet phy seems to die when loaded with traffic, but its reset brings is back alive. ath5k does a reset every 10 seconds.

Quoted 4 lines

If you use WPA, then you might have bigger problems, I mean, during the period when phy is dead, AP might ask for group rekey, but ath5k won't hear this, and continue using old keys. This causes much longer delays, and sometimes reconnect cycles you see.

Unfortunately, this happened with an open network. But YMMV as it seems to work very reliably in other locations (even with WPA)... with both the 2425 and 5414 chipset.

Soeren

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962