Arch Linux

apechimp

Member

Registered: 2020-08-16

Posts: 2

[SOLVED] Network doesn't come up every other reboot

I'm having some bizarre networking issues after setting my router to reserve my computer's IP address. When it boots up, the network doesn't come online (link shows as down) and restarting networkd doesn't have an effect. Then, I reboot it and the network will come up, but without getting an IP via DHCP (it has this weird ipv6 one). At this point, restarting networkd, will have an effect and I get the IP that is reserved for my computer.

I was originally using dhcpcd, but switched to networkd thinking I had something misconfigured somehow. Here are the networkd logs from one iteration of the pattern. Starting with a boot where everything worked fine, then the issue as described.

-- Reboot --
Aug 16 07:22:49 nuchimputer systemd[1]: Starting Network Service...
Aug 16 07:22:50 nuchimputer systemd-networkd[244]: Enumeration completed
Aug 16 07:22:50 nuchimputer systemd[1]: Started Network Service.
Aug 16 07:22:51 nuchimputer systemd-networkd[244]: eth0: Interface name change detected, eth0 has been renamed to eno1.
Aug 16 07:22:51 nuchimputer systemd-networkd[244]: eno1: IPv6 successfully enabled
Aug 16 07:22:51 nuchimputer systemd-networkd[244]: eno1: Link UP
Aug 16 07:22:51 nuchimputer systemd-networkd[244]: wlan0: Interface name change detected, wlan0 has been renamed to wlp0s20f3.
Aug 16 07:22:59 nuchimputer systemd-networkd[244]: eno1: Gained carrier
Aug 16 07:23:01 nuchimputer systemd-networkd[244]: eno1: Gained IPv6LL
Aug 16 07:23:03 nuchimputer systemd-networkd[244]: eno1: DHCPv4 address 192.168.0.183/24 via 192.168.0.1
Aug 16 07:23:04 nuchimputer systemd-networkd[244]: rtnl: received neighbor for link '4' we don't know about, ignoring.
Aug 16 07:23:04 nuchimputer systemd-networkd[244]: rtnl: received neighbor for link '4' we don't know about, ignoring.
Aug 16 07:23:04 nuchimputer systemd-networkd[244]: rtnl: received neighbor for link '4' we don't know about, ignoring.
Aug 16 07:23:04 nuchimputer systemd-networkd[244]: rtnl: received neighbor for link '4' we don't know about, ignoring.
Aug 16 07:23:04 nuchimputer systemd-networkd[244]: docker0: Link UP
Aug 16 09:09:28 nuchimputer systemd[1]: Stopping Network Service...
Aug 16 09:09:28 nuchimputer systemd-networkd[244]: eno1: DHCP lease lost
Aug 16 09:09:28 nuchimputer systemd-networkd[244]: eno1: DHCPv6 lease lost
Aug 16 09:09:28 nuchimputer systemd[1]: systemd-networkd.service: Succeeded.
Aug 16 09:09:28 nuchimputer systemd[1]: Stopped Network Service.
-- Reboot --
Aug 16 14:33:55 nuchimputer systemd[1]: Starting Network Service...
Aug 16 14:33:56 nuchimputer systemd-networkd[234]: Enumeration completed
Aug 16 14:33:56 nuchimputer systemd[1]: Started Network Service.
Aug 16 14:33:57 nuchimputer systemd-networkd[234]: wlan0: Interface name change detected, wlan0 has been renamed to wlp0s20f3.
Aug 16 14:33:57 nuchimputer systemd-networkd[234]: eth0: Interface name change detected, eth0 has been renamed to eno1.
Aug 16 14:33:57 nuchimputer systemd-networkd[234]: eno1: IPv6 successfully enabled
Aug 16 14:33:57 nuchimputer systemd-networkd[234]: eno1: Link UP
Aug 16 14:35:25 nuchimputer systemd[1]: Stopping Network Service...
Aug 16 14:35:25 nuchimputer systemd-networkd[234]: eno1: DHCPv6 lease lost
Aug 16 14:35:25 nuchimputer systemd[1]: systemd-networkd.service: Succeeded.
Aug 16 14:35:25 nuchimputer systemd[1]: Stopped Network Service.
-- Reboot --
Aug 16 14:35:42 nuchimputer systemd[1]: Starting Network Service...
Aug 16 14:35:43 nuchimputer systemd-networkd[244]: Enumeration completed
Aug 16 14:35:43 nuchimputer systemd[1]: Started Network Service.
Aug 16 14:35:44 nuchimputer systemd-networkd[244]: wlan0: Interface name change detected, wlan0 has been renamed to wlp0s20f3.
Aug 16 14:35:44 nuchimputer systemd-networkd[244]: eth0: Interface name change detected, eth0 has been renamed to eno1.
Aug 16 14:35:44 nuchimputer systemd-networkd[244]: eno1: IPv6 successfully enabled
Aug 16 14:35:44 nuchimputer systemd-networkd[244]: eno1: Link UP
Aug 16 14:35:52 nuchimputer systemd-networkd[244]: eno1: Gained carrier
Aug 16 14:35:53 nuchimputer systemd-networkd[244]: eno1: Gained IPv6LL
Aug 16 14:37:11 nuchimputer systemd-networkd[244]: eno1: DHCPv6 lease lost
Aug 16 14:37:11 nuchimputer systemd[1]: Stopping Network Service...
Aug 16 14:37:11 nuchimputer systemd[1]: systemd-networkd.service: Succeeded.
Aug 16 14:37:11 nuchimputer systemd[1]: Stopped Network Service.
Aug 16 14:37:11 nuchimputer systemd[1]: Starting Network Service...
Aug 16 14:37:11 nuchimputer systemd-networkd[1019]: eno1: Gained IPv6LL
Aug 16 14:37:11 nuchimputer systemd-networkd[1019]: Enumeration completed
Aug 16 14:37:11 nuchimputer systemd[1]: Started Network Service.
Aug 16 14:37:11 nuchimputer systemd-networkd[1019]: eno1: IPv6 successfully enabled
Aug 16 14:37:12 nuchimputer systemd-networkd[1019]: rtnl: received neighbor for link '4' we don't know about, ignoring.
Aug 16 14:37:12 nuchimputer systemd-networkd[1019]: rtnl: received neighbor for link '4' we don't know about, ignoring.
Aug 16 14:37:12 nuchimputer systemd-networkd[1019]: rtnl: received neighbor for link '4' we don't know about, ignoring.
Aug 16 14:37:12 nuchimputer systemd-networkd[1019]: rtnl: received neighbor for link '4' we don't know about, ignoring.
Aug 16 14:37:12 nuchimputer systemd-networkd[1019]: docker0: Link UP
Aug 16 14:37:14 nuchimputer systemd-networkd[1019]: eno1: DHCPv4 address 192.168.0.183/24 via 192.168.0.1

Here is my networkd configuration: /etc/systemd/network/20-wired.network

[Match]
Name=eno1

[Network]
DHCP=ipv4

Any ideas what's going on? It seems weird that the DHCP lease gets lost when networkd stops and weird that it has a DHCPv6 lease to lose, but I don't know very much about DHCP, so maybe that's red herring: grasping at straws here

Last edited by apechimp (2020-08-20 00:53:46)

apechimp

Member

Registered: 2020-08-16

Posts: 2

Re: [SOLVED] Network doesn't come up every other reboot

I left out a detail that I didn't fully understand at the time which appears to be the cause of the issue. I was using an ARP binding in my router (tp-link archer a9) so that I could use Wake-on-Lan over WAN via port forwarding. Removing that binding made it so that my router would reliably send DHCPv4 leases back to my computer. I was able to add the ARP binding back after setting up a static IP via the following configuration.

[Match]
Name=eno1

[Link]
ARP=true

[Network]
Address=192.168.0.183/24
Gateway=192.168.0.1
DNS=192.168.0.1