[SOLVED] I can't connect to my wireless network through NetworkManager

surrealistic · 2018-03-17 11:14:13

Hey there!

I'm having some troubles with NetworkManager lately. Since last month I can't connect to my wireless network through NetworkManager because it's keep asking for the password for a while even when it's the correct one.

My first thoughts were that it could be because I've moved my old ADSL network to a new optical fiber one, but I can connect to my network on my Raspberry Pi with Arch Linux ARM so I've discarded that issue...

After a while trying some fixes I've read on Internet and some tests I've done by myself, even with wifi-menu it couldn't connect... I decided to try a different manager and I've installed wicd and it has worked with it, I can connect to my wireless network using wicd.

So I'm here to ask for help in case that someone had or knows about this issue with NetworkManager to try to fix it.

systemctl status NetworkManager.service output:

Mar 17 11:46:18 Arch-Laptop NetworkManager[770]: <info>  [1521283578.0122] dhcp4 (wlp2s0): state changed timeout -> done
Mar 17 11:46:18 Arch-Laptop NetworkManager[770]: <info>  [1521283578.0127] device (wlp2s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Mar 17 11:46:18 Arch-Laptop NetworkManager[770]: <warn>  [1521283578.0137] device (wlp2s0): Activation: failed for connection 'Network SSID'
Mar 17 11:46:18 Arch-Laptop NetworkManager[770]: <info>  [1521283578.1657] device (wlp2s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Mar 17 11:46:18 Arch-Laptop NetworkManager[770]: <info>  [1521283578.1745] device (wlp2s0): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning)
Mar 17 11:46:18 Arch-Laptop NetworkManager[770]: <warn>  [1521283578.1791] sup-iface[0x55c57c972170,wlp2s0]: connection disconnected (reason -3)
Mar 17 11:46:18 Arch-Laptop NetworkManager[770]: <info>  [1521283578.1792] device (wlp2s0): supplicant interface state: completed -> disconnected
Mar 17 11:46:18 Arch-Laptop NetworkManager[770]: <warn>  [1521283578.1792] sup-iface[0x55c57c972170,wlp2s0]: connection disconnected (reason -3)
Mar 17 11:52:02 Arch-Laptop NetworkManager[770]: <info>  [1521283922.0643] device (wlp2s0): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning)
Mar 17 11:57:17 Arch-Laptop NetworkManager[770]: <info>  [1521284237.0639] device (wlp2s0): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning)

lspci -k | grep Wireless output:

02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7265

I'm experiencing the same issue with another laptop, I can't connect to my wireless network but using wicd.

I hope someone has any idea why this is happening

Thank you!!

Last edited by surrealistic (2018-03-27 14:54:19)

positronik · 2018-03-17 12:20:39

I guess one possible way of debugging the issue is to try to connect manually following https://wiki.archlinux.org/index.php/Wi … nual_setup and see when it fails.

surrealistic · 2018-03-17 16:35:49

Hi positronik

I just tried to connect manually to my wireless network but it couldn't connect.

I've generated the file /etc/wpa_supplicant/wpa_supplicant.conf:

network={
	ssid="Network SSID"
	#psk="NetworkPassword"
	psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
}

Then I've tried the following command:

# wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf

Successfully initialized wpa_supplicant
nl80211: Could not set interface 'p2p-dev-wlp2s0' UP
nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
p2p-dev-wlp2s0: Failed to initialize driver interface
P2P: Failed to enable P2P Device interface

Once it failed with the last command, I've tried adding the generic driver wext to the command:

#wpa_supplicant -B -D wext -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf

Successfully initialized wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument

iw wlp2s0 link returns me "Not connected".

Is it something wrong on those steps I've done?

Thank you!

Last edited by surrealistic (2018-03-17 16:36:11)

seth · 2018-03-18 08:21:52

nl80211: Could not set interface 'p2p-dev-wlp2s0' UP

Ensure to first stop network manager (and any other network managing service), then follow the wiki step by step and pay attention to the state checks

surrealistic · 2018-03-18 09:49:30

Thank you seth! I already had NetworkManager stopped but I forgot to stop/kill wpa_supplicant I've tried after kill wpa_supplicant and it's connected now using wpa_supplicant, so I'm not sure whether my issue is a NetworkManager's bug or not...

I can connect to my wireless network normally but when I'm trying it through NetworkManager, which keep asking for the password, and wifi-menu, which fails as well.

