Wireless connection frequently drops [deauthenticating by local choice (reason=3)]

[joshuadugie]

Since about 8.04 or 8.10, perhaps when Ubuntu switched over to NetworkManager, my wireless connection has randomly dropped its association with the access point, about every ten minutes. For a while, the connection will just die, then it will be detected and NetworkManager will re-authenticate and re-associate.

In Lucid Lynx, this problem is now much more frequent (often exactly every two or four minutes) and now Ubuntu does not report that the connection has dropped. Instead, it re-associates in the background, eventually connecting to the access point again, all behind the scenes. Thus, the only thing that has changed, aside from the greater frequency, is that Ubuntu now doesn't report that it has dropped the connection, which seems deceptive from previous versions.

This may be the same bug as bug 429035, but my dmesg output is a bit different. This problem occurs primarily on a WPA2 Enterprise network, but the problem has occurred on other network security configurations as well.

dmesg output after many instances of disconnects:

[ 5423.541343] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5425.134984] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5425.174916] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
[ 5425.177083] wlan0: direct probe responded
[ 5425.177087] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
[ 5425.179379] wlan0: authenticated
[ 5425.179399] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
[ 5425.182881] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=68)
[ 5425.182884] wlan0: associated
[ 5437.562165] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:17:bd:41 tid = 0
[ 5480.893417] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5482.475859] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5482.515034] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
[ 5482.517187] wlan0: direct probe responded
[ 5482.517190] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
[ 5482.518636] wlan0: authenticated
[ 5482.518651] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
[ 5482.522378] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=68)
[ 5482.522381] wlan0: associated
[ 5508.093339] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5508.107358] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
[ 5508.107412] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5508.110595] wlan0: direct probe to AP 00:26:cb:16:e8:d1 (try 1)
[ 5508.113114] wlan0: direct probe responded
[ 5508.113123] wlan0: authenticate with AP 00:26:cb:16:e8:d1 (try 1)
[ 5508.115392] wlan0: authenticated
[ 5508.121973] wlan0: associate with AP 00:26:cb:16:e8:d1 (try 1)
[ 5508.127254] wlan0: RX AssocResp from 00:26:cb:16:e8:d1 (capab=0x431 status=0 aid=16)
[ 5508.127262] wlan0: associated
[ 5525.110100] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:16:e8:d1 tid = 0
[ 5546.029401] wlan0: deauthenticating from 00:26:cb:16:e8:d1 by local choice (reason=3)
[ 5546.042276] wlan0: direct probe to AP 00:26:cb:16:e8:d1 (try 1)
[ 5546.042311] wlan0: deauthenticating from 00:26:cb:16:e8:d1 by local choice (reason=3)
[ 5546.045656] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
[ 5546.048069] wlan0: direct probe responded
[ 5546.048077] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
[ 5546.049864] wlan0: authenticated
[ 5546.077267] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
[ 5546.080885] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=79)
[ 5546.080888] wlan0: associated
[ 5562.875489] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:17:bd:41 tid = 0
[ 5571.881150] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5571.928466] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5571.967725] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
[ 5571.969866] wlan0: direct probe responded
[ 5571.969870] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
[ 5571.971428] wlan0: authenticated
[ 5571.971446] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
[ 5571.974650] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=79)
[ 5571.974658] wlan0: associated
[ 5579.266995] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:17:bd:41 tid = 0
[ 5674.773488] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5674.815768] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5674.855855] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
[ 5674.858186] wlan0: direct probe responded
[ 5674.858195] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
[ 5674.859768] wlan0: authenticated
[ 5674.859811] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
[ 5674.863242] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=79)
[ 5674.863249] wlan0: associated
[ 5693.936473] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:17:bd:41 tid = 0
[ 5871.177501] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5872.845146] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 5872.884514] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
[ 5872.886671] wlan0: direct probe responded
[ 5872.886679] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
[ 5872.888855] wlan0: authenticated
[ 5872.888902] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
[ 5872.892134] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=79)
[ 5872.892142] wlan0: associated
[ 6091.564428] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:17:bd:41 tid = 0
[ 6122.697260] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 6124.304877] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 6124.344923] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
[ 6124.347041] wlan0: direct probe responded
[ 6124.347043] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
[ 6124.348599] wlan0: authenticated
[ 6124.348624] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
[ 6124.352604] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=79)
[ 6124.352609] wlan0: associated
[ 6129.588373] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:17:bd:41 tid = 0
[ 6246.053521] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 6246.089232] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice (reason=3)
[ 6246.129301] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
[ 6246.131530] wlan0: direct probe responded
[ 6246.131540] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
[ 6246.133188] wlan0: authenticated
[ 6246.133229] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
[ 6246.136579] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 status=0 aid=79)
[ 6246.136586] wlan0: associated

[Nirav Patel (nrpatel)]

I'm seeing this as well in: 2.6.32-17-generic #26-Ubuntu SMP Sat Mar 20 02:23:45 UTC 2010 x86_64 GNU/Linux

[Peter Antoniac (pan1nx)]

Thank you for helping and reporting this. However, we need extra information to aid in finding the solution:
Is this solved with the new kernel? 2.6.31-20. Does the new backport modules help?

Thank you!

[joshuadugie (joshuadugie)]

It appears the new kernel (2.6.32-18-generic) does fix the problem. Thank you!

dmesg output:

[ 30.092151] wlan0: no IPv6 routers present
[ 58.292308] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:a0:a3:f1 tid = 0
[ 59.720079] wlan0: deauthenticating from 00:26:cb:a0:a3:f1 by local choice (reason=3)
[ 59.733311] wlan0: direct probe to AP 00:26:cb:a0:a3:f1 (try 1)
[ 59.733318] wlan0: deauthenticating from 00:26:cb:a0:a3:f1 by local choice (reason=3)
[ 59.741022] wlan0: direct probe to AP 00:26:cb:a0:a3:fe (try 1)
[ 59.940041] wlan0: direct probe to AP 00:26:cb:a0:a3:fe (try 2)
[ 59.940858] wlan0: direct probe responded
[ 59.940861] wlan0: authenticate with AP 00:26:cb:a0:a3:fe (try 1)
[ 59.941439] wlan0: authenticated
[ 59.941457] wlan0: associate with AP 00:26:cb:a0:a3:fe (try 1)
[ 59.943285] wlan0: RX AssocResp from 00:26:cb:a0:a3:fe (capab=0x11 status=0 aid=8)
[ 59.943287] wlan0: associated
[ 67.519961] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:a0:a3:fe tid = 0
[ 108.432059] CE: hpet increasing min_delta_ns to 15000 nsec
[ 159.753388] wlan0: deauthenticating from 00:26:cb:a0:a3:fe by local choice (reason=3)
[ 159.766434] wlan0: deauthenticating from 00:26:cb:a0:a3:fe by local choice (reason=3)
[ 159.772078] wlan0: direct probe to AP 00:26:cb:a0:a3:f1 (try 1)
[ 159.776701] wlan0: direct probe responded
[ 159.776708] wlan0: authenticate with AP 00:26:cb:a0:a3:f1 (try 1)
[ 159.778191] wlan0: authenticated
[ 159.801433] wlan0: associate with AP 00:26:cb:a0:a3:f1 (try 1)
[ 159.804965] wlan0: RX AssocResp from 00:26:cb:a0:a3:f1 (capab=0x431 status=0 aid=82)
[ 159.804971] wlan0: associated
[ 194.378493] iwlagn 0000:0b:00.0: iwl_tx_agg_start on ra = 00:26:cb:a0:a3:f1 tid = 0
[ 410.835396] CE: hpet increasing min_delta_ns to 22500 nsec
   -- end --

(I am currently at [3000.000000] right now with no problems.)

[Benjamin Zeller (zeller-benjamin)]

I'm seeing this problem too on kernel with WPA2 security (no enterprise):
Linux version 2.6.31-20-generic

My network card is: Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection

My wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=2

network={
        ssid="WLAN-1AFE02"
        psk=<some very long hexvalue>
        scan_ssid=1
        proto=RSN
        key_mgmt=WPA-PSK
        pairwise=CCMP
        group=TKIP
}

From dmesg:

[ 4539.906494] wlan0: associate with AP 00:1a:2a:1a:fe:0c (try 1)
[ 4539.923039] wlan0: RX AssocResp from 00:1a:2a:1a:fe:0c (capab=0x431 status=0 aid=1)
[ 4539.923042] wlan0: associated
[ 4545.020065] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=17)
[ 4545.020140] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=3)
[ 4545.060811] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=3)
[ 4545.061325] wlan0: direct probe to AP 00:1a:2a:1a:fe:0c (try 1)
[ 4545.075888] wlan0: direct probe responded
[ 4545.075892] wlan0: authenticate with AP 00:1a:2a:1a:fe:0c (try 1)
[ 4545.082269] wlan0: authenticated
[ 4545.082286] wlan0: associate with AP 00:1a:2a:1a:fe:0c (try 1)
[ 4545.096930] wlan0: RX AssocResp from 00:1a:2a:1a:fe:0c (capab=0x431 status=0 aid=1)
[ 4545.096939] wlan0: associated
[ 4550.200338] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=17)
[ 4550.200388] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=3)
[ 4550.201765] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=3)
[ 4550.201887] wlan0: direct probe to AP 00:1a:2a:1a:fe:0c (try 1)
[ 4550.216873] wlan0: direct probe responded
[ 4550.216884] wlan0: authenticate with AP 00:1a:2a:1a:fe:0c (try 1)
[ 4550.236229] wlan0: authenticated
[ 4550.241409] wlan0: associate with AP 00:1a:2a:1a:fe:0c (try 1)
[ 4550.259146] wlan0: RX AssocResp from 00:1a:2a:1a:fe:0c (capab=0x431 status=0 aid=1)
[ 4550.259151] wlan0: associated
[ 4555.360113] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=17)
[ 4555.360183] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=3)
[ 4555.361653] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=3)
[ 4555.361866] wlan0: direct probe to AP 00:1a:2a:1a:fe:0c (try 1)
[ 4555.376961] wlan0: direct probe responded
[ 4555.376969] wlan0: authenticate with AP 00:1a:2a:1a:fe:0c (try 1)
[ 4555.396347] wlan0: authenticated
[ 4555.398140] wlan0: associate with AP 00:1a:2a:1a:fe:0c (try 1)
[ 4555.419279] wlan0: RX AssocResp from 00:1a:2a:1a:fe:0c (capab=0x431 status=0 aid=1)
[ 4555.419282] wlan0: associated
[ 4560.520087] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=17)
[ 4560.520148] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=3)
[ 4560.560727] wlan0: deauthenticating from 00:1a:2a:1a:fe:0c by local choice (reason=3)
[ 4560.560879] wlan0: direct probe to AP 00:1a:2a:1a:fe:0c (try 1)
[ 4560.572550] wlan0: direct probe responded
[ 4560.572553] wlan0: authenticate with AP 00:1a:2a:1a:fe:0c (try 1)
[ 4560.582378] wlan0: authenticated
[ 4560.582407...

[Benjamin Zeller (zeller-benjamin)]

I forgot to mention that the connection is dropping so fast, that i cannot even get a ip adress from DHCP.
Connection currently only works with WPA security.

[Benjamin Zeller (zeller-benjamin)]

installing backport modules did NOT help

[brott (gatorstudent20)]

This happens for me as well on 10.04 beta.

uname -a
Linux home 2.6.32-19-generic #28-Ubuntu SMP Thu Apr 1 10:39:41 UTC 2010 x86_64 GNU/Linux

02:00.0 Network controller: Intel Corporation WiFi Link 1000 Series
 Subsystem: Intel Corporation Device 1315
 Flags: bus master, fast devsel, latency 0, IRQ 32
 Memory at d8500000 (64-bit, non-prefetchable) [size=8K]
 Capabilities: <access denied>
 Kernel driver in use: iwlagn
 Kernel modules: iwlagn

Apr 6 05:03:15: [10804.881453] wlan0: deauthenticating from 94:0c:6d:a3:04:4c by local choice (reason=3)
Apr 6 05:03:15: [10808.075504] wlan0: deauthenticating from 94:0c:6d:a3:04:4c by local choice (reason=3)
Apr 6 05:03:15: [10808.113955] wlan0: direct probe to AP 94:0c:6d:a3:04:4c (try 1)
Apr 6 05:03:15: [10808.119020] wlan0: direct probe responded
Apr 6 05:03:15: [10808.119027] wlan0: authenticate with AP 94:0c:6d:a3:04:4c (try 1)
Apr 6 05:03:15: [10808.120810] wlan0: authenticated
Apr 6 05:03:15: [10808.120846] wlan0: associate with AP 94:0c:6d:a3:04:4c (try 1)
Apr 6 05:03:15: [10808.125650] wlan0: RX AssocResp from 94:0c:6d:a3:04:4c (capab=0x431 status=0 aid=1)
Apr 6 05:03:15: [10808.125656] wlan0: associated
Apr 6 05:03:20: [10813.572329] iwlagn 0000:02:00.0: iwl_tx_agg_start on ra = 94:0c:6d:a3:04:4c tid = 0
Apr 6 07:04:17: [18069.891503] wlan0: deauthenticating from 94:0c:6d:a3:04:4c by local choice (reason=3)
Apr 6 07:04:20: [18073.245994] wlan0: deauthenticating from 94:0c:6d:a3:04:4c by local choice (reason=3)
Apr 6 07:04:20: [18073.284365] wlan0: direct probe to AP 94:0c:6d:a3:04:4c (try 1)
Apr 6 07:04:20: [18073.289667] wlan0: direct probe responded
Apr 6 07:04:20: [18073.289675] wlan0: authenticate with AP 94:0c:6d:a3:04:4c (try 1)
Apr 6 07:04:20: [18073.292273] wlan0: authenticated
Apr 6 07:04:20: [18073.292309] wlan0: associate with AP 94:0c:6d:a3:04:4c (try 1)
Apr 6 07:04:20: [18073.296286] wlan0: RX AssocResp from 94:0c:6d:a3:04:4c (capab=0x431 status=0 aid=1)
Apr 6 07:04:20: [18073.296292] wlan0: associated
Apr 6 07:04:26: [18079.264965] iwlagn 0000:02:00.0: iwl_tx_agg_start on ra = 94:0c:6d:a3:04:4c tid = 0
Apr 6 09:05:24: [25336.891506] wlan0: deauthenticating from 94:0c:6d:a3:04:4c by local choice (reason=3)
Apr 6 09:05:27: [25340.167100] wlan0: deauthenticating from 94:0c:6d:a3:04:4c by local choice (reason=3)
Apr 6 09:05:27: [25340.205597] wlan0: direct probe to AP 94:0c:6d:a3:04:4c (try 1)
Apr 6 09:05:27: [25340.210652] wlan0: direct probe responded
Apr 6 09:05:27: [25340.210660] wlan0: authenticate with AP 94:0c:6d:a3:04:4c (try 1)
Apr 6 09:05:27: [25340.212411] wlan0: authenticated
Apr 6 09:05:27: [25340.212445] wlan0: associate with AP 94:0c:6d:a3:04:4c (try 1)
Apr 6 09:05:27: [25340.216437] wlan0: RX AssocResp from 94:0c:6d:a3:04:4c (capab=0x431 status=0 aid=1)
Apr 6 09:05:27: [25340.216443] wlan0: associated
Apr 6 09:05:33: [25345.964362] iwlagn 0000:02:00.0: iwl_tx_agg_start on ra = 94:0c:6d:a3:04:4c tid = 0
Apr 6 09:51:00: [28072.921485] wlan0: deauthenticating from 94:0c:6d:a3:04:4c by local choice (reason=3)
Apr 6 09:51:11: [28084.526146] Registered led device: iwl-phy0::radio
Apr 6 09:51:11: [28084.526181] Registered led device: iwl-ph...

[ftavares (fptavares)]

I also get the same behaviour in both 2.6.31-20 and 2.6.32-19 kernels.

On a laptop with 2.6.31-20:

[ 73.697011] wlan0: direct probe to AP 00:1f:9f:c8:a0:e3 (try 1)
[ 73.892121] wlan0: direct probe to AP 00:1f:9f:c8:a0:e3 (try 2)
[ 73.896839] wlan0: direct probe responded
[ 73.896854] wlan0: authenticate with AP 00:1f:9f:c8:a0:e3 (try 1)
[ 73.898832] wlan0: authenticated
[ 73.898905] wlan0: associate with AP 00:1f:9f:c8:a0:e3 (try 1)
[ 73.901988] wlan0: RX AssocResp from 00:1f:9f:c8:a0:e3 (capab=0x431 status=0 aid=1)
[ 73.902001] wlan0: associated
[ 83.917116] wlan0: deauthenticating from 00:1f:9f:c8:a0:e3 by local choice (reason=3)
[ 83.917269] wlan0: deauthenticating from 00:1f:9f:c8:a0:e3 by local choice (reason=3)
[ 84.118372] wlan0: deauthenticating from 00:1f:9f:c8:a0:e3 by local choice (reason=3)
[ 84.316952] wlan0: direct probe to AP 00:1f:9f:c8:a0:e3 (try 1)
[ 84.320994] wlan0: direct probe responded
[ 84.321029] wlan0: authenticate with AP 00:1f:9f:c8:a0:e3 (try 1)
[ 84.323019] wlan0: authenticated
[ 84.323087] wlan0: associate with AP 00:1f:9f:c8:a0:e3 (try 1)
[ 84.326075] wlan0: RX AssocResp from 00:1f:9f:c8:a0:e3 (capab=0x431 status=0 aid=1)
[ 84.326087] wlan0: associated
[ 94.337129] wlan0: deauthenticating from 00:1f:9f:c8:a0:e3 by local choice (reason=3)
[ 94.337332] wlan0: deauthenticating from 00:1f:9f:c8:a0:e3 by local choice (reason=3)
[ 94.542739] wlan0: deauthenticating from 00:1f:9f:c8:a0:e3 by local choice (reason=3)
[ 94.740991] wlan0: direct probe to AP 00:1f:9f:c8:a0:e3 (try 1)
[ 94.747058] wlan0: direct probe responded
[ 94.747069] wlan0: authenticate with AP 00:1f:9f:c8:a0:e3 (try 1)
[ 94.749555] wlan0: authenticated
[ 94.749626] wlan0: associate with AP 00:1f:9f:c8:a0:e3 (try 1)
[ 94.752787] wlan0: RX AssocResp from 00:1f:9f:c8:a0:e3 (capab=0x431 status=0 aid=1)
[ 94.752798] wlan0: associated
[ 104.764283] wlan0: deauthenticating from 00:1f:9f:c8:a0:e3 by local choice (reason=3) ...

[Brian Curtis (bcurtiswx)]

Sorry, i hit enter by accident when looking at teams (figuring out which to contact). Wireless fail at its best. Fixed

[Eric Swanson (eswanson)]

This issue is affecting me as well on 10.04 Beta, 2.6.32-21-generic x64. Any attempts to use other methods of connection (wicd, wpa_gui, etc) result in no connectivity at all. NM manages to connect intermittently but fails to remain connected.

Bug #425455 is probably similar, although not nearly as recent.

[Mike Rose (psu89)]

I also have this same issue on 10.04 beta, 2.6.32-21-generic. In fact, I have found wireless to be horrible in lucid. Not only does the connection drop and reconnect very frequently, sometimes it won't connect at all with dhcp. In that case, the essid gets mangled. I can get around that issue by manually assigning an address. I have never gotten wicd to connect at all, so am using network-manger. I hope this issues are resolved before the production release or there will be a lot of unhappy folks.

[Chris Bainbridge (chris-bainbridge)]

I just upgraded from karmic to lucid and wifi no longer works. It appears that wlan0 deauthenticates immediately after link becomes ready (reason=3)?, and after this DHCP times out.

Apr 27 21:34:15 yo kernel: [ 1355.137809] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 27 21:34:15 yo kernel: [ 1355.137845] wlan0: direct probe to AP 00:1d:68:0b:2c:d2 (try 1)
Apr 27 21:34:15 yo kernel: [ 1355.162313] wlan0: direct probe responded
Apr 27 21:34:15 yo kernel: [ 1355.162317] wlan0: authenticate with AP 00:1d:68:0b:2c:d2 (try 1)
Apr 27 21:34:15 yo kernel: [ 1355.164139] wlan0: authenticated
Apr 27 21:34:15 yo wpa_supplicant[906]: No network configuration found for the current AP
Apr 27 21:34:15 yo kernel: [ 1355.164161] wlan0: associate with AP 00:1d:68:0b:2c:d2 (try 1)
Apr 27 21:34:15 yo kernel: [ 1355.167221] wlan0: RX AssocResp from 00:1d:68:0b:2c:d2 (capab=0x411 status=0 aid=2)
Apr 27 21:34:15 yo kernel: [ 1355.167225] wlan0: associated
Apr 27 21:34:15 yo kernel: [ 1355.167977] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 27 21:34:15 yo kernel: [ 1355.168641] wlan0: deauthenticating from 00:1d:68:0b:2c:d2 by local choice (reason=3)
Apr 27 21:34:15 yo wpa_supplicant[906]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

[Chris Bainbridge (chris-bainbridge)]

I found the source of my problem: network-manager had been re-installed on upgrade (I had previously uninstalled it) and it is somehow preventing ifup from working. "apt-get remove network-manager" fixed the issue for me - ifup works.

[flyman (fleitman68)]

Same Problem with Intel Corporation PRO/Wireless 3945ABG. (I have no problems in Karmic)

"Ubuntu does not report that the connection has dropped. Instead, it re-associates in the background"

Ubuntu Lucid 10.04
2.6.32-21-generic
Network-Manager

test@lucid:~/Desktop$ lspci -nnvv

0c:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02)
 Subsystem: Intel Corporation Device [8086:1020]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 28
 Region 0: Memory at f9fff000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [c8] Power Management version 2
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
  Address: 00000000fee0300c Data: 41a9
 Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
   MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <64us
   ClockPM+ Suprise- LLActRep- BwNot-
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Advanced Error Reporting <?>
 Capabilities: [140] Device Serial Number 23-0c-81-ff-ff-bf-1c-00
 Kernel driver in use: iwl3945
 Kernel modules: iwl3945

test@lucid:~$ dmesg | grep iwl3945

[ 620.633131] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
[ 620.633137] iwl3945: Copyright(c) 2003-2009 Intel Corporation
[ 620.633245] iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 620.633266] iwl3945 0000:0c:00.0: setting latency timer to 64
[ 620.690117] iwl3945 0000:0c:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
[ 620.690122] iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
[ 620.690275] iwl3945 0000:0c:00.0: irq 28 for MSI/MSI-X
[ 620.702708] iwl3945 0000:0c:00.0: firmware: requesting iwlwifi-3945-2.ucode
[ 620.726686] iwl3945 0000:0c:00.0: loaded firmware version 15.32.2.9

test@lucid:~$ dmesg

[ 4887.102556] No probe response from AP 00:25:9c:41:67:1e after 500ms, disconnecting.
[ 4889.147057] wlan0: direct probe to AP 00:25:9c:41:67:1e (try 1)
[ 4889.149184] wlan0: direct probe responded
[ 4889.149192] wlan0: authenticate with AP 00:25:9c:41:67:1e (try 1)
[ 4889.151104] wlan0: authenticated
[ 4889.151240] wlan0: associate with AP 00:25:9c:41:67:1e (try 1)
[ 4889.154040] wlan0: RX AssocResp from 00:25:9c:41:67:1e (capab=0x431...

[Alejandro R. Mosteo (mosteo)]

I too got broken wireless upon upgrade to lucid. It was an USB dongle using driver rt73usb. Simptoms were the same deauthenticating barrage of messages, and mangled essid.

Following the clue of a previous reporter, I saw that I too had network-manager installed, albeit I use wicd. Killing the process (sudo service network-manager stop) didn't work. Uninstalling the package, however, did it even without rebooting.

[Tony Cox (tonycox01)]

The wireless on my Dell Latitude D630 broke on upgrade. My wireless now continuously cycles between connection/disconnection. It is useless. I can't believe an upgrade broke something so important.

[ 15.352804] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
[ 15.352808] iwl3945: Copyright(c) 2003-2009 Intel Corporation
[ 15.352919] iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 15.352934] iwl3945 0000:0c:00.0: setting latency timer to 64
[ 15.424670] iwl3945 0000:0c:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
[ 15.424673] iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG

dmesg reports a continuous log like this:

[ 82.423839] wlan0: associated
[ 123.237033] No probe response from AP 00:1e:2a:17:6d:50 after 500ms, disconnecting.
[ 126.080032] wlan0: direct probe to AP 00:1e:2a:17:6d:50 (try 1)
[ 126.281051] wlan0: direct probe to AP 00:1e:2a:17:6d:50 (try 2)
[ 126.480282] wlan0: direct probe to AP 00:1e:2a:17:6d:50 (try 3)
[ 126.680524] wlan0: direct probe to AP 00:1e:2a:17:6d:50 timed out
[ 137.036090] CE: hpet increasing min_delta_ns to 15000 nsec
[ 138.740934] wlan0: deauthenticating from 00:1e:2a:17:6d:50 by local choice (reason=3)
[ 138.742002] wlan0: direct probe to AP 00:0f:b5:56:90:02 (try 1)
[ 138.941065] wlan0: direct probe to AP 00:0f:b5:56:90:02 (try 2)
[ 139.140209] wlan0: direct probe to AP 00:0f:b5:56:90:02 (try 3)
[ 139.340144] wlan0: direct probe to AP 00:0f:b5:56:90:02 timed out
[ 146.437554] CE: hpet increasing min_delta_ns to 22500 nsec
[ 151.412680] wlan0: direct probe to AP 00:0f:b5:56:90:02 (try 1)
[ 151.612056] wlan0: direct probe to AP 00:0f:b5:56:90:02 (try 2)
[ 151.812258] wlan0: direct probe to AP 00:0f:b5:56:90:02 (try 3)
[ 152.012164] wlan0: direct probe to AP 00:0f:b5:56:90:02 timed out
[ 164.036568] wlan0: deauthenticating from 00:0f:b5:56:90:02 by local choice (reason=3)
[ 164.036756] wlan0: direct probe to AP 00:1e:2a:17:6d:50 (try 1)
[ 164.236160] wlan0: direct probe to AP 00:1e:2a:17:6d:50 (try 2)
[ 164.436298] wlan0: direct probe to AP 00:1e:2a:17:6d:50 (try 3)
[ 164.637519] wlan0: direct probe to AP 00:1e:2a:17:6d:50 timed out
[ 176.678040] wlan0: direct probe to AP 00:1e:2a:17:6d:50 (try 1)
[ 176.876179] wlan0: direct probe to AP 00:1e:2a:17:6d:50 (try 2)
[ 177.076076] wlan0: direct probe to AP 00:1e:2a:17:6d:50 (try 3)
[ 177.276160] wlan0: direct probe to AP 00:1e:2a:17:6d:50 timed out
[ 189.357005] wlan0: deauthenticating from 00:1e:2a:17:6d:50 by local choice (reason=3)
[ 189.357540] wlan0: direct probe to AP 00:0f:b5:56:90:02 (try 1)
[ 189.556084] wlan0: direct probe to AP 00:0f:b5:56:90:02 (try 2)
[ 189.756182] wlan0: direct probe to AP 00:0f:b5:56:90:02 (try 3)
[ 189.956163] wlan0: direct probe to AP 00:0f:b5:56:90:02 timed out

Not sure how to fix this - above did not fix my connection.

[Sebastian Geiger (lanoxx)]

[40374.113488] wlan0: direct probe responded
[40374.113495] wlan0: authenticate with AP 00:11:88:28:5e:ea (try 1)
[40374.114644] wlan0: authenticated
[40374.114690] wlan0: associate with AP 00:11:88:28:5e:ea (try 1)
[40374.118254] wlan0: RX AssocResp from 00:11:88:28:5e:ea (capab=0x11 status=0 aid=1)
[40374.118261] wlan0: associated
[40374.138517] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[40384.122611] wlan0: deauthenticating from 00:11:88:28:5e:ea by local choice (reason=3)
[40384.136814] wlan0: deauthenticating from 00:11:88:28:5e:ea by local choice (reason=3)
[40384.143364] wlan0: direct probe to AP 00:11:88:28:5e:e2 (try 1)
[40384.146195] wlan0: direct probe responded
[40384.146204] wlan0: authenticate with AP 00:11:88:28:5e:e2 (try 1)
[40384.148526] wlan0: authenticated
[40384.202992] wlan0: associate with AP 00:11:88:28:5e:e2 (try 1)
[40384.209155] wlan0: RX AssocResp from 00:11:88:28:5e:e2 (capab=0x411 status=0 aid=12)
[40384.209165] wlan0: associated
[40399.512687] wlan0: deauthenticating from 00:11:88:28:5e:e2 by local choice (reason=3)

