On 9/5/21 12:46 AM, Tamer Higazi wrote: > Hi people, > > After upgrading my gentoo box i see a new behavior, that my machine > after boot doen't configure my network. My network is configured through > systemd-network, > > Only if I manually after login execute: "systemctl restart > systemd-network" it gets configured. > Can somebody tell me why this is the case and how to fix it ? > > systemctl Logs: > > after start: > > ● systemd-networkd.service - Network Configuration > Loaded: loaded (/lib/systemd/system/systemd-networkd.service; > enabled; vendor preset: enabled) > Active: active (running) since Sat 2021-09-04 08:49:48 CEST; 1min > 4s ago > TriggeredBy: ● systemd-networkd.socket > Docs: man:systemd-networkd.service(8) > Main PID: 957 (systemd-network) > Status: "Processing requests..." > Tasks: 1 (limit: 19136) > Memory: 2.3M > CGroup: /system.slice/systemd-networkd.service > └─957 /lib/systemd/systemd-networkd > > Sep 04 08:49:48 tux systemd[1]: Starting Network Configuration... > Sep 04 08:49:48 tux systemd-networkd[957]: lo: Link UP > Sep 04 08:49:48 tux systemd-networkd[957]: lo: Gained carrier > Sep 04 08:49:48 tux systemd-networkd[957]: Enumeration completed > Sep 04 08:49:48 tux systemd[1]: Started Network Configuration. > Sep 04 08:49:49 tux systemd-networkd[957]: eth0: Interface name change > detected, renamed to enp6s0. > Sep 04 08:49:49 tux systemd-networkd[957]: eth1: Interface name change > detected, renamed to enp7s0. > > after manually restart (systemctl restart systemd-networkd): > > > ● systemd-networkd.service - Network Configuration > Loaded: loaded (/lib/systemd/system/systemd-networkd.service; > enabled; vendor preset: enabled) > Active: active (running) since Sat 2021-09-04 08:51:47 CEST; 13s ago > TriggeredBy: ● systemd-networkd.socket > Docs: man:systemd-networkd.service(8) > Main PID: 1167 (systemd-network) > Status: "Processing requests..." > Tasks: 1 (limit: 19136) > Memory: 1.0M > CGroup: /system.slice/systemd-networkd.service > └─1167 /lib/systemd/systemd-networkd > > Sep 04 08:51:47 tux systemd[1]: Starting Network Configuration... > Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Link UP > Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Gained carrier > Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Link UP > Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Gained carrier > Sep 04 08:51:47 tux systemd-networkd[1167]: Enumeration completed > Sep 04 08:51:47 tux systemd[1]: Started Network Configuration. > Sep 04 08:51:48 tux systemd-networkd[1167]: enp6s0: Gained IPv6LL
What does your networkd configuration look like? One thing that stands out from your example logs is that the first networkd startup seems to occur _before_ udev assigns predictable network interface names (eth0 -> enp6s0), I'm wondering if that's why it works after you later restart the daemon. I'm not a systemd expert -- perhaps there is a dependency ordering issue here? https://github.com/systemd/systemd/issues/7293
