[Solved] Ethernet gradually worsens until it is unusable; wifi if fine

TophDoggy · 2022-04-22 13:59:48

This problem started yesterday. I logged into my laptop and everything was fine. I shut down dhcpcd so that I could set a static ip. At first everything was fine, I could ping, I could surf the web. Then I couldn't. I then dhcpcd on eno1, which gave me an ip I'd expect, but pinging just hangs. I try setting another static ip, but it has the same symptoms as dhcpcd (as I try static ips I'm sure to flush the interface and kill any existing instances of dhcpcd. I had already disabled the systemctl services). Eventually, dhcpcd devolves to assigning me an ip that is not consistent with my network and pinging tells me I have DNS issues. I got so frustrated I backed up my system and popped in a live usb with the intention of doing a fresh install. I took a breath and walked away for several hours, and when I booted things back up, everything was working again. A little while later I go to set a static ip and everything described above has happened again. Apologies if any of the formatting is off or if this is otherwise incorrect, this is my first post. It's now 6:30am, so I'm backing away from my laptop for a while, but I'll be back in a few hours. Please let me know if there are any other logs or information needed.

LC_ALL=C

2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether ec:f4:bb:5f:3c:1e brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 192.168.88.94/24 scope global eno1
       valid_lft forever preferred_lft forever
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 80:00:0b:19:4e:20 brd ff:ff:ff:ff:ff:ff
    inet 192.168.88.92/24 brd 192.168.88.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 494sec preferred_lft 419sec
    inet6 fe80::52c2:82e0:66ac:76f9/64 scope link 
       valid_lft forever preferred_lft forever

[topher@TLaptop ~]$ sudo ip route add 192.168.88.0/24 dev eno1
RTNETLINK answers: File exists
[topher@TLaptop ~]$ sudo ip route add default via 192.168.88.1 dev eno1
[topher@TLaptop ~]$ ping archlinux.org
ping: archlinux.org: Temporary failure in name resolution

[topher@TLaptop ~]$ sudo dhcpcd eno1
dhcpcd-9.4.1 starting
DUID 00:04:4c:4c:45:44:00:48:46:10:80:47:b3:c0:4f:4a:31:32
eno1: IAID bb:5f:3c:1e
eno1: adding address fe80::d083:27ac:4124:4419
eno1: soliciting an IPv6 router
eno1: soliciting a DHCP lease
eno1: no IPv6 Routers available
timed out

Apr 22 06:35:40 TLaptop dhcpcd[3060]: DUID 00:04:4c:4c:45:44:00:48:46:10:80:47:b3:c0:4f:4a:31:32
Apr 22 06:35:40 TLaptop dhcpcd[3060]: eno1: IAID bb:5f:3c:1e
Apr 22 06:35:40 TLaptop dhcpcd[3060]: eno1: soliciting an IPv6 router
Apr 22 06:35:41 TLaptop dhcpcd[3060]: eno1: soliciting a DHCP lease
Apr 22 06:35:52 TLaptop dhcpcd[3060]: eno1: no IPv6 Routers available
Apr 22 06:36:10 TLaptop dhcpcd[3060]: timed out
Apr 22 06:36:10 TLaptop sudo[3056]: pam_unix(sudo:session): session closed for user root
Apr 22 06:36:10 TLaptop audit[3056]: USER_END pid=3056 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Apr 22 06:36:10 TLaptop audit[3056]: CRED_DISP pid=3056 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Apr 22 06:36:10 TLaptop kernel: audit: type=1106 audit(1650634570.037:374): pid=3056 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Apr 22 06:36:10 TLaptop kernel: audit: type=1104 audit(1650634570.037:375): pid=3056 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'

WiFi, just for comparison...

[topher@TLaptop ~]$ pgrep dhcpcd
[topher@TLaptop ~]$ sudo ip add flush wlp3s0
[topher@TLaptop ~]$ sudo dhcpcd wlp3s0
dhcpcd-9.4.1 starting
DUID 00:04:4c:4c:45:44:00:48:46:10:80:47:b3:c0:4f:4a:31:32
wlp3s0: connected to Access Point: TsWifi
wlp3s0: IAID 0b:19:4e:20
wlp3s0: adding address fe80::52c2:82e0:66ac:76f9
wlp3s0: soliciting an IPv6 router
wlp3s0: soliciting a DHCP lease
wlp3s0: offered 192.168.88.92 from 192.168.88.1
wlp3s0: probing address 192.168.88.92/24
wlp3s0: leased 192.168.88.92 for 600 seconds
wlp3s0: adding route to 192.168.88.0/24
wlp3s0: adding default route via 192.168.88.1
forked to background, child pid 3153

Apr 22 06:45:05 TLaptop dhcpcd[3151]: dhcpcd-9.4.1 starting
Apr 22 06:45:05 TLaptop dhcpcd[3154]: DUID 00:04:4c:4c:45:44:00:48:46:10:80:47:b3:c0:4f:4a:31:32
Apr 22 06:45:05 TLaptop dhcpcd[3154]: wlp3s0: connected to Access Point: TsWifi
Apr 22 06:45:05 TLaptop dhcpcd[3154]: wlp3s0: IAID 0b:19:4e:20
Apr 22 06:45:05 TLaptop dhcpcd[3154]: wlp3s0: adding address fe80::52c2:82e0:66ac:76f9
Apr 22 06:45:05 TLaptop dhcpcd[3154]: wlp3s0: soliciting an IPv6 router
Apr 22 06:45:06 TLaptop dhcpcd[3154]: wlp3s0: soliciting a DHCP lease
Apr 22 06:45:06 TLaptop dhcpcd[3154]: wlp3s0: offered 192.168.88.92 from 192.168.88.1
Apr 22 06:45:06 TLaptop dhcpcd[3154]: wlp3s0: probing address 192.168.88.92/24
Apr 22 06:45:11 TLaptop dhcpcd[3154]: wlp3s0: leased 192.168.88.92 for 600 seconds
Apr 22 06:45:11 TLaptop dhcpcd[3154]: wlp3s0: adding route to 192.168.88.0/24
Apr 22 06:45:11 TLaptop dhcpcd[3154]: wlp3s0: adding default route via 192.168.88.1
Apr 22 06:45:11 TLaptop sudo[3150]: pam_unix(sudo:session): session closed for user root
Apr 22 06:45:11 TLaptop audit[3150]: USER_END pid=3150 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Apr 22 06:45:11 TLaptop audit[3150]: CRED_DISP pid=3150 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Apr 22 06:45:11 TLaptop kernel: audit: type=1106 audit(1650635111.986:390): pid=3150 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Apr 22 06:45:11 TLaptop kernel: audit: type=1104 audit(1650635111.986:391): pid=3150 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Apr 22 06:45:19 TLaptop dhcpcd[3154]: wlp3s0: no IPv6 Routers available

Last edited by TophDoggy (2022-04-25 12:02:26)

seth · 2022-04-22 14:58:47

eno1: …
    altname enp0s25

wlp3s0 seems unaffected by such race condition, so try https://wiki.archlinux.org/title/Networ … face_names

progandy · 2022-04-22 15:33:37

and pinging tells me I have DNS issues

If you set a static ip, then you have to configure your dns resolvers as well. How you do that depends on how you set your static ip.

I am not sure why switching back to dhcp does not work. You said that you are stopping all networking tools like dhcpcd...

@seth: That is not really a race condition, but two different naming schemes. Systemd does choose one and adds the others as alternative names. The chosen one is always the same unless systemd configuration is changed/updated. That is set using NamesPolicy and AlternativeNamesPolicy in .link files, the default is in /usr/lib/systemd/network/99-default.link

Last edited by progandy (2022-04-22 15:45:40)

seth · 2022-04-22 16:09:04

Yes, the problem is that this is prone to cause a race condition where early starting services lose oversight - there's some other thread with similar symptoms and the naming scheme being at the root of it.
Let's see whether the forum serach function can … I think I thought of https://bbs.archlinux.org/viewtopic.php?id=274241

TophDoggy · 2022-04-23 11:40:28

I thought I had it, I actually was logging in to marked this solved. Good lord, this is frustrating.
Static IP wouldn't work, though admittedly I haven't had to manually set up a DNS resolver before, so that could have been the issue. I posted my DNS config, if you wouldn't mind letting me know if that looks like it should work.
However, dhcpcd is still not working on ethernet. I was about to say it's now having issues on wifi, but it seems ok now. My 2 access points are pretty equidistant from me, so I'll give it the benefit of the doubt and chalk it up to a fluke.
I've tried different cables, I've tried plugging directly into the router. I've used Arch on this laptop for years, I have essentially the same install on my Desktop. Ethernet works fine when I boot into a live USB. This dual boots Windows; ethernet works just fine over there. I've never had this issue before.
I'm going to bed. Hopefully someone can tell me i̶n̶ ̶t̶h̶e̶ ̶m̶o̶r̶n̶i̶n̶g̶ later this morning what is wrong, otherwise I'm just going to nuke it and start fresh.
Looking on the bright side, at least I've learned the basics of posting here, and I won't soon forget where the logs are. ¯\_(ツ)_/¯

[topher@TLaptop ~]$ sudo ip addr flush eth0 
[topher@TLaptop ~]$ sudo ip addr add 192.168.88.94/24 dev eth0
[topher@TLaptop ~]$ sudo ip route add 192.168.88.0/24 dev eth0
RTNETLINK answers: File exists
[topher@TLaptop ~]$ sudo ip route add default via 192.168.88.1 dev eth0
[topher@TLaptop ~]$ sudo systemctl enable --now systemd-resolved.service
Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service → /usr/lib/systemd/system/systemd-resolved.service.
Created symlink /etc/systemd/system/multi-user.target.wants/systemd-resolved.service → /usr/lib/systemd/system/systemd-resolved.service.
[topher@TLaptop ~]$ ping archlinux.org
ping: archlinux.org: Temporary failure in name resolution
[topher@TLaptop ~]$ cat /etc/systemd/resolved.conf

...

# See resolved.conf(5) for details.

[Resolve]
# Some examples of DNS servers which may be used for DNS= and FallbackDNS=:
# Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com
# Google:     8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google
# Quad9:      9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
DNS=8.8.8.8
#FallbackDNS=1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google
Domains=~
#DNSSEC=no
#DNSOverTLS=no
#MulticastDNS=yes
#LLMNR=yes
#Cache=yes
#CacheFromLocalhost=no
#DNSStubListener=yes
#DNSStubListenerExtra=
#ReadEtcHosts=yes
#ResolveUnicastSingleLabel=no

[topher@TLaptop ~]$ sudo ip addr flush eth0
[topher@TLaptop ~]$ sudo dhcpcd eth0
dhcpcd-9.4.1 starting
DUID 00:04:4c:4c:45:44:00:48:46:10:80:47:b3:c0:4f:4a:31:32
eth0: IAID bb:5f:3c:1e
eth0: adding address fe80::d083:27ac:4124:4419
eth0: soliciting an IPv6 router
eth0: soliciting a DHCP lease
eth0: no IPv6 Routers available
timed out

Apr 23 04:22:59 TLaptop dbus-daemon[507]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.76' (uid=0 pid=15136 comm="sudo dhcpcd eth0")
Apr 23 04:22:59 TLaptop dbus-daemon[507]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Apr 23 04:22:59 TLaptop sudo[15136]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Apr 23 04:22:59 TLaptop audit[15136]: USER_ACCT pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="topher" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Apr 23 04:22:59 TLaptop sudo[15136]:   topher : TTY=pts/2 ; PWD=/home/topher ; USER=root ; COMMAND=/usr/bin/dhcpcd eth0
Apr 23 04:22:59 TLaptop kernel: audit: type=1101 audit(1650712979.288:366): pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="topher" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Apr 23 04:22:59 TLaptop kernel: audit: type=1110 audit(1650712979.291:367): pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Apr 23 04:22:59 TLaptop audit[15136]: CRED_REFR pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Apr 23 04:22:59 TLaptop audit[15136]: USER_START pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Apr 23 04:22:59 TLaptop sudo[15136]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Apr 23 04:22:59 TLaptop dhcpcd[15137]: dhcpcd-9.4.1 starting
Apr 23 04:22:59 TLaptop dhcpcd[15140]: DUID 00:04:4c:4c:45:44:00:48:46:10:80:47:b3:c0:4f:4a:31:32
Apr 23 04:22:59 TLaptop kernel: audit: type=1105 audit(1650712979.291:368): pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Apr 23 04:22:59 TLaptop dhcpcd[15140]: eth0: IAID bb:5f:3c:1e
Apr 23 04:22:59 TLaptop dhcpcd[15140]: eth0: soliciting an IPv6 router
Apr 23 04:23:00 TLaptop dhcpcd[15140]: eth0: soliciting a DHCP lease
Apr 23 04:23:11 TLaptop dhcpcd[15140]: eth0: no IPv6 Routers available
Apr 23 04:23:29 TLaptop dhcpcd[15140]: timed out
Apr 23 04:23:29 TLaptop sudo[15136]: pam_unix(sudo:session): session closed for user root
Apr 23 04:23:29 TLaptop kernel: audit: type=1106 audit(1650713009.321:369): pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Apr 23 04:23:29 TLaptop kernel: audit: type=1104 audit(1650713009.321:370): pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Apr 23 04:23:29 TLaptop audit[15136]: USER_END pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Apr 23 04:23:29 TLaptop audit[15136]: CRED_DISP pid=15136 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'

Last edited by TophDoggy (2022-04-23 11:50:13)

seth · 2022-04-23 13:53:44

This dual boots Windows; ethernet works just fine over there.

3rd link below, mandatory. The dhcp server might ignore you because of a stale lease from the hibernating windows, so this is not theoretical.

progandy · 2022-04-23 13:59:31

As for the DNS in your static setup, you started systemd-resolved. Did you also configure your system to use it?

$ stat /etc/resolv.conf
$ cat /etc/resolv.conf

https://wiki.archlinux.org/title/Domain_name_resolution

In any case, the simplest solution for a static IP would be to just set a dns server directly in /etc/resolv.conf

TophDoggy · 2022-04-25 15:36:43

seth wrote:

3rd link below, mandatory. The dhcp server might ignore you because of a stale lease from the hibernating windows, so this is not theoretical.

Well, I'll be damned... It happens when i reboot out of Windows, whether fast start is enabled or not. I have no such issues when I poweroff then power back on. I think I never would have figured that out, but maybe I should have since dual booting is one four go to links in your signature.

I still have a couple quick questions...
#1. why doesn't flushing eth0 and setting a static ip solve the issue, especially if it's different from the ip Windows was using?
And #2. I disabled dhcpcd service and nowhere do I call for it to start, so how is it starting up?

Last edited by TophDoggy (2022-04-25 18:06:14)

seth · 2022-04-25 19:40:51

The router might reject you based on on your MAC and a stale lease - I'm not positive that there's any dhcp server still starting.

How is the IP configured on windows? Static or via DHCP?
You could try to use dhcp on both OS or assign the same static IP on both OS.
(1st speculating on a proper de-lease when terminating windows and 2nd on the router just not noticing that you're swapping out the OS)

If you've a second system, you can also inspect the router/leases while failing to get on when rebooting into linux.

Arch Linux

#1 2022-04-22 13:59:48

[Solved] Ethernet gradually worsens until it is unusable; wifi if fine

#2 2022-04-22 14:58:47

Re: [Solved] Ethernet gradually worsens until it is unusable; wifi if fine

#3 2022-04-22 15:33:37

Re: [Solved] Ethernet gradually worsens until it is unusable; wifi if fine

#4 2022-04-22 16:09:04

Re: [Solved] Ethernet gradually worsens until it is unusable; wifi if fine

#5 2022-04-23 11:40:28

Re: [Solved] Ethernet gradually worsens until it is unusable; wifi if fine

#6 2022-04-23 13:53:44

Re: [Solved] Ethernet gradually worsens until it is unusable; wifi if fine

#7 2022-04-23 13:59:31

Re: [Solved] Ethernet gradually worsens until it is unusable; wifi if fine

#8 2022-04-25 15:36:43

Re: [Solved] Ethernet gradually worsens until it is unusable; wifi if fine

#9 2022-04-25 19:40:51

Re: [Solved] Ethernet gradually worsens until it is unusable; wifi if fine

Board footer