[SOLVED] WiFi connection drops

zoryfl · 2011-12-18 08:55:27

Hey guys,

I'm having some trouble with my WiFi connection lately as it tends to drop the connection every like 2-10 mins.
It is not directly linked to any specific action, it just happens while browsing the web, watching a video or chatting.

It's definitely not hardware related either as I do not have any connection losses when running windows on the same laptop (Dell Latitude E4300).

lspci: 0c:00.0 Network controller: Intel Corporation WiFi Link 5100

iwconfig: wlan0 IEEE 802.11abgn ESSID:"****"
Mode:Managed Frequency:2.422 GHz Access Point: 00:1C:28:1C:D6:8A
Bit Rate=54 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=61/70 Signal level=-49 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:14 Missed beacon:0

Is this some known bug or is anyone else having the same problem? I couldn't find anything specifically similar to my problem on the forums and the rest of the web but maybe you guys know how to fix this?!

Cheers
Tobi

Last edited by zoryfl (2012-02-20 17:32:38)

/dev/zero · 2011-12-18 09:01:33

What network software do you use?

zoryfl · 2011-12-18 09:34:19

I'm using netcfg if that's what you mean?

/dev/zero · 2011-12-18 10:02:29

zoryfl wrote:

I'm using netcfg if that's what you mean?

Yep, that's what I mean. But I'm not familiar with netcfg, so can't help more than this, sorry.

If you were using wicd, I would suggest testing whether you still have the same problems under wpa_supplicant + dhcpcd.

zoryfl · 2011-12-18 10:15:23

Ahh, that's too bad.. thanks though!

I'm really puzzled about what's going on with this thing. It probably has something to do with a kernel update or whatever but then again why doesn't anyone else have this problem?!

kurych · 2011-12-18 10:51:22

In my expirience:
Loss connect may be triggered by the access point, not client side. I had an old "d-link di-524", which dropped connection every 3-5 minutes. "Wicd" in Linux and Windows could make monitoring such gaps and reconnects again. Pure WPA_supplicant does not make reconnecting in such situations.
With the new router I not observed such disconnects.

Lars Stokholm · 2011-12-18 10:55:01

I would still try wpa_supplicant and dhcpcd to see if the problem persists. Perhaps wpa_supplicant outputs something useful.

wpa_passphrase ESSID PASSPRASE >wpa_supplicant.conf
wpa_supplicant -i wlan0 -c wpa_supplicant.conf
dhcpcd -B wlan0

zoryfl · 2011-12-18 11:14:25

kurych wrote:

In my expirience:
Loss connect may be triggered by the access point, not client side. I had an old "d-link di-524", which dropped connection every 3-5 minutes. "Wicd" in Linux and Windows could make monitoring such gaps and reconnects again. Pure WPA_supplicant does not make reconnecting in such situations.
With the new router I not observed such disconnects.

Thank you for your reply, but as I said I am not experiencing any disconnects when working with windows7 and I do have the same router I always had before so I guess that's not it.

@Lars Stokholm: I'll try that as soon as I can get to it, thanks in advance.

zoryfl · 2011-12-18 11:43:08

Alright, so I just tried to do what Lars told me to.
wpa_supplicant didn't manage to connect to the web at any point showing an output like this:

--------------------------

And dhcpcd said this:

---------------

Unfortunately I can't read anything out of these logs.. and again, I don't know why it didn't even manage to connect via wpa_supplicant?

-------------------

edit: don't know what I did wrong before, but it managed to connect this time. Here's the output:
wpa_supplicant:

Trying to associate with 00:1c:28:1c:d6:8a (SSID='Neto' freq=2422 MHz)
Associated with 00:1c:28:1c:d6:8a
WPA: Key negotiation completed with 00:1c:28:1c:d6:8a [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:1c:28:1c:d6:8a completed (auth) [id=0 id_str=]

dhcpcd:

dhcpcd[12213]: version 5.2.12 starting
dhcpcd[12213]: wlan0: waiting for carrier
dhcpcd[12213]: wlan0: carrier acquired
dhcpcd[12213]: wlan0: rebinding lease of 192.168.1.77
dhcpcd[12213]: wlan0: acknowledged 192.168.1.77 from 192.168.1.1
dhcpcd[12213]: wlan0: checking for 192.168.1.77
dhcpcd[12213]: wlan0: leased 192.168.1.77 for 604800 seconds
/usr/lib/dhcpcd/dhcpcd-hooks/30-hostname: line 9: hostname: command not found

Waiting for the disconnect to come..

Last edited by zoryfl (2011-12-18 11:54:49)

zoryfl · 2011-12-18 16:24:24

Alright, so it seems that the connection losses really just have the output "carrier lost" and then it reconnects.
Not much information in there, I guess.. so I guess it's back to the beginning: what could be the reason of those disconnects?

/dev/zero · 2011-12-18 18:50:36

zoryfl wrote:

Alright, so it seems that the connection losses really just have the output "carrier lost" and then it reconnects.
Not much information in there, I guess.. so I guess it's back to the beginning: what could be the reason of those disconnects?

On google, I see a lot of results when I search for,

Google Search wrote:

dhcpcd carrier lost

At least one response near the top also mentions netcfg. Seems like a good place to start.

zoryfl · 2012-01-21 10:36:08

So, I'm still struggling with these connection drops.
I switched to wicd as a network manager recently but I'm still getting the drops. What makes me curious is that I obviously don't lose the network connection, as I am still connected to the network as wicd tells me. Yet, I'm having 0 traffic and not only my browser but every other programm as well just don't have internet access anymore..

I checked dmesg to see what it says and found this:
[zoryfl@laptop ~]$ dmesg | grep wlan0

[ 61.180847] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 234.077785] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 234.449852] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 239.922104] wlan0: authenticate with 00:1c:28:1c:d6:8a (try 1)
[ 239.924442] wlan0: authenticated
[ 239.929178] wlan0: associate with 00:1c:28:1c:d6:8a (try 1)
[ 239.932895] wlan0: RX AssocResp from 00:1c:28:1c:d6:8a (capab=0x431 status=0 aid=3)
[ 239.932904] wlan0: associated
[ 239.946052] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 250.096688] wlan0: no IPv6 routers present
[ 1376.948827] wlan0: deauthenticating from 00:1c:28:1c:d6:8a by local choice (reason=3)
[ 1377.068053] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1384.751003] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1384.831128] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1385.180843] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1393.517403] wlan0: authenticate with 00:1c:28:1c:d6:8a (try 1)
[ 1393.519951] wlan0: authenticated
[ 1393.521334] wlan0: associate with 00:1c:28:1c:d6:8a (try 1)
[ 1393.525071] wlan0: RX AssocResp from 00:1c:28:1c:d6:8a (capab=0x431 status=0 aid=3)
[ 1393.525080] wlan0: associated
[ 1393.538443] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1403.669911] wlan0: no IPv6 routers present

Why does wlan0 appear two times?

Thanks again for everyone's help, much appreciated!

edit: when I lost the connection, dmesg output is as follows:

[ 34.060696] wlan0: authenticate with 00:1c:28:1c:d6:8a (try 1)
[ 34.063345] wlan0: authenticated
[ 34.064661] wlan0: waiting for beacon from 00:1c:28:1c:d6:8a
[ 34.126979] wlan0: beacon received
[ 34.160042] wlan0: associate with 00:1c:28:1c:d6:8a (try 1)
[ 34.163693] wlan0: RX AssocResp from 00:1c:28:1c:d6:8a (capab=0x431 status=0 aid=3)
[ 34.163697] wlan0: associated
[ 141.576698] wlan0: no IPv6 routers present

Last edited by zoryfl (2012-01-21 11:22:32)

cap_sensitive · 2012-01-22 13:48:39

maybe you can try `net-auto-wireless`, which is based on netcfg and can re-connect automatically (not fast enough, though)

zoryfl · 2012-01-22 21:12:20

Actually that's what I was using before wicd. Means it's not a solution but thank you anyway for trying!

edit:
As this sounds pretty similar to my problem, it seems to be an iwlwifi problem after all..
http://us.generation-nt.com/answer/bug- … 572.html#r

Last edited by zoryfl (2012-01-23 06:03:22)

masutu · 2012-01-28 20:54:05

You can try out to load the module with

modprobe iwlwifi 11n_disable=1 swcrypto=1

or, to make it permanent, create a file /etc/modprobe.d/iwlwifi.conf containing

#/etc/modprobe.d/iwlwifi.conf
options iwlwifi 11n_disable=1 swcrypto=1

That did it for me (i had the same problems: "wlan0: deauthenticating from 00:11:22:33:44:55 by local choice (reason=3)"). Don't know, if both parameters are needed, wasn't patient enough for testing.

yellowtrolley · 2012-02-05 22:55:58

masutu wrote:

You can try out to load the module with
modprobe iwlwifi 11n_disable=1 swcrypto=1 
or, to make it permanent, create a file /etc/modprobe.d/iwlwifi.conf containing
#/etc/modprobe.d/iwlwifi.conf
options iwlwifi 11n_disable=1 swcrypto=1
That did it for me (i had the same problems: "wlan0: deauthenticating from 00:11:22:33:44:55 by local choice (reason=3)"). Don't know, if both parameters are needed, wasn't patient enough for testing.

Big maustu! that did the job for me as well.

This problem may be related to iwlwifi and some adsl routers. Everything was ok for me until we changed internet provider. The new provider (Fastweb, italy). placed their own router. Since then, my connection drops every 15 minutes or so and then it hangs. I have to restart network in order to reconnect.

I tried disabling networmanager and connecting with wpa_supplicant and wpa_supplicant.conf and fiddling with the file templates but the problem persisted.

I did pacman -Syu after we got the new router. Just to verify that it is the new router causing the problem I downgraded iwlwifi to previous version and the problem persisted. I didn't bother downgrading the kernel though...

Booting the same pc with another distro that loads iwlagn everything is ok. Another pc with ubuntu that uses iwl3945 is also fine. The problem seems to be just with iwlwifi, my network card and that f...g router which I have not access to.
My network card is Intel WiFi Link 5300.

The logs in case it really is a problem with iwlwifi and someone know how to deal with it.

