[Solved]Can't connect to Wi-Fi network after disconnecting from one.

exnihilodub · 2017-04-18 08:32:12

Hi. My problem is that I can connect to any wifi network, but after disconnecting from one, I can't connect again(doesn't matter if it's the same network or a different one.) I'm able to connect to a network after rebooting. I use NetworkManager.

The steps I follow to reproduce this problem is:

*starting X server
*starting nm-applet to see the current status of the connection in the top bar
*running networkmanager_dmenu
*selecting a Wi-Fi to connect, verifying the connection has established by looking at nm-applet icon
*running networkmanager_dmenu again and selecting "Disable Networking"
*running networkmanager_dmenu again and selecting "Enable Networking"
*trying to connect to the same or any other Wi-Fi, and failing

here's my systemctl --type=service output:

UNIT                                                LOAD   ACTIVE SUB     DESCRIPTION                                                
alsa-restore.service                                loaded active exited  Save/Restore Sound Card State                              
cronie.service                                      loaded active running Periodic Command Scheduler                                 
dbus.service                                        loaded active running D-Bus System Message Bus                                   
getty@tty1.service                                  loaded active running Getty on tty1                                              
kmod-static-nodes.service                           loaded active exited  Create list of required static device nodes for the current
lm_sensors.service                                  loaded active exited  Initialize hardware monitoring sensors                     
NetworkManager.service                              loaded active running Network Manager                                            
polkit.service                                      loaded active running Authorization Manager                                      
postgresql.service                                  loaded active running PostgreSQL database server                                 
systemd-backlight@backlight:intel_backlight.service loaded active exited  Load/Save Screen Backlight Brightness of backlight:intel_ba
systemd-backlight@leds:smc::kbd_backlight.service   loaded active exited  Load/Save Screen Backlight Brightness of leds:smc::kbd_back
systemd-fsck-root.service                           loaded active exited  File System Check on Root Device                           
systemd-journal-flush.service                       loaded active exited  Flush Journal to Persistent Storage                        
systemd-journald.service                            loaded active running Journal Service                                            
systemd-logind.service                              loaded active running Login Service                                              
systemd-random-seed.service                         loaded active exited  Load/Save Random Seed                                      
systemd-remount-fs.service                          loaded active exited  Remount Root and Kernel File Systems                       
systemd-resolved.service                            loaded active running Network Name Resolution                                    
systemd-sysctl.service                              loaded active exited  Apply Kernel Variables                                     
systemd-timesyncd.service                           loaded active running Network Time Synchronization                               
systemd-tmpfiles-setup-dev.service                  loaded active exited  Create Static Device Nodes in /dev                         
systemd-tmpfiles-setup.service                      loaded active exited  Create Volatile Files and Directories                      
systemd-udev-trigger.service                        loaded active exited  udev Coldplug all Devices                                  
systemd-udevd.service                               loaded active running udev Kernel Device Manager                                 
systemd-update-utmp.service                         loaded active exited  Update UTMP about System Boot/Shutdown                     
systemd-user-sessions.service                       loaded active exited  Permit User Sessions                                       
tlp.service                                         loaded active exited  TLP system startup/shutdown                                
user@1000.service                                   loaded active running User Manager for UID 1000                                  
wpa_supplicant.service                              loaded active running WPA supplicant                                             

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

29 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
lines 1-37/37 (END)

and here's my journalctl -xe output:

