F5F Stay Refreshed Software Operating Systems Error: Network not reachable on Arch Linux system.

Error: Network not reachable on Arch Linux system.

Error: Network not reachable on Arch Linux system.

Pages (2): Previous 1 2
K
kkomeister
Junior Member
6
12-19-2025, 08:54 AM
#11
Arch typically includes a networking guide in the manual, but I often overlook it. I usually check the handbook for setting up networking—perhaps enabling netctl with netctl enable and then activating your network card via systemctl. For GNOME or KDE, consider using Network Manager instead of netctl. If you're booting from a live CD, you can reinstall Arch without formatting and mount the required files as if installing normally. Once installed, enable Network Manager with systemctl, and ensure GDM or SDDM is active during boot by running systemctl enable.
K
kkomeister
12-19-2025, 08:54 AM #11

Arch typically includes a networking guide in the manual, but I often overlook it. I usually check the handbook for setting up networking—perhaps enabling netctl with netctl enable and then activating your network card via systemctl. For GNOME or KDE, consider using Network Manager instead of netctl. If you're booting from a live CD, you can reinstall Arch without formatting and mount the required files as if installing normally. Once installed, enable Network Manager with systemctl, and ensure GDM or SDDM is active during boot by running systemctl enable.

W
Wumty
Member
195
01-10-2026, 05:27 AM
#12
You're likely to discover what you require at this location: https://wiki.archlinux.org/index.php/systemd-networkd
W
Wumty
01-10-2026, 05:27 AM #12

You're likely to discover what you require at this location: https://wiki.archlinux.org/index.php/systemd-networkd

G
Goathead
Junior Member
4
01-23-2026, 06:20 AM
#13
Most DEs include a network manager to handle connectivity. If you lack a DE and remain on the same interface without disconnecting your device, ensure DHCP is running on that port. Start dhcpcd@enp3s0 with sudo systemctl once booted. For better control, use nmcli or nm-applet instead of ifconfig, which is part of net-tools and should be avoided. When using Ethernet only, the above steps suffice. If you move or use your device offline, install network-manager and manage connections via its tools.
G
Goathead
01-23-2026, 06:20 AM #13

Most DEs include a network manager to handle connectivity. If you lack a DE and remain on the same interface without disconnecting your device, ensure DHCP is running on that port. Start dhcpcd@enp3s0 with sudo systemctl once booted. For better control, use nmcli or nm-applet instead of ifconfig, which is part of net-tools and should be avoided. When using Ethernet only, the above steps suffice. If you move or use your device offline, install network-manager and manage connections via its tools.

H
Haylie
Junior Member
23
01-31-2026, 05:09 AM
#14
It seems the DHCP service wasn't activated at startup. Fix it by running sudo systemctl enable dhcpcd. For a smoother setup, you can also start it without rebooting using sudo dhcpcd @101dmrs. This command works on a single interface and helps automatically request an IP address, though enabling it generally ensures consistent behavior across all available networks.
H
Haylie
01-31-2026, 05:09 AM #14

It seems the DHCP service wasn't activated at startup. Fix it by running sudo systemctl enable dhcpcd. For a smoother setup, you can also start it without rebooting using sudo dhcpcd @101dmrs. This command works on a single interface and helps automatically request an IP address, though enabling it generally ensures consistent behavior across all available networks.

Pages (2): Previous 1 2