unable to associate to wireless network

bygmhra · 2014-12-12 22:15:03

I have had this issue the entire time I have my current laptop: after resuming from suspend, it is very difficult to reassociate to the wireless network. It can take at least 10 minutes. Often I "solve" this by restarting my computer. Still takes some time to associate, but not nearly as much.

As of yesterday this "solution" does not seem to be working. I am absolutely unable to connect to wireless. (No issues with wired.)

Please let me know what other information would be helpful:

$ lspci -k | grep Network
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe Wireless Network Adapter

$ journalctl -f
-- Logs begin at Thu 2014-09-18 17:50:29 PDT. --
Dec 12 14:03:32 phorcys polkitd[906]: Loading rules from directory /usr/share/polkit-1/rules.d
Dec 12 14:03:32 phorcys polkitd[906]: Finished loading, compiling and executing 1 rules
Dec 12 14:03:32 phorcys dbus[298]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Dec 12 14:03:32 phorcys polkitd[906]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Dec 12 14:03:36 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c8:32
Dec 12 14:03:36 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:03:36 phorcys kernel: wlp3s0: authenticated
Dec 12 14:03:36 phorcys kernel: wlp3s0: associate with 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:03:36 phorcys kernel: wlp3s0: RX AssocResp from 00:3a:98:c0:c8:32 (capab=0x401 status=17 aid=0)
Dec 12 14:03:36 phorcys kernel: wlp3s0: 00:3a:98:c0:c8:32 denied association (code=17)
Dec 12 14:03:45 phorcys sudo[913]: moonlight : TTY=pts/2 ; PWD=/home/moonlight/my_internet_probs ; USER=root ; COMMAND=/usr/bin/systemctl restart netctl-auto@wlp3s0.service
Dec 12 14:03:45 phorcys sudo[913]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 12 14:03:45 phorcys wpa_actiond[326]: Terminating wpa_actiond session for interface 'wlp3s0'
Dec 12 14:03:47 phorcys netctl-auto[944]: Included profile 'eduroam'
Dec 12 14:03:47 phorcys kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Dec 12 14:03:47 phorcys wpa_actiond[972]: Starting wpa_actiond session for interface 'wlp3s0'
Dec 12 14:03:47 phorcys sudo[913]: pam_unix(sudo:session): session closed for user root
Dec 12 14:03:49 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c8:32
Dec 12 14:03:49 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:03:49 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 2/3)
Dec 12 14:03:49 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 3/3)
Dec 12 14:03:49 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:c8:32 timed out
Dec 12 14:03:49 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:cc:02
Dec 12 14:03:49 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:cc:02 (try 1/3)
Dec 12 14:03:49 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:cc:02 (try 2/3)
Dec 12 14:03:49 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:cc:02 (try 3/3)
Dec 12 14:03:50 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:cc:02 timed out
Dec 12 14:03:50 phorcys kernel: wlp3s0: authenticate with 00:3a:98:cb:1e:82
Dec 12 14:03:50 phorcys kernel: wlp3s0: send auth to 00:3a:98:cb:1e:82 (try 1/3)
Dec 12 14:03:50 phorcys kernel: wlp3s0: send auth to 00:3a:98:cb:1e:82 (try 2/3)
Dec 12 14:03:50 phorcys kernel: wlp3s0: send auth to 00:3a:98:cb:1e:82 (try 3/3)
Dec 12 14:03:50 phorcys kernel: wlp3s0: authentication with 00:3a:98:cb:1e:82 timed out
Dec 12 14:03:50 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c9:a2
Dec 12 14:03:50 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c9:a2 (try 1/3)
Dec 12 14:03:51 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c9:a2 (try 2/3)
Dec 12 14:03:51 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c9:a2 (try 3/3)
Dec 12 14:03:51 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:c9:a2 timed out
Dec 12 14:03:51 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c9:82
Dec 12 14:03:51 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c9:82 (try 1/3)
Dec 12 14:03:51 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c9:82 (try 2/3)
Dec 12 14:03:51 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c9:82 (try 3/3)
Dec 12 14:03:51 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:c9:82 timed out
Dec 12 14:03:52 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c8:32
Dec 12 14:03:53 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:03:53 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 2/3)
Dec 12 14:03:53 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 3/3)
Dec 12 14:03:53 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:c8:32 timed out
Dec 12 14:03:54 phorcys ntpd[328]: Deleting interface #9 wlp3s0, fe80::1acf:5eff:febd:6dc3%3#123, interface stats: received=0, sent=0, dropped=0, active_time=636 secs
Dec 12 14:03:54 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:cc:02
Dec 12 14:03:54 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:cc:02 (try 1/3)
Dec 12 14:03:54 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:cc:02 (try 2/3)
Dec 12 14:03:54 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:cc:02 (try 3/3)
Dec 12 14:03:54 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:cc:02 timed out
Dec 12 14:03:56 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c9:a2
Dec 12 14:03:56 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c9:a2 (try 1/3)
Dec 12 14:03:56 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c9:a2 (try 2/3)
Dec 12 14:03:56 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c9:a2 (try 3/3)
Dec 12 14:03:56 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:c9:a2 timed out
Dec 12 14:03:57 phorcys kernel: wlp3s0: authenticate with 00:3a:98:cb:1e:82
Dec 12 14:03:57 phorcys kernel: wlp3s0: send auth to 00:3a:98:cb:1e:82 (try 1/3)
Dec 12 14:03:57 phorcys kernel: wlp3s0: send auth to 00:3a:98:cb:1e:82 (try 2/3)
Dec 12 14:03:57 phorcys kernel: wlp3s0: send auth to 00:3a:98:cb:1e:82 (try 3/3)
Dec 12 14:03:57 phorcys kernel: wlp3s0: authentication with 00:3a:98:cb:1e:82 timed out
Dec 12 14:03:59 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c9:82
Dec 12 14:03:59 phorcys kernel: wlp3s0: direct probe to 00:3a:98:c0:c9:82 (try 1/3)
Dec 12 14:03:59 phorcys kernel: wlp3s0: direct probe to 00:3a:98:c0:c9:82 (try 2/3)
Dec 12 14:03:59 phorcys kernel: wlp3s0: direct probe to 00:3a:98:c0:c9:82 (try 3/3)
Dec 12 14:03:59 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:c9:82 timed out
Dec 12 14:04:01 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c8:32
Dec 12 14:04:01 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:04:01 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 2/3)
Dec 12 14:04:01 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 3/3)
Dec 12 14:04:02 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:c8:32 timed out
Dec 12 14:04:12 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:cc:02
Dec 12 14:04:12 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:cc:02 (try 1/3)
Dec 12 14:04:12 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:cc:02 (try 2/3)
Dec 12 14:04:12 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:cc:02 (try 3/3)
Dec 12 14:04:12 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:cc:02 timed out
Dec 12 14:04:40 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c8:32
Dec 12 14:04:40 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:04:40 phorcys kernel: wlp3s0: authenticated
Dec 12 14:04:40 phorcys kernel: wlp3s0: associate with 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:04:40 phorcys kernel: wlp3s0: RX AssocResp from 00:3a:98:c0:c8:32 (capab=0x401 status=17 aid=0)
Dec 12 14:04:40 phorcys kernel: wlp3s0: 00:3a:98:c0:c8:32 denied association (code=17)
Dec 12 14:05:27 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c8:32
Dec 12 14:05:27 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:05:27 phorcys kernel: wlp3s0: authenticated
Dec 12 14:05:27 phorcys kernel: wlp3s0: associate with 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:05:27 phorcys kernel: wlp3s0: associate with 00:3a:98:c0:c8:32 (try 2/3)
Dec 12 14:05:27 phorcys kernel: wlp3s0: RX AssocResp from 00:3a:98:c0:c8:32 (capab=0x411 status=0 aid=115)
Dec 12 14:05:27 phorcys kernel: wlp3s0: associated
Dec 12 14:05:27 phorcys kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Dec 12 14:05:28 phorcys wpa_actiond[972]: Interface 'wlp3s0' connecting failed
Dec 12 14:05:30 phorcys ntpd[328]: Listen normally on 10 wlp3s0 [fe80::1acf:5eff:febd:6dc3%3]:123
Dec 12 14:05:30 phorcys ntpd[328]: new interface(s) found: waking up resolver
Dec 12 14:05:30 phorcys kernel: wlp3s0: deauthenticating from 00:3a:98:c0:c8:32 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 12 14:05:30 phorcys kernel: cfg80211: Calling CRDA to update world regulatory domain
Dec 12 14:06:52 phorcys kernel: wlp3s0: authenticate with 00:3a:98:c0:c8:32
Dec 12 14:06:52 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 1/3)
Dec 12 14:06:52 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 2/3)
Dec 12 14:06:52 phorcys kernel: wlp3s0: send auth to 00:3a:98:c0:c8:32 (try 3/3)
Dec 12 14:06:52 phorcys kernel: wlp3s0: authentication with 00:3a:98:c0:c8:32 timed out
^C

TheSaint · 2014-12-13 06:06:14

bygmhra wrote:

Dec 12 14:03:36 phorcys kernel: wlp3s0: 00:3a:98:c0:c8:32 denied association (code=17)

Can you try to connect with static IP ?

WonderWoofy · 2014-12-13 06:44:07

TheSaint wrote:

bygmhra wrote:
Dec 12 14:03:36 phorcys kernel: wlp3s0: 00:3a:98:c0:c8:32 denied association (code=17)
Can you try to connect with static IP ?

From what you quoted there, a static IP would definitely not work. The OP has not successfully authenticated with the AP.

@OP, can you try stopping any network maangement services you use (it appears that this is netctl)? Then use the tools directly to try to get things going. This will include wpa_supplicant/wpa_passphrase to associate with the AP, then using the dhcp client of your choice to get an IP address.

You won't have to stay with this manual process, but it can serve as a good way to try to debug the problem. I also feel as though knowing how to manually connect to a wireless network is a good thing to know as a Linux user in general.

TheSaint · 2014-12-13 13:40:13

Static, may not involve the use of passwords.
Probably I was unclear, sorry about that. I meant to try a simple connection without the use of dhcpcd. Then later try to step further on DHCP and later on encrypted connection.

WonderWoofy · 2014-12-13 23:28:21

