On 20/01/2017 08:42, Rick Stevens wrote:
On 01/19/2017 12:40 PM, Stephen Morris wrote:
On 19/1/17 6:15 pm, Joe Zeff wrote:
On 01/18/2017 11:53 PM, Stephen Morris wrote:
I've checked the KEY_MGMT value and it matches the entry in the
associated keys file.
I've also added the two WPA_ALLOW keys but they have made no difference
to NM acknowledging that the device can be connected to.
Do you have any way of testing the device on a different LAN? I've
been noticing more and more people assuming that any issues must be
software and that the hardware can't fail.
The device works fine under Windows 10 but does have difficulty
remaining connected under Ubuntu 16.10.
You know, it's not that NM won't talk to it (it's obviously trying from
the log entries you've shared), but it's failing the authentication
to the ESSID. You're also saying that it has difficulty under Ubuntu
16.10 (which also uses NM if I remember correctly). I'm starting to
wonder if the access point and the cipher keys on Linux don't match up.
Here's an excerpt of the logs from my laptop. The lines with ESSID
"sssscnet" are from my home network from when I took it home last
night. The lines dealing with ESSID "AD" are from my office when I
brought it back in here this morning (the machine remained on but in
sleep mode on the way into the office):
Jan 18 20:49:23 golem4.hci.com wpa_supplicant[1070]: nl80211: deinit
ifname=wlan0 disabled_11b_rates=0
Jan 18 21:44:14 golem4.hci.com wpa_supplicant[1070]: wlan0: SME: Trying
to authenticate with f4:f2:6d:fc:94:f3 (SSID='sssscnet' freq=2412 MHz)
Jan 18 21:44:14 golem4.hci.com wpa_supplicant[1070]: wlan0: Trying to
associate with f4:f2:6d:fc:94:f3 (SSID='sssscnet' freq=2412 MHz)
Jan 18 21:44:14 golem4.hci.com wpa_supplicant[1070]: wlan0: Associated
with f4:f2:6d:fc:94:f3
Jan 18 21:44:14 golem4.hci.com wpa_supplicant[1070]: wlan0: WPA: Key
negotiation completed with f4:f2:6d:fc:94:f3 [PTK=CCMP GTK=TKIP]
Jan 18 21:44:14 golem4.hci.com wpa_supplicant[1070]: wlan0:
CTRL-EVENT-CONNECTED - Connection to f4:f2:6d:fc:94:f3 completed [id=0
id_str=]
(closed lid on laptop last night at this point)
Jan 18 21:56:53 golem4.hci.com wpa_supplicant[1070]: wlan0:
CTRL-EVENT-DISCONNECTED bssid=f4:f2:6d:fc:94:f3 reason=3 locally_generated=1
Jan 18 21:56:53 golem4.hci.com wpa_supplicant[1070]: wlan0:
CTRL-EVENT-SCAN-FAILED ret=-100
Jan 18 21:56:53 golem4.hci.com wpa_supplicant[1070]: nl80211: deinit
ifname=wlan0 disabled_11b_rates=0
(opened lid on laptop at the office at this point)
Jan 19 10:53:37 golem4.hci.com wpa_supplicant[1070]: wlan0: SME: Trying
to authenticate with 38:2c:4a:a1:0b:d8 (SSID='AD' freq=2437 MHz)
Jan 19 10:53:37 golem4.hci.com wpa_supplicant[1070]: wlan0: Trying to
associate with 38:2c:4a:a1:0b:d8 (SSID='AD' freq=2437 MHz)
Jan 19 10:53:37 golem4.hci.com wpa_supplicant[1070]: wlan0: Associated
with 38:2c:4a:a1:0b:d8
Jan 19 10:53:37 golem4.hci.com wpa_supplicant[1070]: wlan0: WPA: Key
negotiation completed with 38:2c:4a:a1:0b:d8 [PTK=CCMP GTK=CCMP]
Jan 19 10:53:37 golem4.hci.com wpa_supplicant[1070]: wlan0:
CTRL-EVENT-CONNECTED - Connection to 38:2c:4a:a1:0b:d8 completed [id=0
id_str=]
(closed lid to make a phone call at this point)
Jan 19 11:01:28 golem4.hci.com wpa_supplicant[1070]: wlan0:
CTRL-EVENT-DISCONNECTED bssid=38:2c:4a:a1:0b:d8 reason=3 locally_generated=1
Jan 19 11:01:29 golem4.hci.com wpa_supplicant[1070]: wlan0:
CTRL-EVENT-SCAN-FAILED ret=-100
Jan 19 11:01:29 golem4.hci.com wpa_supplicant[1070]: nl80211: deinit
ifname=wlan0 disabled_11b_rates=0
(reopened lid at this point)
Jan 19 13:33:05 golem4.hci.com wpa_supplicant[1070]: wlan0: SME: Trying
to authenticate with 38:2c:4a:a1:0b:d8 (SSID='AD' freq=2437 MHz)
Jan 19 13:33:05 golem4.hci.com wpa_supplicant[1070]: wlan0: Trying to
associate with 38:2c:4a:a1:0b:d8 (SSID='AD' freq=2437 MHz)
Jan 19 13:33:05 golem4.hci.com wpa_supplicant[1070]: wlan0: Associated
with 38:2c:4a:a1:0b:d8
Jan 19 13:33:05 golem4.hci.com wpa_supplicant[1070]: wlan0: WPA: Key
negotiation completed with 38:2c:4a:a1:0b:d8 [PTK=CCMP GTK=CCMP]
Jan 19 13:33:05 golem4.hci.com wpa_supplicant[1070]: wlan0:
CTRL-EVENT-CONNECTED - Connection to 38:2c:4a:a1:0b:d8 completed [id=0
id_str=]
(logs extracted via "journalctl -b 0 -u wpa_supplicant")
What's interesting to me is that the WPA negotiations use different
ciphers ("sssscnet" uses PTK=CCMP GTK=TKIP, while "AD" uses PTK=CCMP
GTK=CCMP). I'm wondering if there's something odd going on there between
your machine and the access point.
You may need to disable NM and stop wpa_supplicant, then run
wpa_supplicant without the "-u" option in the foreground in an
xterm:
# systemctl stop NetworkManager
# systemctl stop wpa_supplicant
# /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf
-i <name-of-your-wifi-device> -d
Then use wpa_gui or wpa_cli (wpa_gui is probably easier) to control
wpa_supplicant (you need to run wpa_supplicant this way because neither
wpa_gui or wpa_cli are dbus-compatible so wpa_supplicant can NOT have
the "-u" option). You can see what's going on with wpa_supplicant by
watching the xterm you ran it in. Once you've got that sorted, stop
wpa_supplicant and restore your system to normal:
# systemctl start wpa_supplicant
# systemctl start NetworkManager
and play with the NM editor to set up what you discovered. Yes it's
convoluted and it may not work, but it's worth a go anyway.
Thanks for the info Rick. It didn't work for me. I don't have wpa_gui
and wpa_cli can't communicate with wpa_supplicant.
Wpa_supplicant also says it can't find wlp4s6 either.
regards,
Steve
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- "Do you suffer from long-term memory loss?" "I don't remember" -
- -- Chumbawumba, "Amnesia" (TubThumping) -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