I am experienceing this bug, its very annoying, here is the output of dmesg directly after I have lost connection, when it happends i am unable to reauthenticate until i either supend or toggle the killswitch once. Depending on my position this occures between every 20secs and a few minutes. Its only happens on a WPA2 Enterprise network.

[sillyxone (sillyxone)]

Confirm. Dell D630, Intel 4965AG. Everything was fine on Hardy until I installed Lucid. Don't have problem with unsecured or WPA1-Personal, only have problem with WPA2-Enterprise (PEAP, MSCHAP). I couldn't tell when it get disconnected, but I can use the Internet for about 30 seconds, then it takes about 15 seconds to connect to the servers again, but in the whole time there is no sign that the connection dropped (IP address stays the same the whole time). Same result for both NetworkManager and wicd.

I think this is a problem of iwlagn. I disabled iwlagn (blacklist it from modprobe), installed ndiswrapper and use a Windows XP driver, and it works fine (except ntos-wq keeps crunching CPU).

I'm currently on 2.6.32-22-generic.

[Stardom (seth-tewebs)]

Same problem here. Except for me if i go from hibernate it does this, but when i finally get internet connection it'll only disconnect once in a while. But getting it to connect in the first place is a pain, full of random button clicking (network disable/enable) and hope.

[sillyxone (sillyxone)]

Right after I commented above, I started Googling in a different direction and found this bug report in Red Hat (see comment #10):
https://bugzilla.redhat.com/show_bug.cgi?id=503983

Basically they said that the N-mode that was causing connection drops, so I added this line to /etc/modprobe.d/options.conf, and it works great then.
options iwlagn 11n_disable=1 11n_disable50=1

I've tested several times with that line enabled and disabled, with reboots in between, and confirm that it does fix the problem (I can reproduce the problem again any time by disabling that line). The network connections without that fix was reported as jumping between 0 and 130 Mb/s, whereas with that line enabled, the connection speed goes between 48-54 Mb/s.

I've only tested during the last hour with WPA2-Enterprise. If I won't report further then it works with my WPA1-personal network too.

[Thomas (t-hartwig)]

sillyxone wrote:
> Basically they said that the N-mode that was causing connection drops,
> so I added this line to /etc/modprobe.d/options.conf, and it works great then.
> options iwlagn 11n_disable=1 11n_disable50=1

 I can not confirm this is fixing it for me. I still have the problem when reloading the module with these options.

[Mike Rose (psu89)]

After a couple other folks said they had luck by getting rid of network-manager, I figured I'd give wicd another shot. I removed network manager, rebooted, manually configured a wired network, then installed wicd. I've been going on a few days now with no disconnects, so perhaps something is amiss with network-manager.

That being said, wicd doesn't seem to work 100% either in that it never shows me other wireless networks. When I first installed wicd, it showed me a list of wireless networks and I picked mine and put in my WPA passphrase. After rebooting, wicd kept prompting me for my password. I got around that by adding "exec wicd" to /etc/init/networking.conf. Wicd always connects to my network on reboot without issue, but if I try to scan for other networks, it says none are found. As long as it connects to my network, I'm okay, but it's still not right.

As a side note, as root if I do an iwlist scan, I get an error message about resource temporarily unavailable. If I do an iwlist scan as a non-root user, it returns my network, but no others.

At least I have a usable wireless connection now. I may go back now and try to build an old otusdriver, as the ar9170usb driver still doesn't support n speeds.

[JamesH (jnahughes)]

Me too I am afraid. Using Lucid, with a BlueNext BN-WD54g USB adapter (lsusb gives ...Ralink Technology, Corp. RT2501USB Wireless Adapter) . Used to work fine on all previous version (from about 6.x).

Behaviour is most odd. Just spent an hour trying to get it to work - different USB ports etc, redoing connection settings, rebooting router, different but same model adapter. Then plugged in a 3COM adapter to same port which started working straight away. Just for fun, I then plugged in the bluenext device as well - and it started working, and continued to work after the 3COM was removed. I then unplugged it, then plugged in to a different port and it kept working, so plugging in the 3COM seems to have kicked the system in to working! Like I said - odd!

Last chunk of dmsg..

[ 974.710436] rt73usb 3-5:1.0: firmware: requesting rt73.bin
[ 975.524474] ADDRCONF(NETDEV_UP): wlan2: link is not ready
[ 984.808547] wlan2: direct probe to AP 00:14:7c:b7:2e:00 (try 1)
[ 984.808619] wlan2: deauthenticating from 00:14:7c:b7:2e:00 by local choice (reason=3)
[ 984.808690] wlan2: direct probe to AP 00:14:7c:b7:2e:00 (try 1)
[ 984.810521] wlan2: direct probe responded
[ 984.810531] wlan2: authenticate with AP 00:14:7c:b7:2e:00 (try 1)
[ 984.815524] wlan2: authenticated
[ 984.815565] wlan2: associate with AP 00:14:7c:b7:2e:00 (try 1)
[ 984.818522] wlan2: RX AssocResp from 00:14:7c:b7:2e:00 (capab=0x431 status=0 aid=3)
[ 984.818530] wlan2: associated
[ 984.962032] ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[ 995.428041] wlan2: no IPv6 routers present
[ 1005.536078] No probe response from AP 00:14:7c:b7:2e:00 after 500ms, disconnecting.
[ 1099.084968] wlan2: direct probe to AP 00:14:7c:b7:2e:00 (try 1)
[ 1099.086989] wlan2: direct probe responded
[ 1099.086999] wlan2: authenticate with AP 00:14:7c:b7:2e:00 (try 1)
[ 1099.089984] wlan2: authenticated
[ 1099.090036] wlan2: associate with AP 00:14:7c:b7:2e:00 (try 1)
[ 1099.288079] wlan2: associate with AP 00:14:7c:b7:2e:00 (try 2)
[ 1099.488060] wlan2: associate with AP 00:14:7c:b7:2e:00 (try 3)
[ 1099.688083] wlan2: association with AP 00:14:7c:b7:2e:00 timed out
[ 1111.192101] wlan2: direct probe to AP 00:14:7c:b7:2e:00 (try 1)
[ 1111.194107] wlan2: direct probe responded
[ 1111.194117] wlan2: authenticate with AP 00:14:7c:b7:2e:00 (try 1)
[ 1111.196238] wlan2: authenticated
[ 1111.196280] wlan2: associate with AP 00:14:7c:b7:2e:00 (try 1)
[ 1111.199102] wlan2: RX AssocResp from 00:14:7c:b7:2e:00 (capab=0x431 status=0 aid=1)
[ 1111.199110] wlan2: associated
[ 1121.560081] wlan2: deauthenticating from 00:14:7c:b7:2e:00 by local choice (reason=3)
[ 1121.872543] wlan2: deauthenticating from 00:14:7c:b7:2e:00 by local choice (reason=3)
[ 1122.367385] wlan2: direct probe to AP 00:14:7c:b7:2e:00 (try 1)
[ 1122.396395] wlan2: direct probe responded
[ 1122.396406] wlan2: authenticate with AP 00:14:7c:b7:2e:00 (try 1)
[ 1122.596080] wlan2: authenticate with AP 00:14:7c:b7:2e:00 (try 2)
[ 1122.623348] wlan2: authenticated
[ 1122.623391] wlan2: associate with AP 00:14:7c:b7:2e:00 (try 1)
[ 1122.820069] wlan2: associate with AP 00:14:7c:b7:2e:00 (try 2)
[ 1123.020081] wlan2: associate with AP 00:14:7c:...

[Phil Ayres (ayres-phil)]

Me too with a workaround (yes, I'm very happy!):

I'm on Lucid with with kernel 2.6.32-22-generic, running an Intel 5100 wifi card and iwlagn driver. I was getting the two minute 'no probe response' error like the bug creator (see my syslog below). I fixed it on my machine by disabling IPV6 in the kernel at boot time by adding

ipv6.disable=1

to my kernel boot line in grub, then doing a

sudo update-grub

My wifi has sped up incredibly (speedtest.net showed almost double what I was getting previously) and the annoying disassociation has stopped (now I can use Skype without 4 seconds of dropped packets and silence every 2 minutes).

No guarantees, and obviously if you depend on ipv6 you're kinda stuck, but maybe it will help somebody track down the issue.

Jun 1 09:38:17 consected-sv1-001 avahi-daemon[940]: last message repeated 2 times
Jun 1 09:38:17 consected-sv1-001 kernel: [328719.776028] No probe response from AP 00:14:6c:1b:93:2e after 500ms, disconnecting.
Jun 1 09:38:17 consected-sv1-001 wpa_supplicant[1123]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jun 1 09:38:17 consected-sv1-001 NetworkManager: <info> (wlan0): supplicant connection state: completed -> disconnected
Jun 1 09:38:17 consected-sv1-001 NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Jun 1 09:38:20 consected-sv1-001 wpa_supplicant[1123]: WPS-AP-AVAILABLE
Jun 1 09:38:20 consected-sv1-001 wpa_supplicant[1123]: Trying to associate with 00:14:6c:1b:93:2e (SSID='homeoffice2a' freq=2462 MHz)
Jun 1 09:38:20 consected-sv1-001 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Jun 1 09:38:20 consected-sv1-001 kernel: [328723.134249] wlan0: direct probe to AP 00:14:6c:1b:93:2e (try 1)
Jun 1 09:38:20 consected-sv1-001 kernel: [328723.136719] wlan0: direct probe responded
Jun 1 09:38:20 consected-sv1-001 kernel: [328723.136730] wlan0: authenticate with AP 00:14:6c:1b:93:2e (try 1)
Jun 1 09:38:20 consected-sv1-001 kernel: [328723.138572] wlan0: authenticated
Jun 1 09:38:20 consected-sv1-001 kernel: [328723.138633] wlan0: associate with AP 00:14:6c:1b:93:2e (try 1)
Jun 1 09:38:20 consected-sv1-001 wpa_supplicant[1123]: Associated with 00:14:6c:1b:93:2e
Jun 1 09:38:20 consected-sv1-001 kernel: [328723.141006] wlan0: RX AssocResp from 00:14:6c:1b:93:2e (capab=0x411 status=0 aid=1)
Jun 1 09:38:20 consected-sv1-001 kernel: [328723.141017] wlan0: associated
Jun 1 09:38:20 consected-sv1-001 NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated
Jun 1 09:38:20 consected-sv1-001 NetworkManager: <info> (wlan0): supplicant connection state: associated -> 4-way handshake
Jun 1 09:38:20 consected-sv1-001 NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake
Jun 1 09:38:20 consected-sv1-001 wpa_supplicant[1123]: WPA: Key negotiation completed with 00:14:6c:1b:93:2e [PTK=TKIP GTK=TKIP]
Jun 1 09:38:20 consected-sv1-001 wpa_supplicant[1123]: CTRL-EVENT-CONNECTED - Connection to 00:14:6c:1b:93:2e completed (reauth) [id=0 id_str=]
Jun 1 09:38:20 consected-sv1-001 NetworkManager: <info> (wlan0): supplicant c...

[Phil Ayres (ayres-phil)]

Oh, just to finish my though, I'm on

WPA2 personal, with a NetGear router running at 11 / 54 Mbs (b or g). Network Manager seems fine. I never had any problems in the past with the wired LAN, and the Intel 5100 card is brand new, albeit offering a pretty puny signal strength compared to the netbook I have across the desk from it.

[matt.wartell (matt-wartell+lp)]

Confirming Phil Ayers workaround of disabling ipv6 apparently stopping the deauthentication and all its consequences.

$ uname -a
Linux flatguy.local 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=5ba98674-c456-438f-bb1c-b1d97f4e2415 ro ipv6.disable=1

System: Sony Vaio PCG-R505DL (with 1988.60 BogoMIPS of Power!!!)
Adapter: Belkin F5D8011v2000 via PCMCIA running rt2500-pci driver (Lucid default) with WPA-PSK2 and no NetworkManager

Prior to adding the workaround, the system was up but with no user activity for 3.9 hours in which syslog recorded 108 deauthentication events with a MTBF of 131 seconds. This was typical behavior over the last month whether associated with a D-Link DI-524 or Belkin F5D8231-4 v2 WAP (yes, I switched WAP/Routers trying to fix this). The affected machine quite literally had no other change except for the addition to /etc/default/grub, update-grub and reboot.

Since applying Mr. Ayers ipv6.disable=1 workaround, the wlan0 connection has remained associated with the WAP since boot, 1.5 hours ago, while beating upon it nearly continuously with netperf to a wired sink at a rate of 15Mbps.

Thanks, Phil!

[matt.wartell (matt-wartell+lp)]

Alas, I spoke too soon, but did get good data out of it.

For my report above (#26 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/548992/comments/26) I had done the grub modification, reboot and testing remotely from a machine other than the troubled "flatguy". I was ssh'ed into flatguy in multiple sessions, running netperf and such, but the laptop itself was physically untouched. Since reboot, the console was running gdm waiting for a login.

After posting, I logged in on flatguy's console and logged six WiFi deauthentications in 17 minutes. However, this information does place the triggering event firmly in some user-space application.

Now I can stop groveling through the kernel WiFi stack and hunt through the Kubuntu XFCE start-up processes for the trigger. Sigh.

[JamesH (jnahughes)]

Further to my comment above, this is the content from end of /var/log/daemon.log. It appears to be timing out on a DHCP request. Since my AP hasn't changed in years, it must be a change at the Ubuntu end that has produced this issue. Since the last update, my workaround no longer works around, so am a bit stuck. I tried the disabling IPV6 on the command line but this hasn't helped.

Jun 15 20:33:27 james-desktop NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit
Jun 15 20:33:27 james-desktop dhclient: Listening on LPF/wlan0/00:21:27:c1:33:19
Jun 15 20:33:27 james-desktop dhclient: Sending on LPF/wlan0/00:21:27:c1:33:19
Jun 15 20:33:27 james-desktop dhclient: Sending on Socket/fallback
Jun 15 20:33:31 james-desktop dhclient: DHCPREQUEST of 192.168.1.3 on wlan0 to 255.255.255.255 port 67
Jun 15 20:33:53 james-desktop dhclient: last message repeated 2 times
Jun 15 20:33:53 james-desktop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jun 15 20:33:58 james-desktop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 15 20:34:05 james-desktop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Jun 15 20:34:13 james-desktop NetworkManager: <info> (wlan0): DHCP transaction took too long, stopping it.
Jun 15 20:34:13 james-desktop NetworkManager: <info> (wlan0): canceled DHCP transaction, dhcp client pid 2175
Jun 15 20:34:13 james-desktop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) scheduled...
Jun 15 20:34:13 james-desktop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) started...
Jun 15 20:34:13 james-desktop NetworkManager: <info> (wlan0): device state change: 7 -> 9 (reason 5)
Jun 15 20:34:13 james-desktop NetworkManager: <info> Activation (wlan0) failed for access point (JamesOne)
Jun 15 20:34:13 james-desktop NetworkManager: <info> Marking connection 'JamesOne' invalid.
Jun 15 20:34:13 james-desktop NetworkManager: <info> Activation (wlan0) failed.
Jun 15 20:34:13 james-desktop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) complete.
Jun 15 20:34:13 james-desktop NetworkManager: <info> (wlan0): device state change: 9 -> 3 (reason 0)
Jun 15 20:34:13 james-desktop NetworkManager: <info> (wlan0): deactivating device (reason: 0).
Jun 15 20:34:13 james-desktop wpa_supplicant[1125]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

