You are not logged in.

Pages: 1

#1 2020-12-23 03:46:00

RVA965
Member
Registered: 2020-12-23
Posts: 3

NetworkManager cannot get an ip-configuration

NetworkManager was working fine and then suddenly, within the span of a second, wifi doesn't work anymore. It keeps getting stuck on 

ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')

I have tried multiple things:
Using a different dhcp client (dhclient). No dice.
Turning off systemd-resolved. Doesn't work, resolv.conf has no nameservers in it.
I tried configuring network manager to not touch a static resolv.conf and added nameservers like 192.168.1.1 and 8.8.8.8. Nothing worked.
Tried openresolv. Nothing

Note, if I try to connect to my phone's hotspot(cellular data), wifi works (though it disconnects often). I am not sure if that is indicative of a router/modem/ISPissue but any information would be great.

Here are my enabled units: 

UNIT FILE                          STATE   VENDOR PRESET
cups.path                          enabled disabled
bluetooth.service                  enabled disabled
cups.service                       enabled disabled
getty@.service                     enabled enabled
NetworkManager-dispatcher.service  enabled disabled
NetworkManager-wait-online.service enabled disabled
NetworkManager.service             enabled disabled
optimus-manager.service            enabled disabled
sshd.service                       enabled disabled
system76-firmware-daemon.service   enabled disabled
system76.service                   enabled disabled
systemd-resolved.service           enabled enabled
cups.socket                        enabled disabled
remote-fs.target                   enabled enabled

Network Manager Logs: 

