[SOLVED] New install can't reach network

davidbryant · 2025-10-28 13:39:06

New Arch Linux install. Ping says network is unreachable.

I have a config file /etc/systemd/network/network.network:
[Match]
Name=enp0s31f6

[Network]
DHCP=yes

Here's the OP from ip link:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether ac:b4:80:3b:e6:14 brd ff:ff:ff:ff:ff:ff

I said "systemctl systemd-networkd" several times, but the network is still unreachable. Suggestions welcomed. Thanks!

Last edited by davidbryant (2025-10-28 23:18:40)

Scimmia · 2025-10-28 13:44:22

https://wiki.archlinux.org/title/Systemd#Using_units . "systemctl systemd-networkd" does nothing.

You will then also need to address DNS.

davidbryant · 2025-10-28 14:38:24

I meant to say "systemctl start systemd-networkd". Excuse me.

davidbryant · 2025-10-28 14:52:56

OK, I edited /etc/systemd/resolved.conf to say

DNS=1.1.1.1
FallbackDNS=1.0.0.1

and I said "systemctl start systemd-resolved. No errors, but still no internet. What's next?

seth · 2025-10-28 14:57:39

What are the outputs of

ip a; resolvectl status

ahepp · 2025-10-28 15:08:02

Can you post the output of the following commands:

systemctl status systemd-networkd
networkctl
ip a
ip r
ping -c 3 1.1.1.1
ping -c 3 google.com

We want to

verify systemd-networkd is actually running
see more information from systemd-networkd
determine whether the DHCP process was successful
verify the route your IP traffic will follow
test IP connectivity without involving DNS
test name resolution

davidbryant · 2025-10-28 15:20:24

ip a says

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether ac:b4:80:3b:e6:14 brd ff:ff:ff:ff:ff:ff
altname enxacb4803be614
inet 192.168.1.10/24 scope global enp0s31f6
valid_lft forever preferred_lft forever
inet6 fe80::aeb4:80ff:fe3b:e614/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever

resolvectl status said something about "failed to reach resolve1", ... I'll do it again, and take a picture.

seth · 2025-10-28 15:24:35

You have a lease but apparently no resolver.
Start/enable systemd-resolved

davidbryant · 2025-10-28 15:33:08

resolvectl status says (in red letters):

Failed to get global data: Could not activate remote peer 'org.freedesktop.resolve1' activation request failed.

davidbryant · 2025-10-28 16:13:51

OK, I said "systemctl start systemd-resolved", then "resolvectl status". That now says

Global
Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
DNS Servers: 1.1.1.1
Fallback DNS Servers: 1.0.0.1 2620:fe::9#dns.quad9.net
1.1.1.1#cloudflare-dns.com
2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google
2001:4860:4860::8888#dns.google

Link 2 (enp0s31f6)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no

Does my ethernet connection need to be a default route? Thanks!

ahepp · 2025-10-28 16:50:02

My experience has been that systemd-networkd will respect the DHCP lease options regarding the gateway. You can tell it not to, or set up a static route, but the preferred way to fix this would probably be making sure the dhcp server is sending a gateway.

seth · 2025-10-28 18:57:11

Don't you have a working internet connection?

ip a; ip r
ping -c1 google.com

davidbryant · 2025-10-28 23:17:40

After a lot of screwing around I do indeed have a working network connection. Thank you very much!

Arch Linux

#1 2025-10-28 13:39:06

[SOLVED] New install can't reach network

#2 2025-10-28 13:44:22

Re: [SOLVED] New install can't reach network

#3 2025-10-28 14:38:24

Re: [SOLVED] New install can't reach network

#4 2025-10-28 14:52:56

Re: [SOLVED] New install can't reach network

#5 2025-10-28 14:57:39

Re: [SOLVED] New install can't reach network

#6 2025-10-28 15:08:02

Re: [SOLVED] New install can't reach network

#7 2025-10-28 15:20:24

Re: [SOLVED] New install can't reach network

#8 2025-10-28 15:24:35

Re: [SOLVED] New install can't reach network

#9 2025-10-28 15:33:08

Re: [SOLVED] New install can't reach network

#10 2025-10-28 16:13:51

Re: [SOLVED] New install can't reach network

#11 2025-10-28 16:50:02

Re: [SOLVED] New install can't reach network

#12 2025-10-28 18:57:11

Re: [SOLVED] New install can't reach network

#13 2025-10-28 23:17:40

Re: [SOLVED] New install can't reach network

Board footer