You are not logged in.

#1 2020-01-04 17:51:30

go3stin1
Member
Registered: 2020-01-04
Posts: 2

[SOLVED] Forced to call dhcpcd at each boot to get wired connection up

Hi,

I've been having quite an odd issue for the last past week and a half or so with my wired connection.
Here is my issue: whenever I boot up after some time (let's say a few hours), NetworkManager can't connect to my wired network (it's worth mentioning that I use a Linksys USB3GIGV1).
Strangely enough, I found a very direct solution, without really knowing why it was working : I invoked dhcpcd.

Here are some logs that might be helpful:

Journalctl, when using the GUI to "force-connect" to the wired network:

janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.1975] audit: op="connection-activate" uuid="9d19020c-6fc5-39d2-a4ac-8d0230994a80" name="Maison" pid=821 uid=1000 result="success"
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.1977] device (enp0s20f0u1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.1990] manager: NetworkManager state is now CONNECTING
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.1996] device (enp0s20f0u1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.2013] device (enp0s20f0u1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.2022] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.2059] dhcp4 (enp0s20f0u1): state changed unknown -> fail
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.2061] device (enp0s20f0u1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.2072] manager: NetworkManager state is now DISCONNECTED
janv. 04 18:31:45 atlas NetworkManager[625]: <warn>  [1578159105.2090] device (enp0s20f0u1): Activation: failed for connection 'Maison'
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.2097] device (enp0s20f0u1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.2513] dhcp4 (enp0s20f0u1): canceled DHCP transaction
janv. 04 18:31:45 atlas NetworkManager[625]: <info>  [1578159105.2514] dhcp4 (enp0s20f0u1): state changed fail -> done
janv. 04 18:31:45 atlas kdeconnectd[897]: "L’interface « org.freedesktop.DBus.Properties » n’existe pas pour l’objet à l’emplacement /org/freedesktop/NetworkManager/ActiveConnection/5"

(translation of last line : "The interface « org.freedesktop.DBus.Properties » doesn't exist for the object located at /org/freedesktop/NetworkManager/ActiveConnection/5")

When calling route:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

When calling iptables -L:

https://pastebin.com/iQwqHyvV

When calling dhcpcd *which fixes the issue*:

dev: loaded udev
DUID 00:01:00:01:22:2c:29:b7:a0:ce:c8:0a:c4:34
enp0s20f0u1: IAID 68:b4:fc:70
enp0s20f0u1: adding address fe80::688e:7284:852:c8db
wlan0: waiting for carrier
enp0s20f0u1: soliciting an IPv6 router
enp0s20f0u1: rebinding lease of 192.168.0.29
enp0s20f0u1: NAK: from 192.168.0.254
enp0s20f0u1: soliciting a DHCP lease
enp0s20f0u1: offered 192.168.0.29 from 192.168.0.254
enp0s20f0u1: Router Advertisement from fe80::3627:92ff:fe42:eb03
enp0s20f0u1: adding address 2a01:e0a:29:a060:ea8d:ec2e:cee3:5ad0/64
enp0s20f0u1: adding route to 2a01:e0a:29:a060::/64
enp0s20f0u1: adding default route via fe80::3627:92ff:fe42:eb03
enp0s20f0u1: leased 192.168.0.29 for 43200 seconds
enp0s20f0u1: adding route to 192.168.0.0/24
enp0s20f0u1: adding default route via 192.168.0.254
forked to background, child pid 7500

When calling route aftewards:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         _gateway        0.0.0.0         UG    202    0        0 enp0s20f0u1
192.168.0.0     0.0.0.0         255.255.255.0   U     202    0        0 enp0s20f0u1

(uncut journalctl logs : https://pastebin.com/kWHCfH2A)

Hope it will help,

Cheers ! wink

Last edited by go3stin1 (2020-01-04 18:37:02)

Offline

#2 2020-01-04 18:03:44

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 10,083

Re: [SOLVED] Forced to call dhcpcd at each boot to get wired connection up

Please search the board, this is covered in a number of threads now, most recently: https://bbs.archlinux.org/viewtopic.php?id=251861

Offline

#3 2020-01-04 18:36:44

go3stin1
Member
Registered: 2020-01-04
Posts: 2

Re: [SOLVED] Forced to call dhcpcd at each boot to get wired connection up

My bad, I looked it up a few days ago and didn't search again today.
I guess the topic is solved.

Cheers

Offline

Board footer

Powered by FluxBB