Dec 22 19:07:40 RVA NetworkManager[2363]: <info>  [1608692860.4749] Config: added 'ssid' value 'homer-5G'
Dec 22 19:07:40 RVA NetworkManager[2363]: <info>  [1608692860.4749] Config: added 'scan_ssid' value '1'
Dec 22 19:07:40 RVA NetworkManager[2363]: <info>  [1608692860.4749] Config: added 'bgscan' value 'simple:30:-70:86400'
Dec 22 19:07:40 RVA NetworkManager[2363]: <info>  [1608692860.4749] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Dec 22 19:07:40 RVA NetworkManager[2363]: <info>  [1608692860.4749] Config: added 'psk' value '<hidden>'
Dec 22 19:07:40 RVA kernel: iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
Dec 22 19:07:40 RVA NetworkManager[2363]: <info>  [1608692860.6129] device (wlp0s20f3): supplicant interface state: interface_disabled -> disconnected
Dec 22 19:07:40 RVA NetworkManager[2363]: <info>  [1608692860.6130] device (p2p-dev-wlp0s20f3): supplicant management interface state: interface_disabled -> disconnected
Dec 22 19:07:40 RVA NetworkManager[2363]: <info>  [1608692860.6253] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
Dec 22 19:07:40 RVA NetworkManager[2363]: <info>  [1608692860.6253] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
Dec 22 19:07:43 RVA wpa_supplicant[517]: wlp0s20f3: SME: Trying to authenticate with 9c:3d:cf:0b:9e:d7 (SSID='homer-5G' freq=5765 MHz)
Dec 22 19:07:43 RVA wpa_supplicant[517]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Dec 22 19:07:43 RVA NetworkManager[2363]: <info>  [1608692863.6996] device (wlp0s20f3): supplicant interface state: scanning -> authenticating
Dec 22 19:07:43 RVA NetworkManager[2363]: <info>  [1608692863.6996] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating
Dec 22 19:07:43 RVA kernel: wlp0s20f3: authenticate with 9c:3d:cf:0b:9e:d7
Dec 22 19:07:43 RVA kernel: wlp0s20f3: send auth to 9c:3d:cf:0b:9e:d7 (try 1/3)
Dec 22 19:07:43 RVA wpa_supplicant[517]: wlp0s20f3: Trying to associate with 9c:3d:cf:0b:9e:d7 (SSID='homer-5G' freq=5765 MHz)
Dec 22 19:07:43 RVA NetworkManager[2363]: <info>  [1608692863.7401] device (wlp0s20f3): supplicant interface state: authenticating -> associating
Dec 22 19:07:43 RVA NetworkManager[2363]: <info>  [1608692863.7401] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
Dec 22 19:07:43 RVA kernel: wlp0s20f3: authenticated
Dec 22 19:07:43 RVA kernel: wlp0s20f3: associate with 9c:3d:cf:0b:9e:d7 (try 1/3)
Dec 22 19:07:43 RVA wpa_supplicant[517]: wlp0s20f3: Associated with 9c:3d:cf:0b:9e:d7
Dec 22 19:07:43 RVA wpa_supplicant[517]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dec 22 19:07:43 RVA kernel: wlp0s20f3: RX AssocResp from 9c:3d:cf:0b:9e:d7 (capab=0x1011 status=0 aid=1)
Dec 22 19:07:43 RVA kernel: wlp0s20f3: associated
Dec 22 19:07:43 RVA NetworkManager[2363]: <info>  [1608692863.7511] device (wlp0s20f3): supplicant interface state: associating -> associated
Dec 22 19:07:43 RVA NetworkManager[2363]: <info>  [1608692863.7512] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated
Dec 22 19:07:43 RVA kernel: wlp0s20f3: Limiting TX power to 30 (30 - 0) dBm as advertised by 9c:3d:cf:0b:9e:d7
Dec 22 19:07:45 RVA NetworkManager[2363]: <info>  [1608692865.4156] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake
Dec 22 19:07:45 RVA NetworkManager[2363]: <info>  [1608692865.4156] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake
Dec 22 19:07:45 RVA wpa_supplicant[517]: wlp0s20f3: WPA: Key negotiation completed with 9c:3d:cf:0b:9e:d7 [PTK=CCMP GTK=CCMP]
Dec 22 19:07:45 RVA wpa_supplicant[517]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 9c:3d:cf:0b:9e:d7 completed [id=0 id_str=]
Dec 22 19:07:45 RVA wpa_supplicant[517]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-42 noise=9999 txrate=6000
Dec 22 19:07:45 RVA NetworkManager[2363]: <info>  [1608692865.6003] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed
Dec 22 19:07:45 RVA NetworkManager[2363]: <info>  [1608692865.6003] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "homer-5G"
Dec 22 19:07:45 RVA NetworkManager[2363]: <info>  [1608692865.6004] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed
Dec 22 19:07:45 RVA kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
Dec 22 19:07:45 RVA NetworkManager[2363]: <info>  [1608692865.6008] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 22 19:07:45 RVA NetworkManager[2363]: <info>  [1608692865.6016] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Dec 22 19:07:49 RVA systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Dec 22 19:07:49 RVA audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 22 19:07:49 RVA kernel: audit: type=1131 audit(1608692869.877:233): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 22 19:07:53 RVA dbus-daemon[431]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.63' (uid=0 pid=2363 comm="/usr/bin/NetworkManager --no-daemon ")
Dec 22 19:07:53 RVA systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 22 19:07:53 RVA dbus-daemon[431]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 22 19:07:53 RVA systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 22 19:07:53 RVA audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 22 19:07:53 RVA kernel: audit: type=1130 audit(1608692873.207:234): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 22 19:07:56 RVA wpa_supplicant[517]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-48 noise=9999 txrate=866700
Dec 22 19:08:03 RVA systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Dec 22 19:08:03 RVA audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 22 19:08:03 RVA kernel: audit: type=1131 audit(1608692883.877:235): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 22 19:08:30 RVA NetworkManager[2363]: <warn>  [1608692910.8706] dhcp4 (wlp0s20f3): request timed out
Dec 22 19:08:30 RVA NetworkManager[2363]: <info>  [1608692910.8707] dhcp4 (wlp0s20f3): state changed unknown -> timeout
Dec 22 19:08:30 RVA NetworkManager[2363]: <info>  [1608692910.8708] device (wlp0s20f3): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Dec 22 19:08:30 RVA NetworkManager[2363]: <info>  [1608692910.8718] manager: NetworkManager state is now DISCONNECTED
Dec 22 19:08:30 RVA kernel: wlp0s20f3: deauthenticating from 9c:3d:cf:0b:9e:d7 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 22 19:08:30 RVA NetworkManager[2363]: <info>  [1608692910.9053] device (wlp0s20f3): set-hw-addr: set MAC address to C2:18:AE:52:4C:02 (scanning)
Dec 22 19:08:31 RVA wpa_supplicant[517]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
Dec 22 19:08:31 RVA NetworkManager[2363]: <warn>  [1608692911.1123] device (wlp0s20f3): Activation: failed for connection 'homer-5G'
Dec 22 19:08:31 RVA NetworkManager[2363]: <info>  [1608692911.1126] device (wlp0s20f3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Dec 22 19:08:31 RVA kernel: iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
Dec 22 19:08:31 RVA wpa_supplicant[517]: wlp0s20f3: Reject scan trigger since one is already pending
Dec 22 19:08:31 RVA wpa_supplicant[517]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD

Result of ip addr:

 <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defa
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state D
    link/ether 80:fa:5b:7b:ce:24 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state U
    link/ether 0c:7a:15:0c:58:dc brd ff:ff:ff:ff:ff:ff
    inet6 fe80::2a1:ffb6:27dd:281d/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

ip route returns nothing.

Since I have systemd-resolved enabled, my resolv.conf is a symlink that looks like

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 1.1.1.1
nameserver 9.9.9.10
nameserver 8.8.8.8
# Too many DNS servers configured, the following entries may be ignored.
nameserver 2606:4700:4700::1111
nameserver 2620:fe::10
nameserver 2001:4860:4860::8888
search .

Offline

#2 2020-12-23 09:27:45

seth
Member
Registered: 2012-09-03
Posts: 60,955

Re: NetworkManager cannot get an ip-configuration

Dec 22 19:08:30 RVA NetworkManager[2363]: <warn>  [1608692910.8706] dhcp4 (wlp0s20f3): request timed out
Dec 22 19:08:30 RVA NetworkManager[2363]: <info>  [1608692910.8707] dhcp4 (wlp0s20f3): state changed unknown -> timeout

Looking at dhcp is the reasonable approach.
resolver and route come after this step anyway, so if it fails already there, the other two are irrelevant for the moment.

a) ensure that you effectively changed to dhclient (see journal)
b) disable https://wiki.archlinux.org/index.php/Ne … domization
c) reboot the router (could have a stale lease and reject you)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB