[systemd-networkd] Interfaces do not automatically start

[elmo]

Hello,

I recently installed Arch on my Odroid U3.
Everything is ok, systemd-networkd, dhcpd, hostapd, dnsmasq...

But if I stop and disables dhcpcd, with each restart I need to start interfaces manually.
And only sometimes systemd-networkd!

Is it normal to require active dhcpcd while my three interfaces are fixed IP?

Thanks

[WarheadsSE]

what are your configs?

[elmo]

/etc/systemd/network/LAN.network$this->bbcode_second_pass_code('', '
[Match]
Name=LAN

[Network]
IPForward=ipv4
DNS=127.0.0.1

[Address]
Address=10.10.10.1/24

[Route]
Gateway=192.168.15.1')/etc/systemd/network/WAN.network$this->bbcode_second_pass_code('', '[Match]
Name=WAN

[Network]
IPForward=ipv4
DNS=127.0.0.1

[Address]
Address=192.168.15.2/24

[Route]
Gateway=192.168.15.1')/etc/systemd/network/WIFI.network$this->bbcode_second_pass_code('', '[Match]
Name=WIFI

[Network]
IPForward=ipv4
DNS=127.0.0.1

[Address]
Address=172.16.0.1/24

[Route]
Gateway=192.168.15.1')

[WarheadsSE]

Name in [Match] does not do what I think you think it does.

[elmo]

A whitespace-separated list of shell-style globs matching the device name, as exposed by the udev property "INTERFACE".

I already tried using MACAddress instead.

/etc/udev/rules.d/10-network.rules$this->bbcode_second_pass_code('', 'SUBSYSTEM=="net", ATTRS{address}=="4e:af:28:5f:e6:d0", NAME="LAN"
SUBSYSTEM=="net", ATTRS{address}=="00:e0:4c:36:13:84", NAME="WAN"
SUBSYSTEM=="net", ATTRS{address}=="00:25:22:4e:06:6c", NAME="WIFI"')ip addr$this->bbcode_second_pass_code('', '2: WAN: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 00:e0:4c:36:13:84 brd ff:ff:ff:ff:ff:ff
inet 192.168.15.2/24 brd 192.168.15.255 scope global WAN
inet6 fe80::2e0:4cff:fe36:1384/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::51f7:74da:2de7:955/64 scope link
valid_lft forever preferred_lft forever
3: LAN: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 4e:af:28:5f:e6:d0 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.1/24 brd 10.10.10.255 scope global LAN
inet6 fe80::4caf:28ff:fe5f:e6d0/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::b79f:b50d:567f:8275/64 scope link
valid_lft forever preferred_lft forever
4: WIFI: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:25:22:4e:06:6c brd ff:ff:ff:ff:ff:ff
inet 172.16.0.1/24 brd 172.16.0.255 scope global WIFI
inet6 fe80::4110:5625:b191:1164/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::225:22ff:fe4e:66c/64 scope link
valid_lft forever preferred_lft forever
')Did I misunderstand? If so can you explain?

[WarheadsSE]

Ah, so you have fine that. Okay. Perhaps a race condition then on the renaming. Unlikely but possible. On a fresh boot, are there any interesting logs from systemd-networkd?

[elmo]

Sorry for the delay, my Wimax modem dropped me.

Without renaming: (so with /etc/systemd/network/eth0, eth1 and wlan0.network) $this->bbcode_second_pass_code('', 'août 29 10:28:56 jeep systemd[1]: Starting Network Service...
août 29 10:28:56 jeep systemd-networkd[249]: Enumeration completed
août 29 10:28:56 jeep systemd-networkd[249]: wlan0: wlan0 : could not bring up interface: Operation not supported
août 29 10:28:56 jeep systemd-networkd[249]: eth1: eth1 : could not bring up interface: Operation not supported
août 29 10:28:56 jeep systemd-networkd[249]: eth0: eth0 : could not bring up interface: Operation not supported
août 29 10:28:56 jeep systemd-networkd[249]: wlan0: wlan0 : could not set route: Network is unreachable
août 29 10:28:56 jeep systemd-networkd[249]: wlan0: Configured
août 29 10:28:56 jeep systemd-networkd[249]: eth1: eth1 : could not set route: Network is unreachable
août 29 10:28:56 jeep systemd-networkd[249]: eth1: Configured
août 29 10:28:56 jeep systemd-networkd[249]: eth0: eth0 : could not set route: Network is unreachable
août 29 10:28:56 jeep systemd-networkd[249]: eth0: Configured
août 29 10:28:56 jeep systemd[1]: Started Network Service.')

Renaming:$this->bbcode_second_pass_code('', 'août 29 10:30:19 jeep systemd[1]: Starting Network Service...
août 29 10:30:19 jeep systemd-networkd[269]: Enumeration completed
août 29 10:30:19 jeep systemd-networkd[269]: WAN: Renamed to eth0
août 29 10:30:19 jeep systemd-networkd[269]: LAN: Renamed to eth1
août 29 10:30:19 jeep systemd-networkd[269]: eth1: Renamed to LAN
août 29 10:30:19 jeep systemd-networkd[269]: WIFI: Renamed to wlan0
août 29 10:30:19 jeep systemd-networkd[269]: eth0: Renamed to WAN
août 29 10:30:19 jeep systemd-networkd[269]: wlan0: Renamed to WIFI
août 29 10:30:19 jeep systemd-networkd[269]: WIFI: WIFI : could not bring up interface: Operation not supported
août 29 10:30:19 jeep systemd-networkd[269]: LAN: LAN : could not bring up interface: Operation not supported
août 29 10:30:19 jeep systemd-networkd[269]: WAN: WAN : could not bring up interface: Operation not supported
août 29 10:30:19 jeep systemd-networkd[269]: WIFI: WIFI : could not set route: Network is unreachable
août 29 10:30:19 jeep systemd-networkd[269]: WIFI: Configured
août 29 10:30:19 jeep systemd-networkd[269]: LAN: LAN : could not set route: Network is unreachable
août 29 10:30:19 jeep systemd-networkd[269]: LAN: Configured
août 29 10:30:19 jeep systemd-networkd[269]: WAN: WAN : could not set route: Network is unreachable
août 29 10:30:19 jeep systemd-networkd[269]: WAN: Configured
août 29 10:30:19 jeep systemd[1]: Started Network Service.
août 29 10:30:25 jeep systemd-networkd[269]: WIFI: Gained carrier')
In either case this does not work if dhcpcd is inactive.

With dhcpcd activated:$this->bbcode_second_pass_code('', 'août 29 10:32:14 jeep systemd[1]: Starting Network Service...
août 29 10:32:15 jeep systemd-networkd[269]: Enumeration completed
août 29 10:32:15 jeep systemd-networkd[269]: WAN: Renamed to eth0
août 29 10:32:15 jeep systemd-networkd[269]: eth0: Lost carrier
août 29 10:32:15 jeep systemd-networkd[269]: LAN: Renamed to eth1
août 29 10:32:15 jeep systemd-networkd[269]: eth1: Renamed to LAN
août 29 10:32:15 jeep systemd-networkd[269]: eth0: Renamed to WAN
août 29 10:32:15 jeep systemd-networkd[269]: WIFI: Renamed to wlan0
août 29 10:32:15 jeep systemd-networkd[269]: wlan0: Renamed to WIFI
août 29 10:32:15 jeep systemd-networkd[269]: WAN: Gained carrier
août 29 10:32:15 jeep systemd[1]: Started Network Service.
août 29 10:32:15 jeep systemd-networkd[269]: WIFI: WIFI : could not set route: Network is unreachable
août 29 10:32:15 jeep systemd-networkd[269]: WIFI: Configured
août 29 10:32:15 jeep systemd-networkd[269]: LAN: LAN : could not set route: Network is unreachable
août 29 10:32:15 jeep systemd-networkd[269]: LAN: Configured
août 29 10:32:15 jeep systemd-networkd[269]: WAN: Configured
août 29 10:32:16 jeep systemd-networkd[269]: LAN: Gained carrier
août 29 10:32:21 jeep systemd-networkd[269]: WIFI: Gained carrier')

But you're probably right, there is a problem with the renaming.
I do not understand why systemd renames in both directions.

[elmo]

Solved by disabling ipv6 (kernel parameter)