lines 1678-1719/1719 (END)
Apr 18 11:17:54 UserName NetworkManager[1163]: <info>  [1492503474.0461] manager: re-enabling...
Apr 18 11:17:54 UserName NetworkManager[1163]: <info>  [1492503474.0462] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 18 11:17:54 UserName NetworkManager[1163]: <info>  [1492503474.0476] device (wlp4s0): set-hw-addr: set MAC address to 16:DA:EF:BA:47:EC (scanning)
Apr 18 11:17:54 UserName NetworkManager[1163]: <info>  [1492503474.0491] audit: op="networking-control" arg="on" pid=1180 uid=1000 result="success"
Apr 18 11:17:54 UserName NetworkManager[1163]: <info>  [1492503474.0981] sup-iface[0x25be020,wlp4s0]: supports 1 scan SSIDs
Apr 18 11:17:54 UserName NetworkManager[1163]: <info>  [1492503474.0992] device (wlp4s0): supplicant interface state: starting -> ready
Apr 18 11:17:54 UserName NetworkManager[1163]: <info>  [1492503474.0993] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Apr 18 11:17:59 UserName systemd-timesyncd[363]: Timed out waiting for reply from 131.211.8.244:123 (0.arch.pool.ntp.org).
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2602] device (wlp4s0): Activation: starting connection 'NetworkName' (fc80c98a-3dab-44aa-8d48-9ffe4e33f6e9)
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2605] audit: op="connection-activate" uuid="fc80c98a-3dab-44aa-8d48-9ffe4e33f6e9" name="NetworkName" pid=1198 uid=1000 resu
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2609] device (wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2612] manager: NetworkManager state is now CONNECTING
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2623] device (wlp4s0): set-hw-addr: reset MAC address to 82:45:BA:D6:2E:DC (preserve)
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2759] device (wlp4s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2764] device (wlp4s0): Activation: (wifi) connection 'NetworkName' requires no security.  No secrets needed.
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2765] Config: added 'ssid' value 'NetworkName'
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2766] Config: added 'scan_ssid' value '1'
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.2766] Config: added 'key_mgmt' value 'NONE'
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.3199] device (wlp4s0): supplicant interface state: ready -> disconnected
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.3201] sup-iface[0x25be020,wlp4s0]: config: set interface ap_scan to 1
Apr 18 11:18:04 UserName NetworkManager[1163]: <info>  [1492503484.3295] device (wlp4s0): supplicant interface state: disconnected -> scanning
Apr 18 11:18:07 UserName wpa_supplicant[681]: wlp4s0: Trying to associate with 18:64:72:1a:40:d0 (SSID='NetworkName' freq=5580 MHz)
Apr 18 11:18:07 UserName NetworkManager[1163]: <info>  [1492503487.4566] device (wlp4s0): supplicant interface state: scanning -> associating
Apr 18 11:18:07 UserName wpa_supplicant[681]: wlp4s0: Associated with 18:64:72:1a:40:d0
Apr 18 11:18:07 UserName wpa_supplicant[681]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to 18:64:72:1a:40:d0 completed [id=0 id_str=]
Apr 18 11:18:07 UserName wpa_supplicant[681]: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 18 11:18:07 UserName NetworkManager[1163]: <info>  [1492503487.6719] device (wlp4s0): supplicant interface state: associating -> completed
Apr 18 11:18:07 UserName NetworkManager[1163]: <info>  [1492503487.6720] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Bilg
Apr 18 11:18:07 UserName NetworkManager[1163]: <info>  [1492503487.6730] device (wlp4s0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 18 11:18:07 UserName NetworkManager[1163]: <info>  [1492503487.6739] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Apr 18 11:18:52 UserName NetworkManager[1163]: <warn>  [1492503532.8890] dhcp4 (wlp4s0): request timed out
Apr 18 11:18:52 UserName NetworkManager[1163]: <info>  [1492503532.8890] dhcp4 (wlp4s0): state changed unknown -> timeout
Apr 18 11:18:52 UserName NetworkManager[1163]: <info>  [1492503532.9090] dhcp4 (wlp4s0): canceled DHCP transaction
Apr 18 11:18:52 UserName NetworkManager[1163]: <info>  [1492503532.9090] dhcp4 (wlp4s0): state changed timeout -> done
Apr 18 11:18:52 UserName NetworkManager[1163]: <info>  [1492503532.9092] device (wlp4s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Apr 18 11:18:52 UserName NetworkManager[1163]: <info>  [1492503532.9093] manager: NetworkManager state is now DISCONNECTED
Apr 18 11:18:52 UserName NetworkManager[1163]: <warn>  [1492503532.9096] device (wlp4s0): Activation: failed for connection 'NetworkName'
Apr 18 11:18:52 UserName NetworkManager[1163]: <info>  [1492503532.9099] device (wlp4s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 18 11:18:52 UserName wpa_supplicant[681]: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=18:64:72:1a:40:d0 reason=3 locally_generated=1
Apr 18 11:18:52 UserName NetworkManager[1163]: <info>  [1492503532.9116] device (wlp4s0): set-hw-addr: set MAC address to 5A:C9:25:CF:4D:AD (scanning)
Apr 18 11:18:52 UserName NetworkManager[1163]: <warn>  [1492503532.9124] sup-iface[0x25be020,wlp4s0]: connection disconnected (reason -3)
Apr 18 11:18:52 UserName NetworkManager[1163]: <info>  [1492503532.9125] device (wlp4s0): supplicant interface state: completed -> disconnected
~

I appreciate the help and thank you for your time looking into this issue. Please let me know if I can help you help me by supplying more info.

Last edited by exnihilodub (2017-04-21 01:07:25)

Trilby · 2017-04-18 10:35:10

Do you only have this problem with networkmanager_dmenu? In other words, if you just use network manager itself to connect, disconnect, and reconnect, does it work?

I suspect the "disable networking" option is simply putting interfaces down but not stopping/killing the relevant daemon processes like wpa_supplicant and dhcpcd.

exnihilodub · 2017-04-18 13:31:03

Trilby wrote:

Do you only have this problem with networkmanager_dmenu? In other words, if you just use network manager itself to connect, disconnect, and reconnect, does it work?
I suspect the "disable networking" option is simply putting interfaces down but not stopping/killing the relevant daemon processes like wpa_supplicant and dhcpcd.

Hi Trilby. I've tried disconnecting and reconnecting with nmcli. Still the same effect.
I've monitored nmcli by using "nmcli m" and here's the output when I disconnect and try to reconnect:

wlp4s0: deactivating
Connectivity is now 'none'
Networkmanager is now in the 'disconnecting' state
wlp4s0: device removed
lo: device removed
NetworkManager has stopped
NetworkName: connection profile removed
AnotherNetwork-DE11-G: connection profile removed
AnotherNetwork-DE11-A: connection profile removed
Hostname set to '(null)'
wlp4s0: device created
lo: device created
Connectivity is now 'none'
Networkmanager is now in the 'disconnected' state
wlp4s0: unavailable
NetworkName: connection profile created
AnotherNetwork-DE11-G: connection profile created
AnotherNetwork-DE11-A: connection profile created
Hostname set to 'UserName'
NetworkManager has started
wlp4s0: disconnected
wlp4s0: connecting (prepare)
wlp4s0: using connection 'NetworkName'
Networkmanager is now in the 'connecting' state
wlp4s0: connecting (configuring)
wlp4s0: connecting (getting IP configuration)
wlp4s0: connection failed

jasonwryan · 2017-04-18 17:52:32

What is the output of `hostnamectl`?

exnihilodub · 2017-04-18 18:05:35

jasonwryan wrote:

What is the output of `hostnamectl`?

If you're curious, I've changed my hostname to UserName in the outputs above.
If the output's going to help me fix the problem, here it is:

   Static hostname: exarch
         Icon name: computer-laptop
           Chassis: laptop
        Machine ID: 7b6f5b78051947a2b79e0681db968fae
           Boot ID: 97d643233c38419fb5536e1ce3853d40
  Operating System: Arch Linux
            Kernel: Linux 4.9.11-1-ARCH
      Architecture: x86-64

Last edited by exnihilodub (2017-04-18 18:05:56)

Trilby · 2017-04-18 18:21:32

I can't be of any help troubleshooting NM specifically as I've never used it. But you could check whether dhcpcd and/or wpa_supplicant are still running after using the dmenu command (check ps output for example).

But you may also want to update your system - that should always be the first step in troubleshooting. I'm not sure if it's relevant here, but it's worth ruling out first. Your kernel is almost 2 months out of date (or do you have ~2month uptime?).

exnihilodub · 2017-04-18 18:56:18

Trilby wrote:

I can't be of any help troubleshooting NM specifically as I've never used it. But you could check whether dhcpcd and/or wpa_supplicant are still running after using the dmenu command (check ps output for example).
But you may also want to update your system - that should always be the first step in troubleshooting. I'm not sure if it's relevant here, but it's worth ruling out first. Your kernel is almost 2 months out of date (or do you have ~2month uptime?).

I ran "top" and saw networkmanager and wpa_supplicant were still running when I disconnected from a network (I don't see any reason why they shouldn't, but wouldn't hurt to give it a try. Right?) I've killed both the processes and services, restarted them, tried reconnecting and failed again.

By the way, sorry for the late info but, I just remembered wifi-menu was having the same issue as well (I had to reboot to select a new connection or it would fail)

About the kernel update, I probably have less than 2 months uptime. I'll give it a go, but I'm really skeptical about if it's going to help solve this issue. So I'd like to delve more into this thing before I try that as a last resort.

exnihilodub · 2017-04-18 19:17:13

I ran journalctl -u NetworkManager -b and here's the output, split into sectors by my actions:

This is when I boot the system and connect to my router:

[exarch@exarch ~]$ journalctl -u NetworkManager -b
-- Logs begin at Thu 2017-02-23 16:40:03 +03, end at Tue 2017-04-18 22:08:36 +03. --
Apr 18 21:48:53 exarch systemd[1]: Starting Network Manager...
Apr 18 21:48:53 exarch NetworkManager[565]: <info>  [1492541333.9964] NetworkManager (version 1.6.2-3, Arch Linux) is starting...
Apr 18 21:48:53 exarch NetworkManager[565]: <info>  [1492541333.9965] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0026] manager[0x98e080]: monitoring kernel firmware directory '/usr/lib/firmware'.
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0055] dns-mgr[0x97b180]: init: dns=default, rc-manager=resolvconf
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0080] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:04:00.0/ieee802
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0082] manager[0x98e080]: WiFi hardware radio set enabled
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0082] manager[0x98e080]: WWAN hardware radio set enabled
Apr 18 21:48:54 exarch systemd[1]: Started Network Manager.
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0272] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc.  To report bugs please use the Netw
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0285] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc.  To report bugs please use the NetworkManager
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0386] keyfile: new connection /etc/NetworkManager/system-connections/BilgiGuest-e761e25f-2126-4e8a-a776-
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0480] keyfile: new connection /etc/NetworkManager/system-connections/Kablonet Netmaster-DE11-A (40b628d1
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.0577] keyfile: new connection /etc/NetworkManager/system-connections/Kablonet Netmaster-DE11-G (7db35434
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2281] settings: hostname: using hostnamed
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2282] settings: hostname changed from (none) to "exarch"
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2292] dhcp-init: default DHCP client 'dhclient' is not available
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2292] dhcp-init: Using DHCP client 'internal'
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2293] manager: WiFi enabled by radio killswitch; enabled by state file
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2293] manager: WWAN enabled by radio killswitch; enabled by state file
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2294] manager: Networking is enabled by state file
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2300] Loaded device plugin: NMBondDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2301] Loaded device plugin: NMBridgeDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2301] Loaded device plugin: NMEthernetDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2301] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2302] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2302] Loaded device plugin: NMMacsecDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2302] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2303] Loaded device plugin: NMTunDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2303] Loaded device plugin: NMVethDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2303] Loaded device plugin: NMVlanDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2304] Loaded device plugin: NMVxlanDeviceFactory (internal)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2323] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/libnm-device-plugin-wifi.so)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2385] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/libnm-device-plugin-wwan.so)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2589] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/libnm-device-plugin-team.so)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2601] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/libnm-device-plugin-adsl.so)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2630] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2650] device (lo): link connected
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2661] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2670] (wlp4s0): using nl80211 for WiFi device control
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2686] manager: (wlp4s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/2)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.2703] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.3090] device (wlp4s0): set-hw-addr: set MAC address to 2A:70:8B:C9:49:61 (scanning)
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.3312] supplicant: wpa_supplicant running
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.3313] device (wlp4s0): supplicant interface state: init -> starting
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.3884] sup-iface[0x9d1e60,wlp4s0]: supports 1 scan SSIDs
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.3892] device (wlp4s0): supplicant interface state: starting -> ready
Apr 18 21:48:54 exarch NetworkManager[565]: <info>  [1492541334.3893] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 
Apr 18 21:48:57 exarch NetworkManager[565]: <info>  [1492541337.8023] manager: startup complete
Apr 18 21:48:57 exarch NetworkManager[565]: <info>  [1492541337.8028] device (wlp4s0): supplicant interface state: ready -> inactive
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.0839] device (wlp4s0): Activation: starting connection 'Kablonet Netmaster-DE11-A' (40b628d1-3bcc-477f-9
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.0842] audit: op="connection-activate" uuid="40b628d1-3bcc-477f-97d8-1cf6a6c83d42" name="Kablonet Netmast
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.0845] device (wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.0849] manager: NetworkManager state is now CONNECTING
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.0857] device (wlp4s0): set-hw-addr: reset MAC address to 28:CF:E9:13:37:55 (preserve)
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.0939] device (wlp4s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.0944] device (wlp4s0): Activation: (wifi) access point 'Kablonet Netmaster-DE11-A' has security, but sec
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.0944] device (wlp4s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1004] device (wlp4s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1011] device (wlp4s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1015] device (wlp4s0): Activation: (wifi) connection 'Kablonet Netmaster-DE11-A' has security, and secre
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1016] Config: added 'ssid' value 'Kablonet Netmaster-DE11-A'
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1016] Config: added 'scan_ssid' value '1'
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1016] Config: added 'key_mgmt' value 'WPA-PSK'
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1017] Config: added 'psk' value '<hidden>'
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1464] device (wlp4s0): supplicant interface state: inactive -> disconnected
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1466] sup-iface[0x9d1e60,wlp4s0]: config: set interface ap_scan to 1
Apr 18 21:49:34 exarch NetworkManager[565]: <info>  [1492541374.1553] device (wlp4s0): supplicant interface state: disconnected -> inactive
Apr 18 21:49:35 exarch NetworkManager[565]: <info>  [1492541375.1773] device (wlp4s0): supplicant interface state: inactive -> scanning
Apr 18 21:49:38 exarch NetworkManager[565]: <info>  [1492541378.6008] device (wlp4s0): supplicant interface state: scanning -> associating
Apr 18 21:49:38 exarch NetworkManager[565]: <info>  [1492541378.6936] device (wlp4s0): supplicant interface state: associating -> associated
Apr 18 21:49:38 exarch NetworkManager[565]: <info>  [1492541378.7068] device (wlp4s0): supplicant interface state: associated -> 4-way handshake
Apr 18 21:49:38 exarch NetworkManager[565]: <info>  [1492541378.7270] device (wlp4s0): supplicant interface state: 4-way handshake -> completed
Apr 18 21:49:38 exarch NetworkManager[565]: <info>  [1492541378.7271] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wire
Apr 18 21:49:38 exarch NetworkManager[565]: <info>  [1492541378.7272] device (wlp4s0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 18 21:49:38 exarch NetworkManager[565]: <info>  [1492541378.7281] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2560] dhcp4 (wlp4s0):   address 192.168.0.14
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2560] dhcp4 (wlp4s0):   plen 24
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2561] dhcp4 (wlp4s0):   expires in 604800 seconds
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2561] dhcp4 (wlp4s0):   nameserver '46.196.235.90'
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2561] dhcp4 (wlp4s0):   nameserver '46.197.15.60'
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2561] dhcp4 (wlp4s0):   nameserver '178.233.140.110'
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2562] dhcp4 (wlp4s0):   gateway 192.168.0.1
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2566] dhcp4 (wlp4s0): state changed unknown -> bound
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2585] device (wlp4s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2595] device (wlp4s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2602] device (wlp4s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2605] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2659] manager: NetworkManager state is now CONNECTED_SITE
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2660] policy: set 'Kablonet Netmaster-DE11-A' (wlp4s0) as default for IPv4 routing and DNS
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.2675] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Apr 18 21:49:42 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 21:49:42 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 21:49:42 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 21:49:42 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 21:49:42 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 21:49:42 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 21:49:42 exarch NetworkManager[565]: <warn>  [1492541382.3272] dns-mgr: resolvconf failed with status 1024
Apr 18 21:49:42 exarch NetworkManager[565]: <warn>  [1492541382.3275] dns-mgr: could not commit DNS changes: resolvconf failed with status 1024
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.3275] device (wlp4s0): Activation: successful, device activated.
Apr 18 21:49:42 exarch NetworkManager[565]: <info>  [1492541382.5103] manager: NetworkManager state is now CONNECTED_GLOBAL

