[SOLVED] [wifi] NetworkManager lists APs but fails WPA authentication
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
[wifi] NetworkManager lists APs but fails WPA authentication
Hello
I'm running Linux Mint 18 on a laptop that has a Qualcomm Atheros AR9285 wifi chip.
It looks like it uses the Gnome NetworkManager and it also has wpasupplicant installed, so I assume NM relies on wpasupplicant for WPA authentication.
Problem is, NM does display the list of hotspots, but it fails when trying to connect to my home wifi router that uses WPA. The password is correct.
How could I investigate where the problem lies? Can I run a whole session with just wpasupplicant, and if it works, investigate why it doesn't work with NM?
Note: It works fine with XPSP3, so the hardware is OK.
Thank you.
Last edited by littlebigman; 04-13-2017 at 07:49 AM.
And you should be connected. Stopping the existing manager is the hard part. Your init system or DE could be restarting it while you fiddle. Check dmesg for firmware woes after you issue the up. When network manager or other managers (wicd) fail, it's probably because your driver doesn't work or is "quirky". If it doesn't work it's probably missing firmware.
It could be a bug in the ath9k driver because 1) this hardware works fine in XPSP3, and 2) it also failed connecting with public hotspots. I wonder if the driver was provided by Qualcomm or written by a Linux developer. It's odd because this hardware is several years old, though.
Anyway, /var/log/syslog shows nothing when I run "ifconfig wlp2s0 up".
And here's what happens when trying to connect:
Code:
mint ~ # wpa_passphrase my_home_AP mypasswd > wpa.conf
mint ~ # wpa_supplicant -Dnl80211,wext -iwlp2s0 -cwpa.conf
Successfully initialized wpa_supplicant
wlp2s0: SME: Trying to authenticate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Trying to associate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Associated with 92:84:62:b4:1c:54
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=92:84:62:b4:1c:54 reason=16
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp2s0: SME: Trying to authenticate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Trying to associate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Associated with 92:84:62:b4:1c:54
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=92:84:62:b4:1c:54 reason=15
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp2s0: SME: Trying to authenticate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Trying to associate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Associated with 92:84:62:b4:1c:54
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=92:84:62:b4:1c:54 reason=15
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp2s0: SME: Trying to authenticate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Trying to associate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Associated with 92:84:62:b4:1c:54
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=92:84:62:b4:1c:54 reason=15
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="my_home_AP" auth_failures=1 duration=10 reaso n=CONN_FAILED
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="my_home_AP"
wlp2s0: SME: Trying to authenticate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Trying to associate with 92:84:62:b4:1c:54 (SSID='my_home_AP' freq=2462 MHz)
wlp2s0: Associated with 92:84:62:b4:1c:54
wlp2s0: WPA: Key negotiation completed with 92:84:62:b4:1c:54 [PTK=CCMP GTK=TKIP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 92:84:62:b4:1c:54 completed [id=0 id_str=]
^Cwlp2s0: CTRL-EVENT-DISCONNECTED bssid=92:84:62:b4:1c:54 reason=3 locally_generated=1
nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
wlp2s0: CTRL-EVENT-TERMINATING
(I hit CTRL+C before the last line)
mint ~ # dhclient -4 -v wlp2s0
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/wlp2s0/74:2f:68:33:ab:04
Sending on LPF/wlp2s0/74:2f:68:33:ab:04
Sending on Socket/fallback
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x99d1900e)
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 8 (xid=0x99d1900e)
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 21 (xid=0x99d1900e)
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 10 (xid=0x99d1900e)
^C
mint ~ #
The up down of the wpa output suggests the driver is failing. Missing firmware?
$ dmesg | grep -i firmware
$ dmesg | grep -i ath
No need to guess which driver you are using. It's logged in several locations which driver is in use. Most times a quirky driver is missing firmware. I used a debian live usb install a few years ago and the atheros wifi chipsets that I observed worked great.
$ sudo apt-get install firmware-atheros
If it's relatively new hardware you might need some bleeding edge firmware. Or some non-mainstream legacy firmware for older hardware. But it probably works, baring hardware issues, if there's a driver for it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
[wifi] NetworkManager lists APs but fails WPA authentication