[Alvin Larson (alvinlarson)]

Hello,

Apparently this old bug still exists. I recently installed Debian (5.0.4) Lenny on my AMD 64 bit computer. The kernel is 2.6.26-2-AMD6. I am having a lot of trouble with the wireless network going down and sometimes the applications start up very slowly and are unresponsive. I removed network-manager, as suggested on another post. This greatly improved performance but the problem hasn't gone away. I discovered that I could make the network go down by trying to install Amarok with the Synaptic Package Manager. The following is dmesg showing (1) the situation while in a normal run mode, (2) the line produced when the network went down during the Synaptic session and then (3) what it looks
like after recovery by ifdown and ifup.

INITIAL END OF DMESG FILE:

[ 4027.427162] wlan0: Initial auth_alg=0
[ 4027.427172] wlan0: authenticate with AP 00:0c:41:fc:ed:a0
[ 4027.427162] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4027.428801] wlan0: RX authentication from 00:0c:41:fc:ed:a0 (alg=0 transaction=2 status=0)
[ 4027.428805] wlan0: authenticated
[ 4027.428808] wlan0: associate with AP 00:0c:41:fc:ed:a0
[ 4027.430783] wlan0: RX AssocResp from 00:0c:41:fc:ed:a0 (capab=0x401 status=0 aid=2)
[ 4027.430788] wlan0: associated
[ 4027.430803] wlan0: switched to short barker preamble (BSSID=00:0c:41:fc:ed:a0)
[ 4027.431386] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 4038.301775] wlan0: no IPv6 routers present

THIS IS WHERE I WAS TRYING TO INSTALL AMAROK WITH SYNAPTIC PACKAGE MANAGER. THE WIRELESS NETWORK DIED RIGHT HERE. FOLLOWING IS DMESG
AFTER THAT.

[ 7597.650723] wlan0: No ProbeResp from current AP 00:0c:41:fc:ed:a0 - assume out of range

THE FOLLOWING IS AFTER I RESTART WIRELESS WITH "ifdown wlan0" an "ifup wlan0".

FOLLOWING IS DMESG AFTER WIRELESS COMES BACK TO LIFE HERE.

[ 7863.634497] wlan0: Initial auth_alg=0
[ 7863.634506] wlan0: authenticate with AP 00:0c:41:fc:ed:a0
[ 7863.634497] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 7863.636536] wlan0: RX authentication from 00:0c:41:fc:ed:a0 (alg=0 transaction=2 status=0)
[ 7863.636540] wlan0: authenticated
[ 7863.636544] wlan0: associate with AP 00:0c:41:fc:ed:a0
[ 7863.638743] wlan0: RX AssocResp from 00:0c:41:fc:ed:a0 (capab=0x401 status=0 aid=2)
[ 7863.638748] wlan0: associated
[ 7863.638761] wlan0: switched to short barker preamble (BSSID=00:0c:41:fc:ed:a0)
[ 7863.639306] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 7873.792488] wlan0: no IPv6 routers present

I do hope this bug can be fixed. It makes Debian very difficult to use.

Al

[JamesH (jnahughes)]

Further investigation after my post here #28.

I am pretty sure this is a DHCP issue. If I am using DHCP, then I get the failures. If I define a static IP address, then things 'appear' to work OK. Still looking in to it, but certainly changing to static IP, the wireless link starts and stays up - on DHCP the link wouldn't even start up.

As said before, this adapter has worked fine on earlier version prior to Lynx.

[JamesH (jnahughes)]

Just to confirm my previous post - moving to a static IP address has resolved all the problems I am seeing. Machine has connected and stayed up for 24hrs. Performance appears to be similar to conditions prior to the failure occurring (ie Lynx upgrade).

[Dirk Eddelbuettel (edd)]

Quick confirmation of post #13 -- I was seeing the infamous 'deauthenticating from .... by local choice' and running 'apt-get remove network-manager' fixed it. FWIW this was on my IBM/Lenovo X60 running Debian testing; the netbook running Kubuntu 10.4 is just fine. So a thanks! and tip of the hat to Chris Bainbridge for the hint!

[quixote (commer-greenglim)]

I seem to have this problem too on a Thinkpad X201s running 64-bit Lucid with all the updates, except that I'm currently using the 2.6.32.22 kernel. Wireless is dropped at some point, from hours to minutes, especially after coming out of suspend. Sometimes the connection is recovered once or twice, but usually it stays dropped until a reboot.

Just a side note for anyone who may not know exactly how to add the ipv6 line: open /etc/default/grub as sudo (eg sudo nano /etc/grub/default), and alter this line:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"

[quixote (commer-greenglim)]

I should add, the connection is dropped just the same under 2.6.32.23 kernel.

[quixote (commer-greenglim)]

Well, turning off ipv.6 at bootup hasn't worked for me. I tend to lose wireless after coming out of suspend, and that hasn't changed. What has helped is manually reassociating the Access Point, sometimes repeatedly. E.g. using the command: sudo iwconfig wlan0 ap 00:80:4D:99:D7:10 (Substitute your own wlan# and ap, which you can see by running iwconfig by itself.)

[pidgas (pidgas)]

I most certainly had/have this problem. Drove me crazy enough to perform a fresh install of Ubuntu Lucid 10.04 retaining only home directories. Was able to reconnect my way through to a fully updated installation with all the most recent updates/kernel (Linux 2.6.32-21-generic kernel) and no added packages. I continued to experience the problem (deauthenticating by local choice reason=3 followed by numerous reconnections and disconnections). I disabled ipv6 as described in this thread and rebooted - error persisted. I attempted to disable power management on my card, but my card does not support that setting. I installed wicd and removed network-manager and network-manager-gnome. I then rebooted. Wireless network now seems solid and I'm seeing none of the previous drops. Speed is fast and consistent - even with long periods between use (at least long enough that I would see the problem previously).

[T61P (jennifertebbutt)]

Running on Thinkpad T61p, kernel 2.6.32-24-generic (64bit) Network Manager seems to be bugged dropping speed to zero over Wifi (Intel 4965 AGN); Connection taking time to connect and then slowing to nothing despite previously working perfectly (but seeming to get worse on last 2 kernel updates) and appears to possibly effecting 3g (sierra wireless) (but may be vodaphone slowing connection (connection is not dropped but slowed progressively). Works fine on same machine with Karmic install (earlier Kernel).

Reboot solves the problem but only temporarily. Fixed dns IP improves the situation, but still rate drops to nothing. Disable IPv6 did not solve the problem (though seems to have speeded up connection times temporarily - but not as much as fixed DNS IP (cannot change manual instead of DHCP but I suspect this may help)

Dmesg
 wlan0: deauthenticating from 00:05:25:10:9d:56 by local choice (reason=3)
[ 29.993271] wlan0: direct probe to AP 00:05:25:10:9d:56 (try 1)
[ 30.190076] wlan0: direct probe to AP 00:05:25:10:9d:56 (try 2)
[ 30.390054] wlan0: direct probe to AP 00:05:25:10:9d:56 (try 3)
[ 30.590048] wlan0: direct probe to AP 00:05:25:10:9d:56 timed out
[ 49.407260] wlan0: direct probe to AP 00:05:25:10:9d:56 (try 1)
[ 49.410129] wlan0: direct probe responded
[ 49.410132] wlan0: authenticate with AP 00:05:25:10:9d:56 (try 1)
[ 49.411983] wlan0: authenticated
[ 49.411995] wlan0: associate with AP 00:05:25:10:9d:56 (try 1)
[ 49.414722] wlan0: RX AssocResp from 00:05:25:10:9d:56 (capab=0x411 status=0 aid=1)
[ 49.414724] wlan0: associated
[ 49.433332] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 53.022955] wlan0: deauthenticated from 00:05:25:10:9d:56 (Reason: 6)
[ 53.209457] wlan0: direct probe to AP 00:05:25:10:9d:56 (try 1)
[ 53.211857] wlan0: direct probe responded
[ 53.211859] wlan0: authenticate with AP 00:05:25:10:9d:56 (try 1)
[ 53.216615] wlan0: authenticated
[ 53.216640] wlan0: associate with AP 00:05:25:10:9d:56 (try 1)
[ 53.219224] wlan0: RX AssocResp from 00:05:25:10:9d:56 (capab=0x411 status=0 aid=1)
[ 53.219227] wlan0: associated
[ 65.030561] wlan0: deauthenticated from 00:05:25:10:9d:56 (Reason: 6)
[ 67.425221] wlan0: direct probe to AP 00:05:25:10:9d:56 (try 1)
[ 67.427605] wlan0: direct probe responded
[ 67.427608] wlan0: authenticate with AP 00:05:25:10:9d:56 (try 1)
[ 67.429485] wlan0: authenticated
[ 67.429501] wlan0: associate with AP 00:05:25:10:9d:56 (try 1)
[ 67.432394] wlan0: RX AssocResp from 00:05:25:10:9d:56 (capab=0x411 status=0 aid=1)
[ 67.432396] wlan0: associated
[ 73.026477] wlan0: deauthenticated from 00:05:25:10:9d:56 (Reason: 6)
[ 73.219549] wlan0: direct probe to AP 00:05:25:10:9d:56 (try 1)
[ 73.410082] wlan0: direct probe to AP 00:05:25:10:9d:56 (try 2)
[ 73.412661] wlan0: direct probe responded
[ 73.412663] wlan0: authenticate with AP 00:05:25:10:9d:56 (try 1)
[ 73.414485] wlan0: authenticated
[ 73.414495] wlan0: associate with AP 00:05:25:10:9d:56 (try 1)
[ 73.416965] wlan0: RX AssocResp from 00:05:25:10:9d:56 (capab=0x411 status=0 aid=1)
[ 73.416966] wlan0: associated
[ 78.024396] wlan0: deauthenticated from 00:05:25...

[RDD (rdd37misc)]

I just wanted to "second" that Chris Bainbridge's solution fixed the issue for me, as well:
'apt-get remove network-manager'

network-manager was apparently re-installed during a recent update; I had removed it previously.

This is on an IBM Thinkpad T30 with external (3rd party) USB wireless card; Ubuntu 10.04, 2.6.32-24-generic kernel.

Thanks for the information here.

[[e-mail] (gadbermd)]

This is also happening on my laptop after an upgrade from Karmic to Lucid. Symptoms are the exact same as reported by original poster. Laptop is a Dell Latitude D630 with Intel wireless running kernel 2.6.32-24-generic. Output from lspci:

0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
 Subsystem: Intel Corporation Device 1020
 Flags: bus master, fast devsel, latency 0, IRQ 28
 Memory at fe8ff000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [c8] Power Management version 2
 Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
 Capabilities: [e0] Express Legacy Endpoint, MSI 00
 Capabilities: [100] Advanced Error Reporting <?>
 Capabilities: [140] Device Serial Number ea-13-a2-ff-ff-3c-1f-00
 Kernel driver in use: iwl3945
 Kernel modules: iwl3945

I can confirm that the fix for me was also to remove network-manager and then install wicd in it's place. My wireless connections seem to be working now. I have to believe this bug is affecting a very large number of users.

[Novastorm (novastorm87)]

I'm getting the same issue as everyone else. However it seems that different access points at my university aren't affected. If i'm in the library I get this issue, see logs below, however when in another building, using the same wireless network, same authentication (WPA with TTLS/PAP) etc, I don't have any problems, good speed, good connection strength etc.

All AP's are Cisco branded, not sure what model (may be different in different buildings), all 802.11G, no 802.11N to my knowledge.

I don't have this problem when booted into Windows 7 (which is rare, lucid is fantastic).

Also worth noting, I've found that when the wireless drops, DNS appears to be the first thing to die. For example if I notice the wireless has died (when using Chromium say), then I open a terminal and try to ping a hostname, I get DNS resolution failures, but if I ping an IP address it works OK for another say 15 - 30 seconds.

LSPCI:
0c:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection
 Subsystem: Intel Corporation Device 1121
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 31
 Region 0: Memory at f1ffe000 (64-bit, non-prefetchable) [size=8K]
 Capabilities: [c8] Power Management version 3
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
  Address: 00000000fee0100c Data: 41c9
 Capabilities: [e0] Express (v1) Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
   MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <32us
   ClockPM+ Suprise- LLActRep- BwNot-
  LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Advanced Error Reporting <?>
 Capabilities: [140] Device Serial Number 3e-3a-xx-xx-xx-xx-xx-xx
 Kernel driver in use: iwlagn
 Kernel modules: iwlagn

DMESG:
[ 91.796964] wlan0: direct probe to AP c4:7d:4f:4b:2f:bb (try 1)
[ 91.990304] wlan0: direct probe to AP c4:7d:4f:4b:2f:bb (try 2)
[ 91.991347] wlan0: direct probe responded
[ 91.991358] wlan0: authenticate with AP c4:7d:4f:4b:2f:bb (try 1)
[ 91.992161] wlan0: authenticated
[ 91.992210] wlan0: associate with AP c4:7d:4f:4b:2f:bb (try 1)
[ 91.994246] wlan0: RX AssocResp from c4:7d:4f:4b:2f:bb (capab=0x11 status=0 aid=1)
[ 91.994252] wlan0: associated
[ 102.040150] wlan0: deauthenticating from c4:7d:4f:4b:2f:bb by local choice (reason=3)
[ 102.087425...

[Seth Forshee (sforshee)]

@thijz: What your logs seem to show is a couple of instances of jumping between two APs on the same network. That's the only cause I see of disconnecting from a BSSID. I'm not familiar enough with wpa_supplicant to know what criteria it uses for switching, presumably something to do with signal strength, but the logs aren't really showing any data about the scan results to let us compare between the APs.

[L. Ross Raszewski (rraszews)]

Just discovered something. Since my issue returned after an absence during a power hit, I wondered if it could be a bug in how power-saving features affect the wireless device. After running "iwconfig wlan0 power off", I have not had any more disconnections. I'm wondering if the power management features are causing the wireless device to reduce the transmitter power or be more aggressive in looking to see if a better access point is available.

[thijs van severen (thijsvanseveren)]

some more info :
- i am experiencing these reconnects when i am sitting at my desk, so i'm not moving (and neither are the AP's i think ;-)
- i have seen this happen while i'm working on my laptop, so my laptop is not going to sleep/standby/powersave at that moment

is there a possibility to see the powersave mode (a log?) together with the logging we already have ?

[thijs van severen (thijsvanseveren)]

just tested the following to make sure that there is no power save kicking in
- i started a simple 1-sec interval ping from my wlan adapter to google (ping -I wlan0 www.google.com -i 1)
- since my wlan connection is active BUT my laptop is also connected to our network via a wired connection (via the dock) i got no response to the ping (the wired connection has priority over the wlan i guess)
- i disconnected the wired connection
- after a minute or so i saw the first 'reason=3' disconnect
- the ping shows a longer response time at the time of disconnect, and only sometimes a 'destination host unreachable'

so since there is constant activity on my wlan interface and i still get the disconnects, i think this issue is not related to powersave

anything else i can try ?

[Seth Forshee (sforshee)]

thijz: If you want to test disabling powersave, you should run 'iwconfig <interface> power off'. I don't know that simply trying to keep the network busy is enough to conclude that your issues aren't related to powersave.

[thijs van severen (thijsvanseveren)]

i can also confirm that the disconnects stop when you issue the 'iwconfig wlan0 power off' command

[mehturt (mehturt)]

power off seems to fix lots of wireless issues..
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/201306

[thijs van severen (thijsvanseveren)]

what are the default iwconfig power settings ?
how does switching power off affect the battery life ?

[Mathieu Trudel-Lapierre (cyphermox)]

Well, if the driver's power management causes issues with disconnection, then I think we've established this isn't an issue with wpasupplicant; so marking this Invalid.

Were these issues on battery or with power connected? pm-utils may be causing issues by turning on power management when a laptop drops from main to battery power.

[Seth Forshee (sforshee)]

thijz: We have powersave enabled in the kernel by default. I don't know what kind of difference in battery life you'll see by disabling it, you'll just have to try it and see I guess.

Wireless powersave is a cooperative arrangement between the card and the AP, and it's known that some APs have problems with powersave mode that lead to dropped connections. If you only see this issue on one or a limited number of networks, it may be an AP problem, in which case it may be worth investigating whether a firmware update is available or if you can disable support in the AP. Otherwise I think that you can disable powersave permanently by adding a script to execute the iwconfig command in /etc/network/if-up.d (I haven't tested this myself though).

[Seth Forshee (sforshee)]

I just noticed that the original reporter of this bug indicated that his problems were fixed over a year ago. Therefore I'm marking this bug fixed. Those of you still experiencing connection drops should open new bugs, probably based on the model of your wireless adapter. I.e., if you can't find a bug with the same symptoms and wireless adapter model that you have, please open a new bug. If we later find the problem really is the same as another bug we can always mark it as a duplicate.

[Yves Dorfsman (dorfsmay)]

Same here, "iwconfig wlan0 power off" solved the issue with the problematic APs.

L. Ross Raszewski :

I had created a bug report with Intel:

http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2305

Do you want to update it with your findings, or do you want me to do it?

[thijs van severen (thijsvanseveren)]

@Mathieu : i have the disconnects both running on AC and on battery power
@Seth : fyi i'm using a thinkpad (W510, core i7) and all the AP's are cisco

do i understand correctly that i should open a ticket for the specific combination of my type of wlan adapter and the the type of AP in my company ??? is this for real ??
this means that there must (or should) exist a ton of tickets out there ...

i'll check what type of wlan adapter i have (currently working on another pc so cant check right now) and see if i can find a ticket for it. is there a way to determine the type of AP used without asking IT ? (i can already see the look on their faces when i tell them why i need to know this ... i'll probably get nothing more that a 'huh ?' ;-)