Does anyone know if it is a known bug or why this may happen?

Thank you!!

Last edited by surrealistic (2018-03-18 10:00:54)

seth · 2018-03-18 10:13:20

Why is there an independent wpa_supplicant service anyway?

systemctl list-unit-files --state=enabled

surrealistic · 2018-03-18 16:36:04

I don't know about that, should not that process be running?

Here is the output of systemctl list-unit-files --state=enabled:

UNIT FILE                                   STATE  
autovt@.service                             enabled
bumblebeed.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
remote-fs.target                            enabled

NOTE: That's the output after a reboot and running NetworkManager again since I have it enabled at startup.

seth · 2018-03-18 19:43:37

wpa_supplicant is implicitly started by networkmanager, but should go down with it (unless you'd run it in a dedicated service, what does not seem to be the case, the output looks sane) - did you stop NM or just kill the process(es)?

surrealistic · 2018-03-19 21:56:40

I've stopped NM with systemctl stop NetworkManager.service

seth · 2018-03-20 06:47:03

There must have been a rogue wpa_supplicant process then.
At least we know the issue is NM related? (Did wifi-menu work afte fully tearing down NM and other services?)

Try https://wiki.archlinux.org/index.php/Ne … domization

surrealistic · 2018-03-22 18:26:20

seth wrote:

There must have been a rogue wpa_supplicant process then.
At least we know the issue is NM related? (Did wifi-menu work afte fully tearing down NM and other services?)
Try https://wiki.archlinux.org/index.php/Ne … domization

Hi! I've tried configuring MAC address randomization following those steps but it's still failing.

wifi-menu doesn't connect as well, but I've realised that once I stop NetworkManager service wifi-menu spends more time trying to connect to my network. If I try to connect through wifi-menu while NetworkManager service is running it fails instantly.

Last edited by surrealistic (2018-03-22 20:40:29)

seth · 2018-03-22 22:09:53

Concurrent management (NM + wifi-menu) is expectable to fail.
So basically you can only (but can!) connect manually?
What does the journal say for exclusive wifi-menu attempts?

LordChaos73 · 2018-03-23 12:40:40

Same issue here, apparently NetworkManager won't connect anymore:

mrt 23 13:28:55 x1carbon NetworkManager[516]: <info>  [1521808135.2422] device (wlp3s0): supplicant interface state: scanning -> authenticating
mrt 23 13:28:55 x1carbon NetworkManager[516]: <info>  [1521808135.2535] device (wlp3s0): supplicant interface state: authenticating -> associated
mrt 23 13:28:55 x1carbon NetworkManager[516]: <info>  [1521808135.2701] device (wlp3s0): supplicant interface state: associated -> completed
mrt 23 13:28:55 x1carbon NetworkManager[516]: <info>  [1521808135.2701] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'XXXXXX'.
mrt 23 13:28:55 x1carbon NetworkManager[516]: <info>  [1521808135.2702] device (wlp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
mrt 23 13:28:55 x1carbon NetworkManager[516]: <info>  [1521808135.2706] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
mrt 23 13:29:41 x1carbon NetworkManager[516]: <warn>  [1521808181.0049] dhcp4 (wlp3s0): request timed out
mrt 23 13:29:41 x1carbon NetworkManager[516]: <info>  [1521808181.0049] dhcp4 (wlp3s0): state changed unknown -> timeout
mrt 23 13:29:41 x1carbon NetworkManager[516]: <info>  [1521808181.0191] dhcp4 (wlp3s0): canceled DHCP transaction
mrt 23 13:29:41 x1carbon NetworkManager[516]: <info>  [1521808181.0192] dhcp4 (wlp3s0): state changed timeout -> done
mrt 23 13:29:41 x1carbon NetworkManager[516]: <info>  [1521808181.0197] device (wlp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
mrt 23 13:29:41 x1carbon NetworkManager[516]: <info>  [1521808181.0202] manager: NetworkManager state is now DISCONNECTED
mrt 23 13:29:41 x1carbon NetworkManager[516]: <warn>  [1521808181.0216] device (wlp3s0): Activation: failed for connection 'XXXXXX'
mrt 23 13:29:41 x1carbon NetworkManager[516]: <info>  [1521808181.0292] device (wlp3s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
mrt 23 13:29:41 x1carbon NetworkManager[516]: <info>  [1521808181.0387] device (wlp3s0): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning)
mrt 23 13:29:41 x1carbon NetworkManager[516]: <warn>  [1521808181.0498] sup-iface[0x55bb3654e170,wlp3s0]: connection disconnected (reason -3)
mrt 23 13:29:41 x1carbon NetworkManager[516]: <info>  [1521808181.0499] device (wlp3s0): supplicant interface state: completed -> disconnected
mrt 23 13:29:41 x1carbon NetworkManager[516]: <warn>  [1521808181.0500] sup-iface[0x55bb3654e170,wlp3s0]: connection disconnected (reason -3)

x1carbon :: ~ » systemctl list-unit-files --state=enabled
UNIT FILE                                   STATE  
org.cups.cupsd.path                         enabled
autovt@.service                             enabled
avahi-daemon.service                        enabled
bluetooth.service                           enabled
dbus-org.bluez.service                      enabled
dbus-org.freedesktop.Avahi.service          enabled
dbus-org.freedesktop.network1.service       enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
dbus-org.freedesktop.resolve1.service       enabled
dbus-org.freedesktop.thermald.service       enabled
display-manager.service                     enabled
gdm.service                                 enabled
getty@.service                              enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
org.cups.cupsd.service                      enabled
sshd.service                                enabled
systemd-networkd-wait-online.service        enabled
systemd-networkd.service                    enabled
systemd-resolved.service                    enabled
systemd-timesyncd.service                   enabled
thermald.service                            enabled
tlp.service                                 enabled
org.cups.cupsd.socket                       enabled
systemd-networkd.socket                     enabled
ctrl-alt-del.target                         enabled
machines.target                             enabled
reboot.target                               enabled
remote-fs.target                            enabled
runlevel6.target                            enabled

x1carbon :: ~ » lspci -k |grep -i wireless
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7260

Netctl works fine though, could this be related to the latest NetworkManager update?

[2018-03-19 18:30] [ALPM] upgraded networkmanager (1.10.6-1 -> 1.10.6-2)

Last edited by LordChaos73 (2018-03-23 12:41:15)

seth · 2018-03-23 12:43:30

Looks and sounds more like https://wiki.archlinux.org/index.php/Ne … HCP_client

LordChaos73 · 2018-03-23 12:52:33

seth wrote:

Looks and sounds more like https://wiki.archlinux.org/index.php/Ne … HCP_client

Thanks, installing dhclient solved my issue!

surrealistic · 2018-03-23 18:55:03

seth wrote:

Looks and sounds more like https://wiki.archlinux.org/index.php/Ne … HCP_client

Hi! I tried with that but doesn't work.

seth · 2018-03-23 19:15:53

Yes, this only fits LordChaos73 pattern, sorry :-(

https://bbs.archlinux.org/viewtopic.php … 7#p1775577 ?

surrealistic · 2018-03-25 16:10:15

Hi! It seems that it was fixed with the latest updates... I just turned on the laptop for the first time since the last time I ran pacman -Syyu (some hours ago) and I've been able to connect now to my wireless network using NetworkManager.. It seems that some of the latest gnome's updates have fixed that problem.

I'm going to check it during today to ensure that it works correctly.

Last edited by surrealistic (2018-03-25 21:40:34)

surrealistic · 2018-03-27 14:55:34

I can confirm that it has been solved with the latest updates.

Thank you!

Arch Linux

#1 2018-03-17 11:14:13

[SOLVED] I can't connect to my wireless network through NetworkManager

#2 2018-03-17 12:20:39

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#3 2018-03-17 16:35:49

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#4 2018-03-18 08:21:52

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#5 2018-03-18 09:49:30

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#6 2018-03-18 10:13:20

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#7 2018-03-18 16:36:04

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#8 2018-03-18 19:43:37

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#9 2018-03-19 21:56:40

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#10 2018-03-20 06:47:03

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#11 2018-03-22 18:26:20

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#12 2018-03-22 22:09:53

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#13 2018-03-23 12:40:40

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#14 2018-03-23 12:43:30

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#15 2018-03-23 12:52:33

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#16 2018-03-23 18:55:03

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#17 2018-03-23 19:15:53

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#18 2018-03-25 16:10:15

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

#19 2018-03-27 14:55:34

Re: [SOLVED] I can't connect to my wireless network through NetworkManager

Board footer