Feb  5 14:34:38 localhost NetworkManager[574]: <info> (wlan0): bringing up device.
Feb  5 14:34:38 localhost NetworkManager[574]: <info> WiFi hardware radio set enabled
Feb  5 14:34:38 localhost NetworkManager[574]: <info> WiFi now enabled by radio killswitch
Feb  5 14:34:38 localhost NetworkManager[574]: <info> (wlan0): bringing up device.
Feb  5 14:34:38 localhost kernel: [ 7642.175703] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Feb  5 14:34:38 localhost kernel: [ 7642.176099] iwlwifi 0000:03:00.0: Radio type=0x0-0x2-0x0
Feb  5 14:34:38 localhost NetworkManager[574]: <info> (wlan0): supplicant interface state: starting -> ready
Feb  5 14:34:38 localhost NetworkManager[574]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Feb  5 14:34:38 localhost NetworkManager[574]: <info> (wlan0): supplicant interface state: ready -> inactive
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Auto-activating connection 'FASTWEB-1-XqkFmfh2na6e'.
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) starting connection 'FASTWEB-1-XqkFmfh2na6e'
Feb  5 14:34:42 localhost NetworkManager[574]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb  5 14:34:42 localhost NetworkManager[574]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0/wireless): access point 'FASTWEB-1-XqkFmfh2na6e' has security, but secrets are required.
Feb  5 14:34:42 localhost NetworkManager[574]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb  5 14:34:42 localhost NetworkManager[574]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb  5 14:34:42 localhost NetworkManager[574]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0/wireless): connection 'FASTWEB-1-XqkFmfh2na6e' has security, and secrets exist.  No new secrets needed.
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Config: added 'ssid' value 'FASTWEB-1-XqkFmfh2na6e'
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Config: added 'scan_ssid' value '1'
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Config: added 'psk' value '<omitted>'
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb  5 14:34:42 localhost NetworkManager[574]: <info> Config: set interface ap_scan to 1
Feb  5 14:34:42 localhost NetworkManager[574]: <info> (wlan0): supplicant interface state: inactive -> scanning
Feb  5 14:34:45 localhost NetworkManager[574]: <info> (wlan0): supplicant interface state: scanning -> associating
Feb  5 14:34:45 localhost NetworkManager[574]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Feb  5 14:34:45 localhost NetworkManager[574]: <info> (wlan0): supplicant interface state: 4-way handshake -> group handshake
Feb  5 14:34:45 localhost NetworkManager[574]: <info> (wlan0): supplicant interface state: group handshake -> completed
Feb  5 14:34:45 localhost NetworkManager[574]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'FASTWEB-1-XqkFmfh2na6e'.
Feb  5 14:34:45 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb  5 14:34:45 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Feb  5 14:34:45 localhost NetworkManager[574]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb  5 14:34:45 localhost NetworkManager[574]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb  5 14:34:45 localhost NetworkManager[574]: <info> dhcpcd started with pid 6079
Feb  5 14:34:45 localhost NetworkManager[574]: <info> Activation (wlan0) Beginning IP6 addrconf.
Feb  5 14:34:45 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Feb  5 14:34:45 localhost dhcpcd[6079]: version 5.2.12 starting
Feb  5 14:34:45 localhost NetworkManager[574]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Feb  5 14:34:45 localhost dhcpcd[6079]: wlan0: rebinding lease of 192.168.1.128
Feb  5 14:34:45 localhost dhcpcd[6079]: wlan0: acknowledged 192.168.1.128 from 192.168.1.254
Feb  5 14:34:45 localhost dhcpcd[6079]: wlan0: leased 192.168.1.128 for 1800 seconds
Feb  5 14:34:45 localhost NetworkManager[574]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Feb  5 14:34:45 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Feb  5 14:34:45 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Feb  5 14:34:45 localhost NetworkManager[574]: <info>   address 192.168.1.128
Feb  5 14:34:45 localhost NetworkManager[574]: <info>   prefix 24 (255.255.255.0)
Feb  5 14:34:45 localhost NetworkManager[574]: <info>   gateway 192.168.1.254
Feb  5 14:34:45 localhost NetworkManager[574]: <info>   hostname 'pabhost'
Feb  5 14:34:45 localhost NetworkManager[574]: <info>   nameserver '62.101.93.101'
Feb  5 14:34:45 localhost NetworkManager[574]: <info>   nameserver '83.103.25.250'
Feb  5 14:34:45 localhost NetworkManager[574]: <info>   domain name 'fastwebnet.it'
Feb  5 14:34:45 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Feb  5 14:35:05 localhost NetworkManager[574]: <info> (wlan0): IP6 addrconf timed out or failed.
Feb  5 14:35:05 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) scheduled...
Feb  5 14:35:05 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) started...
Feb  5 14:35:05 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Feb  5 14:35:05 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) complete.
Feb  5 14:35:05 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Feb  5 14:35:06 localhost NetworkManager[574]: <info> (wlan0): writing resolv.conf to /usr/sbin/resolvconf
Feb  5 14:35:06 localhost NetworkManager[574]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Feb  5 14:35:06 localhost NetworkManager[574]: <info> Policy set 'FASTWEB-1-XqkFmfh2na6e' (wlan0) as default for IPv4 routing and DNS.
Feb  5 14:35:06 localhost NetworkManager[574]: <info> Activation (wlan0) successful, device activated.
Feb  5 14:35:06 localhost NetworkManager[574]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Feb  5 14:35:06 localhost dbus[548]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb  5 14:35:06 localhost dbus[548]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb  5 14:49:46 localhost dhcpcd[6079]: wlan0: renewing lease of 192.168.1.128
Feb  5 14:49:46 localhost dhcpcd[6079]: wlan0: acknowledged 192.168.1.128 from 192.168.1.254
Feb  5 14:49:46 localhost dhcpcd[6079]: wlan0: leased 192.168.1.128 for 1800 seconds
Feb  5 14:49:46 localhost NetworkManager[574]: <info> (wlan0): DHCPv4 state changed reboot -> renew
Feb  5 14:49:46 localhost NetworkManager[574]: <info>   address 192.168.1.128
Feb  5 14:49:46 localhost NetworkManager[574]: <info>   prefix 24 (255.255.255.0)
Feb  5 14:49:46 localhost NetworkManager[574]: <info>   gateway 192.168.1.254
Feb  5 14:49:46 localhost NetworkManager[574]: <info>   hostname 'pabhost'
Feb  5 14:49:46 localhost NetworkManager[574]: <info>   nameserver '62.101.93.101'
Feb  5 14:49:46 localhost NetworkManager[574]: <info>   nameserver '83.103.25.250'
Feb  5 14:49:46 localhost NetworkManager[574]: <info>   domain name 'fastwebnet.it'
Feb  5 14:49:46 localhost dbus[548]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb  5 14:49:46 localhost dbus[548]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb  5 15:04:46 localhost dhcpcd[6079]: wlan0: renewing lease of 192.168.1.128
Feb  5 15:09:57 localhost NetworkManager[574]: <info> (wlan0): device state change: activated -> unavailable (reason 'none') [100 20 0]
Feb  5 15:09:57 localhost NetworkManager[574]: <info> (wlan0): deactivating device (reason 'none') [0]
Feb  5 15:09:57 localhost dhcpcd[6079]: received SIGTERM, stopping
Feb  5 15:09:57 localhost dhcpcd[6079]: wlan0: removing interface
Feb  5 15:09:57 localhost NetworkManager[574]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 6079
Feb  5 15:09:57 localhost NetworkManager[574]: <info> (wlan0): removing resolv.conf from /usr/sbin/resolvconf
Feb  5 15:09:57 localhost dbus[548]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb  5 15:09:57 localhost dbus[548]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb  5 15:09:57 localhost NetworkManager[574]: <info> (wlan0): taking down device.
Feb  5 15:09:57 localhost kernel: [ 9761.463858] cfg80211: Calling CRDA to update world regulatory domain
Feb  5 15:09:57 localhost NetworkManager[574]: <info> WiFi hardware radio set disabled
Feb  5 15:09:57 localhost NetworkManager[574]: <info> WiFi now disabled by radio killswitch
Feb  5 15:09:57 localhost NetworkManager[574]: <warn> (pid 6079) unhandled DHCP event for interface wlan0