this is when I disconnect from my router:

Apr 18 22:05:58 exarch NetworkManager[565]: <info>  [1492542358.9292] device (wlp4s0): state change: activated -> deactivating (reason 'user-requested') [100 110 39]
Apr 18 22:05:58 exarch NetworkManager[565]: <info>  [1492542358.9295] manager: NetworkManager state is now DISCONNECTING
Apr 18 22:05:58 exarch NetworkManager[565]: <info>  [1492542358.9370] audit: op="device-disconnect" interface="wlp4s0" ifindex=2 pid=1249 uid=1000 result="success"
Apr 18 22:05:58 exarch NetworkManager[565]: <info>  [1492542358.9376] device (wlp4s0): state change: deactivating -> disconnected (reason 'user-requested') [110 30 39]
Apr 18 22:05:58 exarch NetworkManager[565]: <info>  [1492542358.9383] dhcp4 (wlp4s0): canceled DHCP transaction
Apr 18 22:05:58 exarch NetworkManager[565]: <info>  [1492542358.9384] dhcp4 (wlp4s0): state changed bound -> done
Apr 18 22:05:58 exarch NetworkManager[565]: <info>  [1492542358.9413] device (wlp4s0): set-hw-addr: set MAC address to 16:36:43:8A:21:FF (scanning)
Apr 18 22:05:58 exarch NetworkManager[565]: <info>  [1492542358.9418] dns-mgr: Removing DNS information from /usr/bin/resolvconf
Apr 18 22:05:58 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 22:05:58 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 22:05:58 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 22:05:58 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 22:05:58 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 22:05:58 exarch NetworkManager[565]: /etc/resolvconf.conf: line 8: nameserver: command not found
Apr 18 22:05:59 exarch systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV
Apr 18 22:05:59 exarch systemd[1]: NetworkManager.service: Unit entered failed state.
Apr 18 22:05:59 exarch systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Apr 18 22:05:59 exarch systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart.
Apr 18 22:05:59 exarch systemd[1]: Stopped Network Manager.
Apr 18 22:05:59 exarch systemd[1]: Starting Network Manager...
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2697] NetworkManager (version 1.6.2-3, Arch Linux) is starting...
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2699] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2748] manager[0x1346080]: monitoring kernel firmware directory '/usr/lib/firmware'.
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2768] dns-mgr[0x1333180]: init: dns=default, rc-manager=resolvconf
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2782] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:04:00.0/ieee80
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2784] manager[0x1346080]: WiFi hardware radio set enabled
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2784] manager[0x1346080]: WWAN hardware radio set enabled
Apr 18 22:05:59 exarch systemd[1]: Started Network Manager.
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2818] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc.  To report bugs please use the Net
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2820] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc.  To report bugs please use the NetworkManage
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.2933] keyfile: new connection /etc/NetworkManager/system-connections/BilgiGuest-e761e25f-2126-4e8a-a776
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.3039] keyfile: new connection /etc/NetworkManager/system-connections/Kablonet Netmaster-DE11-A (40b628d
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.3140] keyfile: new connection /etc/NetworkManager/system-connections/Kablonet Netmaster-DE11-G (7db3543
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4945] settings: hostname: using hostnamed
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4946] settings: hostname changed from (none) to "exarch"
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4949] dhcp-init: default DHCP client 'dhclient' is not available
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4950] dhcp-init: Using DHCP client 'internal'
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4950] manager: WiFi enabled by radio killswitch; enabled by state file
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4950] manager: WWAN enabled by radio killswitch; enabled by state file
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4951] manager: Networking is enabled by state file
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4952] Loaded device plugin: NMBondDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4952] Loaded device plugin: NMBridgeDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4952] Loaded device plugin: NMEthernetDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4952] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4953] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4953] Loaded device plugin: NMMacsecDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4954] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4954] Loaded device plugin: NMTunDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4954] Loaded device plugin: NMVethDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4955] Loaded device plugin: NMVlanDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4955] Loaded device plugin: NMVxlanDeviceFactory (internal)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4963] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/libnm-device-plugin-wifi.so)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.4985] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/libnm-device-plugin-wwan.so)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5071] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/libnm-device-plugin-team.so)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5077] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/libnm-device-plugin-adsl.so)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5084] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5100] device (lo): link connected
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5112] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5118] (wlp4s0): using nl80211 for WiFi device control
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5135] manager: (wlp4s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/2)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5155] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5167] device (wlp4s0): set-hw-addr: set MAC address to 1E:E6:61:B0:0E:AD (scanning)
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5600] supplicant: wpa_supplicant running
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5600] device (wlp4s0): supplicant interface state: init -> starting
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5655] sup-iface[0x1380e40,wlp4s0]: supports 1 scan SSIDs
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5664] device (wlp4s0): supplicant interface state: starting -> ready
Apr 18 22:05:59 exarch NetworkManager[1309]: <info>  [1492542359.5665] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30
Apr 18 22:06:02 exarch NetworkManager[1309]: <info>  [1492542362.9718] manager: startup complete

