Open sbharvey opened 2 months ago
Note this issue appears to have been fixed at Clear Linux build 42410. I update ever one to 2 week intervals so I cannot be sure what exact build number fixed the issue. All I can report is that behavior is more expected, The changes to systemd-networkd-wait-online.service work as expected. The effect can be seen with system-analyze command as shown systemd-analyze plot >bootup.svg. bootup.svg can be viewed with eog or firefox. The timeline of the bootup can be observed.
[Unit]
Description=Wait for Network to be Configured
Documentation=man:systemd-networkd-wait-online.service(8)
ConditionCapability=CAP_NET_ADMIN
DefaultDependencies=no
Conflicts=shutdown.target
BindsTo=systemd-networkd.service
After=systemd-networkd.service
Before=network-online.target shutdown.target
[Service]
Type=oneshot
#ExecStart=/usr/lib/systemd/systemd-networkd-wait-online --any
ExecStart=/usr/lib/systemd/systemd-networkd-wait-online --interface=enp5s0 --interface=enp6s0 --interface=enp9s0 --ipv4
RemainAfterExit=yes
[Install] WantedBy=network-online.target
Below are the status of iptables and systemd-networkd-wait-online.service are shown:
systemctl status systemd-networkd-wait-online.service
● systemd-networkd-wait-online.service - Wait for Network to be Configured
Loaded: loaded (/etc/systemd/system/systemd-networkd-wait-online.service; enabled; preset: disabled)
Active: active (exited) since Fri 2024-09-27 15:50:19 PDT; 2h 10min ago
Docs: man:systemd-networkd-wait-online.service(8)
Main PID: 815 (code=exited, status=0/SUCCESS)
Sep 27 15:50:13 netserver03 systemd[1]: Starting systemd-networkd-wait-online.service...
Sep 27 15:50:19 netserver03 systemd[1]: Finished systemd-networkd-wait-online.service.
systemctl status iptables-restore.service
● iptables-restore.service - Restore IPv4 firewall settings across reboots
Loaded: loaded (/etc/systemd/system/iptables-restore.service; enabled; preset: disabled)
Active: active (exited) since Fri 2024-09-27 15:50:13 PDT; 2h 10min ago
Main PID: 677 (code=exited, status=0/SUCCESS)
Sep 27 15:50:13 netserver03 systemd[1]: Starting iptables-restore.service...
Sep 27 15:50:13 netserver03 systemd[1]: Finished iptables-restore.service.
In the process of updating my system from Clear Linux 42050 to 42170. I experienced network configuration issue. I have been using systemd-networkd.service and iptables for nearly 2 years now. But with this latest update it is failing, iptables is not configuring any rules. I configured my desired ethernet interface routing by using the files in /etc/systemd/network. I have NetworkManager.service turned off I have looked into the problem and it seems that something has changed between Clear Linux build 42050 and 42170 that affects systemd boot timing, as a result network routing comes up broken.
I use systemd-netword.service to configure my network.
I configure iptable with the file:
When the system boots this what the status of systemd-networkd.service shows:
Failed systed-networkd-wait-online.service it did not run
The only way to fix the network routing is to run an alias I created after the server has booted in a terminal shell.
When systemd-netword.service was restarted manually below is the expected status.
The networkd-systemd.service defines the conditions for restart if by my understanding, references systemd-networkd-wait-online.service, None of this seems to be working. I have have made changes to systemd-networkd-wait-online to define a valid state for my my network. If I test the unit systemd-networkd-wait-online these changes work by itself. However the changes to systemd-networkd-wait-online did not work when rebooting from a power cycle.
Here is the unit file definition for systemd-netword.service:
Other details my server hardware and relevant software versions: