You are not logged in.

Pages: 1

#1 2016-07-17 19:30:48

DrZhivago
Member
Registered: 2016-07-17
Posts: 8

[Solved] NetworkManager cannot connect to WPA networks

I have been struggling with this issue for days after upgrading networkmanager. I cannot connect to any wpa networks.

Below is the output I get when running "journalctl -u NetworkManager".

Jul 17 14:49:09 Leliel NetworkManager[2007]: <info>  [1468781349.9633] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jul 17 14:49:11 Leliel NetworkManager[2007]: <info>  [1468781351.2287] device (wlp3s0): supplicant interface state: ready -> inactive
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5646] device (wlp3s0): Activation: starting connection 'NTTU' (28aa0255-46c1-4fbb-ac3a-21fa2fda6f2b)
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5649] audit: op="connection-activate" uuid="28aa0255-46c1-4fbb-ac3a-21fa2fda6f2b" name="NTTU" pid=605 uid=1000 
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5651] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5661] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5682] device (wlp3s0): Activation: (wifi) access point 'NTTU' has security, but secrets are required.
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5682] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5760] device (wlp3s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5772] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5779] device (wlp3s0): Activation: (wifi) connection 'NTTU' has security, and secrets exist.  No new secrets ne
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5783] Config: added 'ssid' value 'NTTU'
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5786] Config: added 'scan_ssid' value '1'
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5789] Config: added 'key_mgmt' value 'WPA-PSK'
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5792] Config: added 'auth_alg' value 'OPEN'
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.5795] Config: added 'psk' value '<omitted>'
Jul 17 14:56:15 Leliel NetworkManager[2007]: <info>  [1468781775.6346] sup-iface[0x282bc30,wlp3s0]: config: set interface ap_scan to 1
Jul 17 14:56:16 Leliel NetworkManager[2007]: <info>  [1468781776.0083] device (wlp3s0): supplicant interface state: inactive -> scanning
Jul 17 14:56:16 Leliel NetworkManager[2007]: <info>  [1468781776.9476] device (wlp3s0): supplicant interface state: scanning -> authenticating
Jul 17 14:56:17 Leliel NetworkManager[2007]: <info>  [1468781777.2769] device (wlp3s0): supplicant interface state: authenticating -> disconnected
Jul 17 14:56:17 Leliel NetworkManager[2007]: <info>  [1468781777.3769] device (wlp3s0): supplicant interface state: disconnected -> scanning
Jul 17 14:56:18 Leliel NetworkManager[2007]: <info>  [1468781778.3203] device (wlp3s0): supplicant interface state: scanning -> authenticating
Jul 17 14:56:18 Leliel NetworkManager[2007]: <info>  [1468781778.6435] device (wlp3s0): supplicant interface state: authenticating -> disconnected
Jul 17 14:56:19 Leliel NetworkManager[2007]: <info>  [1468781779.1443] device (wlp3s0): supplicant interface state: disconnected -> scanning
Jul 17 14:56:20 Leliel NetworkManager[2007]: <info>  [1468781780.0757] device (wlp3s0): supplicant interface state: scanning -> authenticating
Jul 17 14:56:20 Leliel NetworkManager[2007]: <info>  [1468781780.4066] device (wlp3s0): supplicant interface state: authenticating -> disconnected
Jul 17 14:56:21 Leliel NetworkManager[2007]: <info>  [1468781781.4080] device (wlp3s0): supplicant interface state: disconnected -> scanning
Jul 17 14:56:22 Leliel NetworkManager[2007]: <info>  [1468781782.3456] device (wlp3s0): supplicant interface state: scanning -> authenticating
Jul 17 14:56:22 Leliel NetworkManager[2007]: <info>  [1468781782.6701] device (wlp3s0): supplicant interface state: authenticating -> disconnected
Jul 17 14:56:27 Leliel NetworkManager[2007]: <info>  [1468781787.6727] device (wlp3s0): supplicant interface state: disconnected -> scanning
Jul 17 14:56:32 Leliel NetworkManager[2007]: <info>  [1468781792.5901] device (wlp3s0): supplicant interface state: scanning -> authenticating
Jul 17 14:56:32 Leliel NetworkManager[2007]: <info>  [1468781792.9265] device (wlp3s0): supplicant interface state: authenticating -> disconnected
Jul 17 14:56:40 Leliel NetworkManager[2007]: <warn>  [1468781800.3482] device (wlp3s0): Activation: (wifi) association took too long, failing activation
Jul 17 14:56:40 Leliel NetworkManager[2007]: <info>  [1468781800.3483] device (wlp3s0): state change: config -> failed (reason 'ssid-not-found') [50 120 53]
Jul 17 14:56:40 Leliel NetworkManager[2007]: <warn>  [1468781800.3493] device (wlp3s0): Activation: failed for connection 'NTTU'
Jul 17 14:56:40 Leliel NetworkManager[2007]: <info>  [1468781800.3508] device (wlp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Jul 17 14:56:41 Leliel NetworkManager[2007]: <info>  [1468781801.2966] device (wlp3s0): supplicant interface state: disconnected -> inactive

In this case I am trying to connect to a network named NTTU.

I have checked and wpa_supplicant is running, and netctl is not.

Does any body have any tips on how to solve this?

Thanks.

Edit: I am using a T430.

Last edited by DrZhivago (2016-07-17 21:16:01)

Offline

#2 2016-07-17 20:43:56

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: [Solved] NetworkManager cannot connect to WPA networks

Can you connect manually?
https://wiki.archlinux.org/index.php/Wi … nual_setup

Any error messages returned during that process may pinpoint the failing.

I have checked and wpa_supplicant is running, and netctl is not.

Please post the commands that you used and the full output.

I would use:

# systemctl list-unit-files --state=enabled

Are you infected with Wetiko?

Offline

#3 2016-07-17 21:01:28

DrZhivago
Member
Registered: 2016-07-17
Posts: 8

Re: [Solved] NetworkManager cannot connect to WPA networks

Thanks for the reply.  Running "sudo wpa_supplicant -i wlp3s0 -c <(wpa_passphrase "NTTU" "Syzranru#1") " yields this as a result: (I am not sure if this just an improper way of connecting or not)

➜  ~ sudo wpa_supplicant -i wlp3s0 -c <(wpa_passphrase "NTTU" "Syzranru#1") 
Successfully initialized wpa_supplicant
Failed to open config file '/proc/self/fd/11', error: No such file or directory
Failed to read or parse configuration '/proc/self/fd/11'.

Running "systemctl list-unit-files --state=enabled" produces this output:

➜  ~ systemctl list-unit-files --state=enabled
UNIT FILE                                    STATE  
autovt@.service                              enabled
dbus-fi.epitest.hostap.WPASupplicant.service enabled
dbus-org.freedesktop.NetworkManager.service  enabled
dbus-org.freedesktop.nm-dispatcher.service   enabled
display-manager.service                      enabled
gdm.service                                  enabled
getty@.service                               enabled
NetworkManager-dispatcher.service            enabled
NetworkManager.service                       enabled
systemd-timesyncd.service                    enabled
wpa_supplicant.service                       enabled
remote-fs.target                             enabled

12 unit files listed.

Offline

#4 2016-07-17 21:14:25

DrZhivago
Member
Registered: 2016-07-17
Posts: 8

Re: [Solved] NetworkManager cannot connect to WPA networks

You know what, I feel like so stupid. I noticed that a chromebook on my network was having the same issue. I just restarted my router, and everything works fine. Weird that this was only an issue for my laptop this chromebook, and not any of the windows machines on the network.

Thanks for your help.

Offline

Pages: 1

Board footer

Powered by FluxBB