and this is when I try to reconnect:

Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7539] device (wlp4s0): Activation: starting connection 'Kablonet Netmaster-DE11-A' (40b628d1-3bcc-477f-
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7542] audit: op="connection-activate" uuid="40b628d1-3bcc-477f-97d8-1cf6a6c83d42" name="Kablonet Netmas
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7544] device (wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7547] manager: NetworkManager state is now CONNECTING
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7557] device (wlp4s0): set-hw-addr: reset MAC address to 16:36:43:8A:21:FF (preserve)
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7632] device (wlp4s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7636] device (wlp4s0): Activation: (wifi) access point 'Kablonet Netmaster-DE11-A' has security, but se
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7636] device (wlp4s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7755] device (wlp4s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7759] device (wlp4s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7762] device (wlp4s0): Activation: (wifi) connection 'Kablonet Netmaster-DE11-A' has security, and secr
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7762] Config: added 'ssid' value 'Kablonet Netmaster-DE11-A'
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7762] Config: added 'scan_ssid' value '1'
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7763] Config: added 'key_mgmt' value 'WPA-PSK'
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.7763] Config: added 'psk' value '<hidden>'
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.8030] device (wlp4s0): supplicant interface state: ready -> disconnected
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.8031] sup-iface[0x1380e40,wlp4s0]: config: set interface ap_scan to 1
Apr 18 22:06:47 exarch NetworkManager[1309]: <info>  [1492542407.8289] device (wlp4s0): supplicant interface state: disconnected -> scanning
Apr 18 22:06:51 exarch NetworkManager[1309]: <info>  [1492542411.2347] device (wlp4s0): supplicant interface state: scanning -> associating
Apr 18 22:06:51 exarch NetworkManager[1309]: <info>  [1492542411.3268] device (wlp4s0): supplicant interface state: associating -> associated
Apr 18 22:06:51 exarch NetworkManager[1309]: <info>  [1492542411.3410] device (wlp4s0): supplicant interface state: associated -> 4-way handshake
Apr 18 22:06:59 exarch NetworkManager[1309]: <info>  [1492542419.0587] device (wlp4s0): supplicant interface state: 4-way handshake -> disconnected
Apr 18 22:06:59 exarch NetworkManager[1309]: <info>  [1492542419.0602] device (wlp4s0): Activation: (wifi) disconnected during association, asking for new key
Apr 18 22:06:59 exarch NetworkManager[1309]: <info>  [1492542419.0603] device (wlp4s0): state change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8]
Apr 18 22:06:59 exarch NetworkManager[1309]: <warn>  [1492542419.0741] device (wlp4s0): No agents were available for this request.
Apr 18 22:06:59 exarch NetworkManager[1309]: <info>  [1492542419.0742] device (wlp4s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 18 22:06:59 exarch NetworkManager[1309]: <info>  [1492542419.0744] manager: NetworkManager state is now DISCONNECTED
Apr 18 22:06:59 exarch NetworkManager[1309]: <warn>  [1492542419.0750] device (wlp4s0): Activation: failed for connection 'Kablonet Netmaster-DE11-A'
Apr 18 22:06:59 exarch NetworkManager[1309]: <info>  [1492542419.0757] device (wlp4s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 18 22:06:59 exarch NetworkManager[1309]: <info>  [1492542419.0767] device (wlp4s0): set-hw-addr: set MAC address to CA:91:AC:D9:44:E9 (scanning)
Apr 18 22:06:59 exarch NetworkManager[1309]: <info>  [1492542419.1314] device (wlp4s0): supplicant interface state: disconnected -> inactive
Apr 18 22:07:15 exarch NetworkManager[1309]: <info>  [1492542435.7654] device (wlp4s0): supplicant interface state: inactive -> disconnected
Apr 18 22:07:26 exarch NetworkManager[1309]: <info>  [1492542446.7670] device (wlp4s0): supplicant interface state: disconnected -> inactive
Apr 18 22:07:27 exarch NetworkManager[1309]: <info>  [1492542447.6088] device (wlp4s0): supplicant interface state: inactive -> disconnected
Apr 18 22:07:30 exarch NetworkManager[1309]: <info>  [1492542450.7414] device (wlp4s0): supplicant interface state: disconnected -> inactive
Apr 18 22:07:47 exarch NetworkManager[1309]: <info>  [1492542467.1789] device (wlp4s0): supplicant interface state: inactive -> disconnected
Apr 18 22:08:27 exarch NetworkManager[1309]: <info>  [1492542507.7640] device (wlp4s0): supplicant interface state: disconnected -> inactive

the inactive -> disconnected cycle goes on and on

EDIT: well, upgrading the system caused my X to give a black screen. I think I've got another problem in my hands right now.

Last edited by exnihilodub (2017-04-18 19:48:54)

Trilby · 2017-04-18 20:50:06

exnihilodub wrote:

I've killed both the processes and services, restarted them, tried reconnecting and failed again.

That might be a problem. My point has been all along, that your dmenu deactivate command may not properly kill all the child processes like wpa_supplicant and dhcpcd. If you kill them yourself, great, but restarting them defeats the purpose: they may be what are preventing you from reconnecting.

seth · 2017-04-18 21:16:05

Apr 18 22:06:59 exarch NetworkManager[1309]: <info> [1492542419.0603] device (wlp4s0): state change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8]
Apr 18 22:06:59 exarch NetworkManager[1309]: <warn> [1492542419.0741] device (wlp4s0): No agents were available for this request.
Apr 18 22:06:59 exarch NetworkManager[1309]: <info> [1492542419.0742] device (wlp4s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]

How do you manage network keys? Gnome keyring?

exnihilodub · 2017-04-18 21:17:48

hey trilby fixed the X problem. without restarting the wpa_supplicant service, networkmanager fails to retrieve what wireless AP's are in the vincinity. And I remind you that this happened with other managers like wifi-menu(netctl).

exnihilodub · 2017-04-18 21:33:27

seth wrote:

Apr 18 22:06:59 exarch NetworkManager[1309]: <info> [1492542419.0603] device (wlp4s0): state change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8]
Apr 18 22:06:59 exarch NetworkManager[1309]: <warn> [1492542419.0741] device (wlp4s0): No agents were available for this request.
Apr 18 22:06:59 exarch NetworkManager[1309]: <info> [1492542419.0742] device (wlp4s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
How do you manage network keys? Gnome keyring?

I'm not sure sir, I've used nm-applet's connection manager to enter keys per network. Same with wifi-menu when I used to use it.

balazs.mezei · 2017-04-18 21:44:15

Apr 18 11:18:07 UserName NetworkManager[1163]: <info> [1492503487.6719] device (wlp4s0): supplicant interface state: associating -> completed
Apr 18 11:18:07 UserName NetworkManager[1163]: <info> [1492503487.6720] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Bilg
Apr 18 11:18:07 UserName NetworkManager[1163]: <info> [1492503487.6730] device (wlp4s0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 18 11:18:07 UserName NetworkManager[1163]: <info> [1492503487.6739] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Apr 18 11:18:52 UserName NetworkManager[1163]: <warn> [1492503532.8890] dhcp4 (wlp4s0): request timed out
Apr 18 11:18:52 UserName NetworkManager[1163]: <info> [1492503532.8890] dhcp4 (wlp4s0): state changed unknown -> timeout
Apr 18 11:18:52 UserName NetworkManager[1163]: <info> [1492503532.9090] dhcp4 (wlp4s0): canceled DHCP transaction

Your computer managed to reconnect to the wireless network, but it did not get an IP address (DHCP didn't complete). There could be an error somewhere else in the network. What's your router? Try rebooting the router and try again. What happens if you just restart NetworkManager? (sudo systemctl restart NetworkManager).

You can check if you have connected to the wifi by running "iw dev wlp4s0 link".

Last edited by balazs.mezei (2017-04-18 21:45:23)

seth · 2017-04-18 21:44:44

This could turn out to be a problem w/ using network manager - ensure to install gnome-keyring if it remains.
However, wifi-menu uses netctl which stores passwords in the profiles.

First, figure whether this is a problem w/ the hardware. Disable networkmanager and try to manually connect/disconnect/connect:
https://wiki.archlinux.org/index.php/Wi … nual_setup

If this fails, check rfkill and dmesg - the device could eg. fail to re-initialize.

exnihilodub · 2017-04-19 13:44:55

seth wrote:

This could turn out to be a problem w/ using network manager - ensure to install gnome-keyring if it remains.
However, wifi-menu uses netctl which stores passwords in the profiles.
First, figure whether this is a problem w/ the hardware. Disable networkmanager and try to manually connect/disconnect/connect:
https://wiki.archlinux.org/index.php/Wi … nual_setup
If this fails, check rfkill and dmesg - the device could eg. fail to re-initialize.

Thanks seth, I've disabled WPA on my router to minimize the probability of me making a mistake and complicating the proccess less. Connecting/Disconnecting/Connecting manually is actually working.

[root@exarch ]# ip link set dev wlp4s0 up
[root@exarch ]# iw dev wlp4s0 connect "Kablonet Netmaster-DE11-A"
[root@exarch ]# iw dev wlp4s0 link
Connected to fc:4a:e9:63:de:17 (on wlp4s0)
	SSID: Kablonet Netmaster-DE11-A
	freq: 5180
	signal: -37 dBm
	tx bitrate: 216.5 MBit/s
[root@exarch ]# dhcpcd wlp4s0
DUID 00:01:00:01:20:40:e9:85:00:e0:4c:53:44:58
wlp4s0: IAID e9:13:37:55
wlp4s0: soliciting a DHCP lease
wlp4s0: offered 192.168.0.14 from 192.168.0.1
wlp4s0: soliciting an IPv6 router
wlp4s0: probing address 192.168.0.14/24
wlp4s0: leased 192.168.0.14 for 604800 seconds
wlp4s0: adding route to 192.168.0.0/24
wlp4s0: adding default route via 192.168.0.1
/etc/resolvconf.conf: line 8: nameserver: command not found
/etc/resolvconf.conf: line 8: nameserver: command not found
/etc/resolvconf.conf: line 8: nameserver: command not found
/etc/resolvconf.conf: line 8: nameserver: command not found
/etc/resolvconf.conf: line 8: nameserver: command not found
/etc/resolvconf.conf: line 8: nameserver: command not found
forked to background, child pid 1154
[root@exarch ]# killall dhcpcd
[root@exarch ]# ip link set dev wlp4s0 down
[root@exarch ]# ip link set dev wlp4s0 up  
[root@exarch ]# iw dev wlp4s0 connect "Kablonet Netmaster-DE11-A"
[root@exarch ]# iw dev wlp4s0 link
Connected to fc:4a:e9:63:de:17 (on wlp4s0)
	SSID: Kablonet Netmaster-DE11-A
	freq: 5180
	signal: -36 dBm
	tx bitrate: 216.5 MBit/s
[root@exarch ]# dhcpcd wlp4s0
DUID 00:01:00:01:20:40:e9:85:00:e0:4c:53:44:58
wlp4s0: IAID e9:13:37:55
wlp4s0: adding address fe80::cdc2:2c65:2b94:99c6
wlp4s0: soliciting an IPv6 router
wlp4s0: rebinding lease of 192.168.0.14
wlp4s0: leased 192.168.0.14 for 604800 seconds
wlp4s0: adding route to 192.168.0.0/24
wlp4s0: adding default route via 192.168.0.1
/etc/resolvconf.conf: line 8: nameserver: command not found
forked to background, child pid 1192
[root@exarch ]#

Later today I'll try connecting with NetworkManager without WPA to see if it's a WPA key issue or something else.

Last edited by exnihilodub (2017-04-19 13:51:55)

exnihilodub · 2017-04-19 21:56:37

Hi. I couldn't manage to run iw dev after NetworkManager to see if it'll connect to a network without a WPA key. It just didn't connect when I tried iw dev wlp4s0 connect (I'd appreciate it if anyone could teach me how to get debug messages for iw. I don't think --debug option is human readable). Though I did try doing that with WPA enabled, and saw this:

After connecting with NetworkManager and disconnecting, wpa supplicant will give a wrong key warning even though I kill NetworkManager and wpa_supplicant.

here's the output of such occurence:

[root@exarch ]# wpa_supplicant -D nl80211,wext -i wlp4s0 -c <(wpa_passphrase "Kablonet Netmaster-DE11-A" "79d008ca")
Successfully initialized wpa_supplicant
wlp4s0: Trying to associate with fc:4a:e9:63:de:17 (SSID='Kablonet Netmaster-DE11-A' freq=5180 MHz)
wlp4s0: Associated with fc:4a:e9:63:de:17
wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=fc:4a:e9:63:de:17 reason=0
wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Kablonet Netmaster-DE11-A" auth_failures=1 duration=10 reason=WRONG_KEY
wlp4s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="Kablonet Netmaster-DE11-A"
wlp4s0: Trying to associate with fc:4a:e9:63:de:17 (SSID='Kablonet Netmaster-DE11-A' freq=5180 MHz)
wlp4s0: Associated with fc:4a:e9:63:de:17
wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=fc:4a:e9:63:de:17 reason=0
wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Kablonet Netmaster-DE11-A" auth_failures=2 duration=23 reason=WRONG_KEY
^Cnl80211: deinit ifname=wlp4s0 disabled_11b_rates=0
wlp4s0: CTRL-EVENT-TERMINATING

Also checked the directory NetworkManager stores its passwords. the keys look correct there. even if they weren't, I still don't understand how those keys could effect my connection when I kill NetworkManager and wpa_supplicant, and try again by supplying WPA directly as:

wpa_supplicant -D nl80211,wext -i wlp4s0 -c <(wpa_passphrase "Kablonet Netmaster-DE11-A" "79d008ca")

Thanks again for your help

Last edited by exnihilodub (2017-04-19 21:57:36)

seth · 2017-04-20 06:51:12

I couldn't manage to run iw dev after NetworkManager

That's not an error message. "How" could you not run iw dev?

After connecting with NetworkManager and disconnecting, wpa supplicant

That's going to fail for pretty much sure because you're trying to manage the device from two processes at the same time (race condition)

Please leave networkmanager away for the moment and just try to connect/disconnect/connect to the network using wpa_supplicant.

exnihilodub · 2017-04-20 10:29:20

a post above I've explained doing a connection cycle with wpa_supplicant and iw works.

Also I tried to explain that after running NetworkManager and killing it, trying iw dev doesn't output any message. and I'd appreciate a debug method. All I know is iw dev wlp4s0 link gives a "Not Connected" output. I can post the result of --debug when I get home.

Also I'd like to remind you, I kill those proccesses between each try: Run NetworkManager, connect, disconnect, kill NetworkManager, kill wpa_supplicant, try connecting with wpa_supplicant again (and fail).

Last edited by exnihilodub (2017-04-20 10:31:50)

seth · 2017-04-20 12:53:34

This

After connecting with NetworkManager and disconnecting, wpa supplicant will give a wrong key warning even though I kill NetworkManager and wpa_supplicant.

rather read like a networkmanager/disconnect/wpa_supplicant chain to me and the post before suggests you disabled WPA to rule that out first.

To stress my point: get networkmanager out of the way *entirely*. Disable the service, don't run it at all, reboot, ensure NM isn't running, then try a pure wpa cycle.

"--debug" is the human readable debug output - if there's no "iw dev" output at all (and the process doesn't hang) there's no wireless device remaining (re-init issue?)
=> check dmesg, maybe try to un- and reload the module for your chip, but before everything else, please get NM out of the way for a test.

exnihilodub · 2017-04-20 19:42:49

seth wrote:

This
After connecting with NetworkManager and disconnecting, wpa supplicant will give a wrong key warning even though I kill NetworkManager and wpa_supplicant.
rather read like a networkmanager/disconnect/wpa_supplicant chain to me and the post before suggests you disabled WPA to rule that out first.
To stress my point: get networkmanager out of the way *entirely*. Disable the service, don't run it at all, reboot, ensure NM isn't running, then try a pure wpa cycle.
"--debug" is the human readable debug output - if there's no "iw dev" output at all (and the process doesn't hang) there's no wireless device remaining (re-init issue?)
=> check dmesg, maybe try to un- and reload the module for your chip, but before everything else, please get NM out of the way for a test.

thanks and I'll try doing reloading the modules later today.

Just to clarify: I've done this: Boot-> connect with wpa -> turn interface down -> connect with wpa (post #15). I apologize about the post being unclear.

Everything works manually, even if it has a password or not (iw dev/wpa_supplicant). Can connect as many time as I'd like.
everything fails. when you introduce NetworkManager to it. We're almost final the problem is there.

Since rebooting is the only remedy to this, I was going to ask if there's anything I can do to revert things to their working state without rebooting (what I've tried was killing processes and stopping services.). Thanks for the tip on reloading the modules.