TheSaint wrote:

Static, may not involve the use of passwords.
Probably I was unclear, sorry about that. I meant to try a simple connection without the use of dhcpcd. Then later try to step further on DHCP and later on encrypted connection.

What? This is even less clear.

Yes, using a static IP would no longer involve using dhcpcd (or any dhcp client). But if the OP isn't properly associated to the wireless access point, it will do absolutely nothing to improve the situation.

TheSaint · 2014-12-14 09:07:08

OK, sorry, I was wrong.
See what about code=17:

code 17 = Association denied because AP is unable to handle additional associated stations

vri · 2014-12-14 20:50:47

Edit: moved to new thread.

Theo

Last edited by vri (2014-12-15 10:45:21)

WonderWoofy · 2014-12-15 01:04:14

@vri, it appears from your log output that this may be a separate issue. You probably should have started your own thread on this, as merging is pretty easy.

ewaller · 2014-12-15 02:16:01

Moderator comment.
I agree with WonderWoofy. Please do start a new thread.

Thanks.

bygmhra · 2015-03-31 16:57:31

TheSaint wrote:

OK, sorry, I was wrong.
See what about code=17:
code 17 = Association denied because AP is unable to handle additional associated stations

This makes sense to me. The network is my university's so there are probably a lot of people connecting. But then I would expect other students to also have issues associating but it seems to be only me.

Other Linux users seem to not have this problem. Haven't encountered any other archers though....

Arch Linux

#1 2014-12-12 22:15:03

unable to associate to wireless network

#2 2014-12-13 06:06:14

Re: unable to associate to wireless network

#3 2014-12-13 06:44:07

Re: unable to associate to wireless network

#4 2014-12-13 13:40:13

Re: unable to associate to wireless network

#5 2014-12-13 23:28:21

Re: unable to associate to wireless network

#6 2014-12-14 09:07:08

Re: unable to associate to wireless network

#7 2014-12-14 20:50:47

Re: unable to associate to wireless network

#8 2014-12-15 01:04:14

Re: unable to associate to wireless network

#9 2014-12-15 02:16:01

Re: unable to associate to wireless network

#10 2015-03-31 16:57:31

Re: unable to associate to wireless network

Board footer