| 1 |
On 9/5/21 12:46 AM, Tamer Higazi wrote: |
| 2 |
> Hi people, |
| 3 |
> |
| 4 |
> After upgrading my gentoo box i see a new behavior, that my machine |
| 5 |
> after boot doen't configure my network. My network is configured through |
| 6 |
> systemd-network, |
| 7 |
> |
| 8 |
> Only if I manually after login execute: "systemctl restart |
| 9 |
> systemd-network" it gets configured. |
| 10 |
> Can somebody tell me why this is the case and how to fix it ? |
| 11 |
> |
| 12 |
> systemctl Logs: |
| 13 |
> |
| 14 |
> after start: |
| 15 |
> |
| 16 |
> ● systemd-networkd.service - Network Configuration |
| 17 |
> Loaded: loaded (/lib/systemd/system/systemd-networkd.service; |
| 18 |
> enabled; vendor preset: enabled) |
| 19 |
> Active: active (running) since Sat 2021-09-04 08:49:48 CEST; 1min |
| 20 |
> 4s ago |
| 21 |
> TriggeredBy: ● systemd-networkd.socket |
| 22 |
> Docs: man:systemd-networkd.service(8) |
| 23 |
> Main PID: 957 (systemd-network) |
| 24 |
> Status: "Processing requests..." |
| 25 |
> Tasks: 1 (limit: 19136) |
| 26 |
> Memory: 2.3M |
| 27 |
> CGroup: /system.slice/systemd-networkd.service |
| 28 |
> └─957 /lib/systemd/systemd-networkd |
| 29 |
> |
| 30 |
> Sep 04 08:49:48 tux systemd[1]: Starting Network Configuration... |
| 31 |
> Sep 04 08:49:48 tux systemd-networkd[957]: lo: Link UP |
| 32 |
> Sep 04 08:49:48 tux systemd-networkd[957]: lo: Gained carrier |
| 33 |
> Sep 04 08:49:48 tux systemd-networkd[957]: Enumeration completed |
| 34 |
> Sep 04 08:49:48 tux systemd[1]: Started Network Configuration. |
| 35 |
> Sep 04 08:49:49 tux systemd-networkd[957]: eth0: Interface name change |
| 36 |
> detected, renamed to enp6s0. |
| 37 |
> Sep 04 08:49:49 tux systemd-networkd[957]: eth1: Interface name change |
| 38 |
> detected, renamed to enp7s0. |
| 39 |
> |
| 40 |
> after manually restart (systemctl restart systemd-networkd): |
| 41 |
> |
| 42 |
> |
| 43 |
> ● systemd-networkd.service - Network Configuration |
| 44 |
> Loaded: loaded (/lib/systemd/system/systemd-networkd.service; |
| 45 |
> enabled; vendor preset: enabled) |
| 46 |
> Active: active (running) since Sat 2021-09-04 08:51:47 CEST; 13s ago |
| 47 |
> TriggeredBy: ● systemd-networkd.socket |
| 48 |
> Docs: man:systemd-networkd.service(8) |
| 49 |
> Main PID: 1167 (systemd-network) |
| 50 |
> Status: "Processing requests..." |
| 51 |
> Tasks: 1 (limit: 19136) |
| 52 |
> Memory: 1.0M |
| 53 |
> CGroup: /system.slice/systemd-networkd.service |
| 54 |
> └─1167 /lib/systemd/systemd-networkd |
| 55 |
> |
| 56 |
> Sep 04 08:51:47 tux systemd[1]: Starting Network Configuration... |
| 57 |
> Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Link UP |
| 58 |
> Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Gained carrier |
| 59 |
> Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Link UP |
| 60 |
> Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Gained carrier |
| 61 |
> Sep 04 08:51:47 tux systemd-networkd[1167]: Enumeration completed |
| 62 |
> Sep 04 08:51:47 tux systemd[1]: Started Network Configuration. |
| 63 |
> Sep 04 08:51:48 tux systemd-networkd[1167]: enp6s0: Gained IPv6LL |
| 64 |
|
| 65 |
What does your networkd configuration look like? One thing that stands |
| 66 |
out from your example logs is that the first networkd startup seems to |
| 67 |
occur _before_ udev assigns predictable network interface names (eth0 -> |
| 68 |
enp6s0), I'm wondering if that's why it works after you later restart |
| 69 |
the daemon. |
| 70 |
|
| 71 |
I'm not a systemd expert -- perhaps there is a dependency ordering issue |
| 72 |
here? https://github.com/systemd/systemd/issues/7293 |
Archives