Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)

[Tamer Higazi]

Dear Dr. Valdés,

/etc/systemd/network/20-wirded.network:

[Match]
Name=enp6s0

[Network]
Address=192.168.0.50/24
Gateway=192.168.0.1

DNS=192.168.0.1

for enp7s0 there is no other network file.

/etc/systemd/networkd.conf:

[Network]
#SpeedMeter=no
#SpeedMeterIntervalSec=10sec
#ManageForeignRoutingPolicyRules=yes
#ManageForeignRoutes=yes
#RouteTable=

[DHCPv4]
#DUIDType=vendor
#DUIDRawData=

[DHCPv6]
#DUIDType=vendor
#DUIDRawData=

remained untouched.


I think with THIS systemd version, the whole problem is, that the 
configuration will be done before the devices are made and renamed to 
enp6s0 and enp7s0.

The problem is, how to solve it ....

Because when I don't do anything by hand, nothing occurs.
I believe that the configuration is done before everything is full 
available.
(devices created and renamed ....)

I think I found the solution to my problem, but don't know how to 
implement it.
systemd-udev-settle.service

systemctl list-dependencies --after systemd-networkd:

systemd-networkd.service
● ├─-.mount
● ├─system.slice
● ├─systemd-journald.socket
● ├─systemd-networkd.socket
● ├─systemd-sysctl.service
○ ├─systemd-sysusers.service
○ ├─systemd-udev-settle.service
● ├─systemd-udevd.service
○ └─network-pre.target

Any further ideas I am thankful.


best, Tamer Higazi

references: https://github.com/systemd/systemd/issues/7293

Am 9/5/21 um 9:51 PM schrieb Canek Peláez Valdés:
> On Sun, Sep 5, 2021 at 1:36 PM Tamer Higazi <th982a@××××××××××.com
> <mailto:th982a@××××××××××.com>> wrote:
> [...]
>
>     × systemd-networkd-wait-online.service - Wait for Network to be
>     Configured
>           Loaded: loaded
>     (/lib/systemd/system/systemd-networkd-wait-online.service; enabled;
>     vendor preset: disabled)
>           Active: failed (Result: exit-code) since Sun 2021-09-05
>     20:22:19
>     CEST; 11min ago
>             Docs: man:systemd-networkd-wait-online.service(8)
>         Main PID: 984 (code=exited, status=1/FAILURE)
>
>
>     Sep 05 20:20:18 tux systemd[1]: Starting Wait for Network to be
>     Configured...
>     Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout
>     occurred
>     while waiting for network connectivity.
>     Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service:
>     Main process exited, code=exited, status=1/FAILURE
>     Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service:
>     Failed with result 'exit-code'.
>     Sep 05 20:22:19 tux systemd[1]: Failed to start Wait for Network
>     to be
>     Configured.
>
>
> There's your problem: systemd-networkd-wait-online.service is timing out:
>
> Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout
> occurred while waiting for network connectivity.
>
> The systemd-networkd-wait-online service runs relatively early and
> waits for *ALL* interfaces it is aware of to be fully configured or
> failed[1], so it probably one of your interfaces is taking too long to
> be ready. Between timing out and you restarting
> systemd-networkd.service, the interface reaches the ready state (or
> fails), and systemd-networkd-wait-online.service doesn't time out anymore.
>
> By your logs, you have two ethernet interfaces: enp6s0 and enp7s0, the
> latter not in use. Do you .network files in /etc/systemd/network/ or
> /run/systemd/network/? Any changes (uncommented lines) in
> /etc/systemd/networkd.conf?
>
> Regards.
>
> [1]
> https://man7.org/linux/man-pages/man8/systemd-networkd-wait-online.8.html
> <https://man7.org/linux/man-pages/man8/systemd-networkd-wait-online.8.html>
> --
> Dr. Canek Peláez Valdés
> Profesor de Carrera Asociado C
> Departamento de Matemáticas
> Facultad de Ciencias
> Universidad Nacional Autónoma de México