[Seth Forshee (sforshee)]

thijz: Not one ticket per wlan adapter/AP combo, just one ticket per wlan adapter. Otherwise we end up with bugs that represent a multitude of different problems with similar symptoms. That's what has happened with this one.

If the problem is specific to an AP then the problem may be with the AP, in which case there probably isn't much we can do. I don't know of any way to determine the type of AP remotely, and really what's probably a better test is using the device on a variety of networks and seeing if you have problems consistently or only with one particular network.

[Daniel Hershcovich (daniel-h)]

I was also affected by this problem (disconnects and frequent prompts for wireless authentication), and installing Wicd instead of Network Manager fixed it.

[David Navarro (dnbelmonte)]

When I put the command "iwconfig wlan0 power off", appears this message:

Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan0 ; Operation not supported.

I have ubuntu 11.04

any idea?

thanks a lot,

[Dennis van der Pool (dennisvanderpool)]

I thought my problem was fixed by installing WICD instead of Network Manager, but disabling power management did the trick! :-)

dennis@dennis-netbook:~$ sudo iwconfig wlan0 power off
dennis@dennis-netbook:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:"ddwrt"
          Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:10:AA:CE:46
          Bit Rate=54 Mb/s Tx-Power=13 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=41/70 Signal level=-69 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:745 Missed beacon:0

[Thomas (t-hartwig)]

Anybody an idea how to persist the powermanagement off solution?

[Dennis van der Pool (dennisvanderpool)]

Hi Thomas,

The option is persisted between reboots directly as far as i know.
No need to add line to some start-up script.
Can you try it?

Kind regards,

Dennis

[Thomas (t-hartwig)]

Thanks Dennis, indeed it kept off.

[Anton (antoskail)]

Same problem - WiFi reconnects all the time. I have found the problem after access-point reconfiguration and updates. Unfortunately I can't reproduce previous state.
Kernel 2.6.32-36-generic
Ubuntu 10.04.3 LTS
on Dell E6500

Solved similar to comment #20
except, I don't have "options.conf" in "/etc/modprobe.d/"

So, in file
         /etc/modprobe.d/alsa-base.conf
I have added the line
        options iwlagn 11n_disable=1 11n_disable50=1

[Paul Smith (psmith-gnu)]

