You are not logged in.
On my Thinkpad running Arch Linux, I experience problems with our WiFi network, which otherwise works fine. After connecting it usually works for a couple of minutes, then fails. NetworkManager claims it's still connected but I cannot transfer data, in fact even pinging the router fails. In such a situation, dis- and then reconnecting helps sometimes.
In the messages.log file, I find frequent blocks like this one:
Jan 1 20:03:59 localhost kernel: [11075.229049] cfg80211: Calling CRDA to update world regulatory domain
Jan 1 20:03:59 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: completed -> disconnected
Jan 1 20:03:59 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Jan 1 20:04:03 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: scanning -> associating
Jan 1 20:04:03 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: associating -> associated
Jan 1 20:04:04 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Jan 1 20:04:06 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: 4-way handshake -> group handshake
Jan 1 20:04:06 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: group handshake -> completed
Any ideas? Even just how to debug, I'm a bit clueless...
Thanks,
Alex
Offline
In the messages.log file, I find frequent blocks like this one:
Jan 1 20:03:59 localhost kernel: [11075.229049] cfg80211: Calling CRDA to update world regulatory domain
Jan 1 20:03:59 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: completed -> disconnected
Jan 1 20:03:59 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Jan 1 20:04:03 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: scanning -> associating
Jan 1 20:04:03 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: associating -> associated
Jan 1 20:04:04 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Jan 1 20:04:06 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: 4-way handshake -> group handshake
Jan 1 20:04:06 localhost NetworkManager[743]: <info> (wlan0): supplicant interface state: group handshake -> completed
I don't use NetworkManager, so I'm just guessing here, but when I read your log block, it seems to say that first a disconnection happens (maybe as a result of your CRDA having problems?), then NM reconnects, but maybe it doesn't re-run DHCPCD or dhclient?
Offline
I have the exact same problem described here and it's getting a little bit annoying... My WiFi card is the Intel WiFi Link 5100 AGN.
There's something I can do to help with this problem? I've never debugged anything, maybe is time for the first-time.
Regards
Offline
I'm experiencing the same problems. Been connected to various networks today, maybe it's a problem with WEP ?
At home I'm using WPA2 without a problem. Can you confirm that you're having problems with such networks ?
PS
On WEP networks killing NetworkManager and configuring ESS and KEY via iwconfig, bringing wlan0 up and running dhcpcd on it seems to help - looks like a problem with NM itself.
Offline
I'm experiencing the same problems. Been connected to various networks today, maybe it's a problem with WEP ?
At home I'm using WPA2 without a problem. Can you confirm that you're having problems with such networks ?
PS
On WEP networks killing NetworkManager and configuring ESS and KEY via iwconfig, bringing wlan0 up and running dhcpcd on it seems to help - looks like a problem with NM itself.
In my home I'm using WPA Personal and I'm having this issue, also, I tried installing wicd but the problem persist... I'm lost here...
Regards
Last edited by AurosGamma (2012-01-03 17:02:44)
Offline
What about if you disable all network managers and just use wpa_supplicant + dhcpcd?
Offline
Let's just make sure we all have the same issue. I have frequent blocks like the one below show up in dmesg:
[ 430.871250] wlan0: deauthenticated from 00:23:f8:0f:ef:bf (Reason: 1)
[ 430.930161] cfg80211: Calling CRDA to update world regulatory domain
[ 434.235766] wlan0: authenticate with 00:23:f8:0f:ef:bf (try 1)
[ 434.237999] wlan0: authenticated
[ 434.240386] wlan0: associate with 00:23:f8:0f:ef:bf (try 1)
[ 434.244496] wlan0: RX ReassocResp from 00:23:f8:0f:ef:bf (capab=0x471 status=0 aid=3)
[ 434.244499] wlan0: associated
My gut feeling is that it's a driver issue.
Offline
Well, I changed my router's security mode from WPA Personal TKIP to WPA2 Personal AES and looks like the problem is gone... This is a little weird, but I still want to help. Anyway, maybe is a driver problem (anybody can confirm this?), so we'll have to wait until the kernel developers fix this...
Regards
Offline
I have the exact same problem described here and it's getting a little bit annoying... My WiFi card is the Intel WiFi Link 5100 AGN.
There's something I can do to help with this problem? I've never debugged anything, maybe is time for the first-time.Regards
Similar problem here with the same card (Intel WiFi Link 5100 AGN).
My network connection on my laptop periodically stops and to restore it I have to restart networkmanager daemon.
On wired connection everything is OK.
May be I have to buy another wifi card.
Offline
May be I have to buy another wifi card.
.. Or try downgrading the kernel or just give it a bit more time. It seems to be a frequent error that is looked into.
Offline
Kernel 3.1.8 has what looked like quite an important iwlwifi fix, probably 3.2 has it as well. So, a bit of patience. And Strike0 is fully correct, buying a new card is way overkill when there's solutions that don't involve spending money.
Offline