Network Management

nikolaus · 2023-12-08 08:08:56

Hello everyone

I have two open points with my current networking (new installed system).
a) does a network manager like netctl always make sense or just under circumstance and does it conflict with systemd-networkd service (as it requires to have no other network service running)?
b) my network device (ethernet cable) is always DOWN after system start. 'ip link set <device> on' only works for a session. Is that normal and is there a way to permanently make it UP at start?

- nikolaus

seth · 2023-12-08 08:23:38

a) depends on whether you want to dynamically change the setup during runtime and yes, they're gonna conflict. You've to pick one service and disable all others (technically "per NIC", but even if you figured that would make any sense, I'd postpone such efforts util you're a bit more experienced)
b) what does "ip a" actually say? The relevant entry for "ip link set <device> up" is in the <brackets>, the "state DOWN" later on means there's no immediate usage

If you've only a single wired NIC, just dhcpcd is gonna suffice for your setup.

nikolaus · 2023-12-08 10:13:10

Ok .. thanks for your answer!

After login "ip a" has the following result.

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: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 40:16:7e:a8:03:2c brd ff:ff:ff:ff:ff:ff

After activation as mentioned is has this result:

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: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 40:16:7e:a8:03:2c brd ff:ff:ff:ff:ff:ff
    inet6 2003:c6:ef11:4f60:4216:7eff:fea8:32c/64 scope global dynamic mngtmpaddr proto kernel_ra 
       valid_lft 604769sec preferred_lft 86369sec
    inet6 fe80::4216:7eff:fea8:32c/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever

But as I mentioned, activation has not lasting effect over sessions.

seth · 2023-12-08 12:39:25

"of course not", what are you currently using to configure the network?

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

nikolaus · 2023-12-09 06:36:29

dbus-org.freedesktop.network1.service    | system
dbus-org.freedesktop.resolve1.service    | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-networkd-wait-online.service     | network-online.target.wants
systemd-network-generator.service        | sysinit.target.wants
systemd-resolved.service                 | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants

This is the situation after I activated the device manually with ip.
I'm still looking for information on what to do to configure the network setup. The documents are not quite practical.

Last edited by nikolaus (2023-12-09 06:39:36)

seth · 2023-12-09 07:57:14

https://wiki.archlinux.org/title/Networ … management
https://wiki.archlinux.org/title/Networ … #Automatic
You're currently using networkd, https://wiki.archlinux.org/title/System … using_DHCP

seth wrote:

If you've only a single wired NIC, just dhcpcd is gonna suffice for your setup.

And in that case disable systemd-networkd.

Arch Linux

#1 2023-12-08 08:08:56

Network Management

#2 2023-12-08 08:23:38

Re: Network Management

#3 2023-12-08 10:13:10

Re: Network Management

#4 2023-12-08 12:39:25

Re: Network Management

#5 2023-12-09 06:36:29

Re: Network Management

#6 2023-12-09 07:57:14

Re: Network Management

Board footer