Last edited by exnihilodub (2017-04-20 19:52:05)

seth · 2017-04-20 20:02:42

Keeping networkmanager out of the way - does wifi-menu/netctl work as expected?

If you desire to use networkmanager: "pacman -Qi gnome-keyring"?

exnihilodub · 2017-04-20 21:04:25

seth wrote:

Keeping networkmanager out of the way - does wifi-menu/netctl work as expected?
If you desire to use networkmanager: "pacman -Qi gnome-keyring"?

Wifi-menu does work now sir. Apparently my previous problem with wifi-menu was the connection services staying active between connections, that's why it rejected to connect.

I've just installed keyring since networkmanager also had problems on networks without WPA. Didn't think it would've been the culprit. Will report after checking this.

exnihilodub · 2017-04-21 01:06:49

Hi. I don't know how it occured to me, but I think I've solved the problem by adding

[device]
wifi.scan-rand-mac-address=no

in NetworkManager config. Seems like it's a default proccess (I don't know why.) and I can't connect to any network if my MAC address is changed.

A few questions have emerged, though I think I'll research those first, then open a new thread if I fail: Why is it that I can't connect if my MAC address is changed? What should I do if I want to spoof my MAC? setting a new MAC by using iwconfig "devicename" hw ether xx:xx:xx:xx:xx:xx gives the error "siocsifhwaddr: too many open files in system"(ulimit is unlimited), sets the new MAC addr. until the next reboot, also renders me incapable of connecting to any network.