zoryfl · 2012-02-20 17:32:27

masutu wrote:

You can try out to load the module with
modprobe iwlwifi 11n_disable=1 swcrypto=1 
or, to make it permanent, create a file /etc/modprobe.d/iwlwifi.conf containing
#/etc/modprobe.d/iwlwifi.conf
options iwlwifi 11n_disable=1 swcrypto=1
That did it for me (i had the same problems: "wlan0: deauthenticating from 00:11:22:33:44:55 by local choice (reason=3)"). Don't know, if both parameters are needed, wasn't patient enough for testing.

I don't know how but it really did the job! Awesome, thank you!

LLStarks · 2012-02-21 18:34:03

Keep bothering the devs about this bug

http://bugzilla.intellinuxwireless.org/ … gi?id=2328

Viper_Scull · 2012-03-20 23:55:50

I have the same behaviour on my laptop, but in this case i'm using iwl3945.
I tried loading the module with the option 11n_disable but my card doesn't have that parameter.

[bary@Arch-laptop ~]$ ls /sys/module/iwl3945/parameters
antenna  disable_hw_scan  fw_restart  swcrypto

Last edited by Viper_Scull (2012-03-21 00:43:20)

dara0418 · 2014-01-04 00:46:20

Super! I've tried several workarounds but just this one works. It resolves the long-term unstable wireless connection issue which affected me for almost a whole year.

fukawi2 · 2014-01-04 01:23:02

Welcome to the Arch Forums dara0418 - please take a few minutes to review our Forum Etiquette, particularly in regard to raising the dead: https://wiki.archlinux.org/index.php/Fo … Bumping.22

Closing.

Arch Linux

#1 2011-12-18 08:55:27

[SOLVED] WiFi connection drops

#2 2011-12-18 09:01:33

Re: [SOLVED] WiFi connection drops

#3 2011-12-18 09:34:19

Re: [SOLVED] WiFi connection drops

#4 2011-12-18 10:02:29

Re: [SOLVED] WiFi connection drops

#5 2011-12-18 10:15:23

Re: [SOLVED] WiFi connection drops

#6 2011-12-18 10:51:22

Re: [SOLVED] WiFi connection drops

#7 2011-12-18 10:55:01

Re: [SOLVED] WiFi connection drops

#8 2011-12-18 11:14:25

Re: [SOLVED] WiFi connection drops

#9 2011-12-18 11:43:08

Re: [SOLVED] WiFi connection drops

#10 2011-12-18 16:24:24

Re: [SOLVED] WiFi connection drops

#11 2011-12-18 18:50:36

Re: [SOLVED] WiFi connection drops

#12 2012-01-21 10:36:08

Re: [SOLVED] WiFi connection drops

#13 2012-01-22 13:48:39

Re: [SOLVED] WiFi connection drops

#14 2012-01-22 21:12:20

Re: [SOLVED] WiFi connection drops

#15 2012-01-28 20:54:05

Re: [SOLVED] WiFi connection drops

#16 2012-02-05 22:55:58

Re: [SOLVED] WiFi connection drops

#17 2012-02-20 17:32:27

Re: [SOLVED] WiFi connection drops

#18 2012-02-21 18:34:03

Re: [SOLVED] WiFi connection drops

#19 2012-03-20 23:55:50

Re: [SOLVED] WiFi connection drops

#20 2014-01-04 00:46:20

Re: [SOLVED] WiFi connection drops

#21 2014-01-04 01:23:02

Re: [SOLVED] WiFi connection drops

Board footer