I have this same problem (Ubuntu 11.10, dual-boot installation via Wubi, on a Samsung laptop--not sure of the model but it's brand new). lshw shows this for my wireless device:

                description: Wireless interface
                product: Centrino Advanced-N 6230
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:01:00.0
                logical name: wlan0
                version: 34
                serial: 88:53:2e:67:ea:85
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=iwlagn driverversion=3.0.0-12-generic firmware=17.168.5.1 build 33993 ip=192.168.1.108 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
                resources: irq:42 memory:c0500000-c0501fff

Disabling the power management via iwconfig seems to solve the problem. However, this is NOT persistent. When I reboot, it's set back to "on" and I get power issues.

I tried adding a script to /etc/network/if-pre-up.d that turned off power management, but that script was never being invoked (I added an echo to a file in /tmp which never showed up). I don't know why that script is not invoked??

I moved it to /etc/network/if-up.d and now it seems to work (although it takes a long time for me to get my first wireless connection, I think because the power management is not disabled until after the first connection).

Also, after rebooting a few times testing this out, my wireless got into some strange state where it would NEVER connect, and just continued to ask me for the wireless password (even though it already knew the right password). I rebooted into Windows, then back to Ubuntu, and so far it's been OK and the wireless is stable.

I really wonder why my pre-up scripts are not being invoked, though: I think if I could disable the power management before trying to bring up the interface I could connet

[Matt (mhhennig)]

Yes, that's it, turning wlan power management off solves the problem on a Thinkpad T500.

It is automatically enabled again though when I go to battery, but I have not yet been able to locate the relevant script (ubuntu 11.10). Anybody knows?

[RedCow (redcow)]

My dmesg looking like this:

[48754.543729] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[48754.752857] r8169 0000:02:00.0: eth0: link down
[48754.753212] ADDRCONF(NETDEV_UP): eth0: link is not ready
[48755.006093] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[48757.616276] wlan0: deauthenticating from 00:27:22:2e:a4:62 by local choice (reason=3)
[48757.650319] wlan0: authenticate with 00:27:22:2e:a4:62 (try 1)
[48757.652508] wlan0: authenticated
[48757.672121] wlan0: associate with 00:27:22:2e:a4:62 (try 1)
[48757.872078] wlan0: associate with 00:27:22:2e:a4:62 (try 2)
[48758.072074] wlan0: associate with 00:27:22:2e:a4:62 (try 3)
[48758.272071] wlan0: association with 00:27:22:2e:a4:62 timed out
[48790.756833] wlan0: authenticate with 00:27:22:2e:a4:62 (try 1)
[48790.758774] wlan0: authenticated
[48790.758832] wlan0: associate with 00:27:22:2e:a4:62 (try 1)
[48790.761998] wlan0: RX AssocResp from 00:27:22:2e:a4:62 (capab=0x431 status=0 aid=1)
[48790.762006] wlan0: associated
[48790.762598] ADDRCONF(NETDEV_CHANGE): drops wlan0: link becomes ready
[48792.917396] wlan0: deauthenticating from 00:27:22:2e:a4:62 by local choice (reason=3)
[48792.939219] cfg80211: All devices are disconnected, going to restore regulatory settings
[48792.939231] cfg80211: Restoring regulatory settings
[48792.939263] cfg80211: Calling CRDA to update world regulatory domain
[48792.951931] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
[48792.951952] cfg80211: World regulatory domain updated:

Seems, like network manager drops not only wireless, but wired connection too

Only manual reconnecting in network-manager (somtimes more then once) helps.

Linux s205 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 athlon i386 GNU/Linux
access-point is NanoStation Loco m2
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
Linux Mint 11 Katya

[RedCow (redcow)]

Found solution here:
http://azitech.wordpress.com/2010/02/22/deauthenticating-reason3/

killing wpa_supplicant helps. Daemon immediately resurrects and connection becoming stable.

[Dean McLennan (dgmclennan)]

Setting the BSSID in network-manager has stabilized the deauths (ath9k) You can also try Wicd as some have had positive results as well.

[Kaspars (stiebrs)]

Same here :
kernel 2.6.32-5-686
wpasupplicant 0.6.10-2.1
eth1: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.60.48.36

Feb 15 14:09:42 longitude wpa_supplicant[1576]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Feb 15 14:09:42 longitude NetworkManager[1541]: <info> (eth1): supplicant connection state: completed -> disconnected
Feb 15 14:09:42 longitude NetworkManager[1541]: <info> (eth1): supplicant connection state: disconnected -> scanning
Feb 15 14:09:45 longitude dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Feb 15 14:09:45 longitude dhclient: Copyright 2004-2010 Internet Systems Consortium.
Feb 15 14:09:45 longitude dhclient: All rights reserved.
Feb 15 14:09:45 longitude dhclient: For info, please visit https://www.isc.org/software/dhcp/
Feb 15 14:09:45 longitude dhclient:
Feb 15 14:09:45 longitude dhclient: Listening on LPF/eth1/00:23:4e:ab:8d:00
Feb 15 14:09:45 longitude dhclient: Sending on LPF/eth1/00:23:4e:ab:8d:00
Feb 15 14:09:45 longitude dhclient: Sending on Socket/fallback
Feb 15 14:09:45 longitude dhclient: DHCPRELEASE on eth1 to 172.19.8.1 port 67
Feb 15 14:09:45 longitude avahi-daemon[1487]: Withdrawing address record for 192.168.1.75 on eth1.
Feb 15 14:09:45 longitude avahi-daemon[1487]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.75.
Feb 15 14:09:45 longitude avahi-daemon[1487]: Interface eth1.IPv4 no longer relevant for mDNS.
Feb 15 14:09:45 longitude dhclient: receive_packet failed on eth1: Network is down
Feb 15 14:09:45 longitude wpa_supplicant[1576]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Feb 15 14:09:45 longitude NetworkManager[1541]: <info> (eth1): supplicant connection state: scanning -> disconnected
Feb 15 14:09:45 longitude dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Feb 15 14:09:45 longitude dhclient: Copyright 2004-2010 Internet Systems Consortium.
Feb 15 14:09:45 longitude dhclient: All rights reserved.
Feb 15 14:09:45 longitude dhclient: For info, please visit https://www.isc.org/software/dhcp/
Feb 15 14:09:45 longitude dhclient:
Feb 15 14:09:45 longitude dhclient: Listening on LPF/eth0/00:21:9b:e0:44:5a
Feb 15 14:09:45 longitude dhclient: Sending on LPF/eth0/00:21:9b:e0:44:5a
Feb 15 14:09:45 longitude dhclient: Sending on Socket/fallback
Feb 15 14:09:45 longitude dhclient: DHCPRELEASE on eth0 to 193.40.5.35 port 67
Feb 15 14:09:45 longitude dhclient: send_packet: Network is unreachable
Feb 15 14:09:45 longitude dhclient: send_packet: please consult README file regarding broadcast address.
Feb 15 14:09:45 longitude kernel: [13853.020452] tg3 0000:09:00.0: irq 29 for MSI/MSI-X
Feb 15 14:09:46 longitude NetworkManager[1541]: <info> (eth1): roamed from BSSID 00:0E:8E:7A:32:08 (ap11g) to (none) ((none))
Feb 15 14:09:48 longitude NetworkManager[1541]: <info> (eth1): supplicant connection state: disconnected -> scanning
Feb 15 14:09:53 longitude wpa_supplicant[1576]: Trying to associate with 00:0e:8e:7a:32:08 (SSID='ap11g' freq=2437 MHz)
Feb 15 14:09:53 longitude NetworkManager[1541]: <info> (eth1): supplicant connection state: scanni...

[Thomas Schweikle (tps)]

Same for oneiric and precise. Both are not able to build up a working WLAN connection.
None of the workarounds mentioned works for both of them.

[Thomas Schweikle (tps)]

wicd does not run with oneiric or precise (seems not to be worked on any more since 2010).
Adding ip6.disable=1 to kernel command line doesn't have any effect.
Adding various parameters to iwlxxxx-modules doesn't have any effect.

[Thomas Schweikle (tps)]

Looks like Network Manager is badly broken using any WLAN module.

Networking does work with:
- eth0, usb0

It does not work using:
- wlan0

[Thomas Schweikle (tps)]

Since a fix was released (according to the bug reports state), and the bug is there again, I suppose it a regression with oneiric and precise!

[Matt (mhhennig)]

As I said earlier, this problem is clearly linked to power management.

Type

iwconfig wlan0 power off

and the problem is gone!

So it's probably a kernel issue.

[Thomas Schweikle (tps)]

The bug seems related to various errors never reported by NetworkManager:

For WLAN:
authentication is perfect. Communication too, but the connection is terminated because of Reason 3 (whatever this means).
In between the connection is assigned an IP address. Doing:
dhclient wlan0
shortly later the connection is functional and up for hours! But: dhclient throws two error messages.

For USB:
All working, IP is assigned, then deassigned again. No error messages logged. Doing:
dhclient usb0
shortly later the connection is up and running, but dhclient throws two error messages.

I had a look at NetworkManager to find out why no errors are reported --- quite simple: NetworkManager just ignores them, but deconfigures the interface.

The error messages thrown by dhclient:
# dhclient wlan0
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service smbd reload

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the reload(8) utility, e.g. reload smbd
RTNETLINK answers: File exists
/etc/dhcp/dhclient-script: line 40: local: `new_resolv.dhcp': not a valid identifier
/etc/dhcp/dhclient-script: line 46: new_resolv.dhcp=/etc/resolv.dhcp.dhclient-new: No such file or directory

I did not look deep enough to find out what "dhclient" is calling while initializing the interface. At least: an IP-address is assigned and the connection is working.

[Thomas Schweikle (tps)]

@Matt:
# iwconfig wlan0 power off
Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan0 ; Operation not supported.

[Thomas Schweikle (tps)]

Looks like this is what we see if there are a bundle of errors at very different places, but the main software (NetworkManager) doesn't report them the way it should do -- ignoring some of them, while acting on others, but for none of them giving back useful information.

In my opinion: NetworkManager was a badly written peace of software. -- And this hasn't changed since. But all rely on this stuff, because all concurrent projects have died or are not worked anymore on.

[Thomas Schweikle (tps)]

# iwconfig
[...]
wlan0 IEEE 802.11abg ESSID:off/any
          Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Encryption key:off
          Power Management:off
[...]

I've removed the various other interface lines.

[Matt (mhhennig)]

On Sun, 2012-03-04 at 16:15 +0000, Thomas Schweikle wrote:
> # iwconfig
> [...]
> wlan0 IEEE 802.11abg ESSID:off/any
> Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off

I see, this looks ok. In my case it is different, it is clearly the
power management, this is 100% reproducible (on a Thinkpad T500, kernel
3.1.6).

[Mathieu Trudel-Lapierre (cyphermox)]

This bug was closed as Fixed Released -- this means we believe the problem was truly found and corrected. If you're still running into issues, please make sure you file a new, separate bug for your own hardware, using the 'ubuntu-bug linux' command; this will file a new bug in Launchpad which the developers will be able to mark as duplicate if necessary. Thanks!

[Thomas Hood (jdthood)]

@sillyxone, @Rasmus, @ricolai: You mentioned that you only have a problem with WPA-Enterprise. Please see bug #1020775.

[Faré (fahree)]

Note that I had a problem with the same symptom, and in the end, what solved it was killing wpa_supplicant, as suggested in this bug comment:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1294044/comments/9