Arch Linux

cristianpark

Member

Registered: 2011-10-20

Posts: 7

Problems connecting to an specific wireless router (Atheros+Asus)

Hi guys

I'm facing a problem with my home wireless router (Netgear WGT624v3), I can't connect to the router (it's using WPA2 encryption) and have the following error in dmesg

[ 9573.889377] ath9k 0000:02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP
[ 9573.889380] ath9k 0000:02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP
[ 9573.891645] wlp2s0: associate with 00:18:4d:85:53:66 (try 1/3)
[ 9573.995005] wlp2s0: associate with 00:18:4d:85:53:66 (try 2/3)
[ 9574.098319] wlp2s0: associate with 00:18:4d:85:53:66 (try 3/3)
[ 9574.201673] wlp2s0: association with 00:18:4d:85:53:66 timed out
[ 9589.981595] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

My device an controller information is

02:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
	Subsystem: Lite-On Communications Inc Device 6627
	Kernel driver in use: ath9k
	Kernel modules: ath9k

I tried with NetworkManager and wicd without any luck, I tried to connect using WPA supplicant and get errors too

 # wpa_supplicant -i wlp2s0 -c <(wpa_passphrase "SSID" "password")
Successfully initialized wpa_supplicant
wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="OurCovine" auth_failures=1 duration=10 reason=CONN_FAILED
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="OurCovine"
wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="OurCovine" auth_failures=2 duration=23 reason=CONN_FAILED

I'm out of options right now so I'm thinking in reinstalling my 3 years old (but up to date) ArchLinux installation. Do you have any advice to me?

Thanks in advance

Last edited by cristianpark (2017-06-23 22:15:36)

R00KIE

Forum Fellow

From: Between a computer and a chair

Registered: 2008-09-14

Posts: 4,734

Re: Problems connecting to an specific wireless router (Atheros+Asus)

Disable all your network manager programs, which in your case seems to be networkmanager, and then try connecting manually with wpa_supplicant and a dhcp client and see if it works. If it doesn't work post the full connection log.

---

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

cristianpark

Member

Registered: 2011-10-20

Posts: 7

Re: Problems connecting to an specific wireless router (Atheros+Asus)

Hi ROOKIE, thanks for your answer, my network manager is currently NetworkManager indeed (but I tried wicd previously with same results), here is the console output of wpa_supplicant after stopping NetworkManager: (I don't know where can I look for another log of wpa_supplicant connection)

Successfully initialized wpa_supplicant

wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="OurCovine" auth_failures=1 duration=10 reason=CONN_FAILED
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="OurCovine"
wlp2s0: SME: Trying to authenticate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: Trying to associate with 00:18:4d:85:53:66 (SSID='OurCovine' freq=2462 MHz)
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="OurCovine" auth_failures=2 duration=23 reason=CONN_FAILED

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,523

Website

Re: Problems connecting to an specific wireless router (Atheros+Asus)

wpa_passphrases generates only the most basic wpa_supplicant stanza.  Depending on the network settings you will often need additional parameters.  If you start wpa_supplicant with an empty config then run `wpa_cli scan` then wait a few seconds for the scan, then `wpa_cli scan_results | grep OurCovine` and post the result here.  I'm particularly interested in the flags column which may be something like "[WPA2-PSK-CCMP][ESS]" (if the flags are identical to that, then the basic wpa_passphrase stanza should be fine, but if there are other acronyms there you may need more.)

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

cristianpark

Member

Registered: 2011-10-20

Posts: 7

Re: Problems connecting to an specific wireless router (Atheros+Asus)

Trilby, I have this output with wpa_cli scan for SSID OurCovine

00:18:4d:85:53:66	2462	-56	[WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP-preauth][ESS]	OurCovine

I tried with other encryption on the router (even without passphrase at all) and got the same results, can't connect with the same output

Last edited by cristianpark (2017-06-29 12:33:50)

cristianpark

Member

Registered: 2011-10-20

Posts: 7

Re: Problems connecting to an specific wireless router (Atheros+Asus)

I could connect to the network in my ubuntu 13.10 but I recently upgraded to ubuntu 17.04 and I have the same problem that I have with Arch. Old ubuntu versions used ifconfig and the current one uses ip (like arch),  maybe it has something to do with it?