Thank you all for bearing with me on this and I appreciate your help and time.

Update: The MAC address issue appears to be a limitation of the horrid broadcom drivers.

Last edited by exnihilodub (2017-04-21 01:13:23)

Arch Linux

#1 2017-04-18 08:32:12

[Solved]Can't connect to Wi-Fi network after disconnecting from one.

#2 2017-04-18 10:35:10

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#3 2017-04-18 13:31:03

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#4 2017-04-18 17:52:32

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#5 2017-04-18 18:05:35

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#6 2017-04-18 18:21:32

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#7 2017-04-18 18:56:18

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#8 2017-04-18 19:17:13

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#9 2017-04-18 20:50:06

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#10 2017-04-18 21:16:05

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#11 2017-04-18 21:17:48

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#12 2017-04-18 21:33:27

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#13 2017-04-18 21:44:15

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#14 2017-04-18 21:44:44

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#15 2017-04-19 13:44:55

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#16 2017-04-19 21:56:37

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#17 2017-04-20 06:51:12

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#18 2017-04-20 10:29:20

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#19 2017-04-20 12:53:34

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#20 2017-04-20 19:42:49

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#21 2017-04-20 20:02:42

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#22 2017-04-20 21:04:25

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

#23 2017-04-21 01:06:49

Re: [Solved]Can't connect to Wi-Fi network after disconnecting from one.

Board footer