Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

frr.service starts before networking is fully booted and breaks set src for static routes if source IP is on an interface not configured #18230

Open
2 tasks done
EasyNetDev opened this issue Feb 22, 2025 · 1 comment
Open
2 tasks done

frr.service starts before networking is fully booted and breaks set src for static routes if source IP is on an interface not configured #18230

EasyNetDev opened this issue Feb 22, 2025 · 1 comment
Labels
triage Needs further investigation

Comments

@EasyNetDev
Copy link
Contributor

EasyNetDev commented Feb 22, 2025 •
edited
Loading

Description

Hello,

I'm noticing a very weird situation with frr.service and networking.service.
There is a reason why frr.service should boot before the networking.service and before network.target which is triggered by networking.service?

/usr/lib/systemd/system/frr.service:

[Unit]
Description=FRRouting
Documentation=https://frrouting.readthedocs.io/en/latest/setup.html
Wants=network.target
After=network-pre.target systemd-sysctl.service
Before=network.target
OnFailure=heartbeat-failed@%n

[Service]
Nice=-5
Type=forking
NotifyAccess=all
StartLimitInterval=3m
StartLimitBurst=3
TimeoutSec=2m
WatchdogSec=60s
RestartSec=5
Restart=always
LimitNOFILE=1024
PIDFile=/var/run/frr/watchfrr.pid
ExecStart=/usr/lib/frr/frrinit.sh start
ExecStop=/usr/lib/frr/frrinit.sh stop
ExecReload=/usr/lib/frr/frrinit.sh reload

[Install]
WantedBy=multi-user.target

My case: I have a lot of interfaces (67 of them) that needs to be prepared, like lo0, lo1 .. etc done via dummy.
My configuration has a default route in GRT which is using set src. And each time I'm rebooting the router, this default route is marked as r - rejected.

After troubleshooting the kernel messages using debug on FRR I found this:

2025-02-21T21:42:42.985742+02:00 R02 zebra[6074]: [YXPF5-B2CE0] netlink_route_multipath_msg_encode: RTM_NEWROUTE 0.0.0.0/0 vrf 0(254)
2025-02-21T21:42:42.985784+02:00 R02 zebra[6074]: [J87BH-XW5PP] netlink_route_multipath_msg_encode: 0.0.0.0/0 nhg_id is 11
2025-02-21T21:42:42.985838+02:00 R02 zebra[6074]: [RVH9G-QKM3J] netlink_route_multipath_msg_encode: 0.0.0.0/0 set src 89.X.X.2
2025-02-21T21:42:42.985877+02:00 R02 zebra[6074]: [HYEHE-CQZ9G] nl_batch_send: netlink-dp (NS 0), batch size=144, msg cnt=2
2025-02-21T21:42:42.985906+02:00 R02 zebra[6074]: [TJ327-ET8HE] netlink_send_msg: >> netlink message dump [sent]
2025-02-21T21:42:42.986281+02:00 R02 zebra[6074]: [JAS4D-NCWGP] nlmsghdr [len=60 type=(24) NEWROUTE flags=(0x0501) {REQUEST,DUMP,(ROOT|REPLACE|CAPPED),(ATOMIC|CREATE)} seq=214 pid=2492117586]
2025-02-21T21:42:42.986322+02:00 R02 zebra[6074]: [GCEGC-W8YBF]   rtmsg [family=(2) AF_INET dstlen=0 srclen=0 tos=0 table=254 protocol=(196) UNKNOWN scope=(0) UNIVERSE type=(1) UNICAST flags=0x0000 {}]
2025-02-21T21:42:42.986364+02:00 R02 zebra[6074]: [KFBSR-XYJV1]     rta [len=8 (payload=4) type=(1) DST]
2025-02-21T21:42:42.986404+02:00 R02 zebra[6074]: [M8QV4-KY9C0]       0.0.0.0
2025-02-21T21:42:42.986445+02:00 R02 zebra[6074]: [KFBSR-XYJV1]     rta [len=8 (payload=4) type=(6) PRIORITY]
2025-02-21T21:42:42.986486+02:00 R02 zebra[6074]: [Z4E9C-GD9EP]       20
2025-02-21T21:42:42.986527+02:00 R02 zebra[6074]: [KFBSR-XYJV1]     rta [len=8 (payload=4) type=(30) NH_ID]
2025-02-21T21:42:42.986568+02:00 R02 zebra[6074]: [Z4E9C-GD9EP]       11
2025-02-21T21:42:42.986625+02:00 R02 zebra[6074]: [KFBSR-XYJV1]     rta [len=8 (payload=4) type=(7) PREFSRC]
2025-02-21T21:42:42.986671+02:00 R02 zebra[6074]: [M8QV4-KY9C0]       89.X.X.2
2025-02-21T21:42:42.986728+02:00 R02 zebra[6074]: [V8KNF-8EXH8] netlink_recv_msg: << netlink message dump [recv]
2025-02-21T21:42:42.986771+02:00 R02 zebra[6074]: [JAS4D-NCWGP] nlmsghdr [len=64 type=(2) ERROR flags=(0x0300) {DUMP,(ROOT|REPLACE|CAPPED),(MATCH|EXCLUDE|ACK_TLVS)} seq=214 pid=2492117586]
2025-02-21T21:42:42.986812+02:00 R02 zebra[6074]: [KWP1C-6CSXF]   nlmsgerr [error=(-22) Invalid argument]
2025-02-21T21:42:42.986853+02:00 R02 zebra[6074]: [HSYZM-HV7HF] Extended Error: Invalid prefsrc address
2025-02-21T21:42:42.986895+02:00 R02 zebra[6074]: [WVJCK-PPMGD]
[EC 4043309093] netlink-dp (NS 0) error: Invalid argument, type=RTM_NEWROUTE(24), seq=214, pid=2492117586
2025-02-21T21:42:42.986937+02:00 R02 zebra[6074]: [QTT8V-3ZQ34] nl_batch_read_resp: netlink error message seq=214
2025-02-21T21:42:42.986980+02:00 R02 zebra[6074]: [VYKYC-709DP] default(0:254):0.0.0.0/0: Route install failed
2025-02-21T21:42:43.186948+02:00 R02 zebra[6074]: [V8KNF-8EXH8] netlink_recv_msg: << netlink message dump [recv]

Trying to find out why this happens only on boot, I've did a trace of ifupdown-ng on boot and I've compared the times with FRRouting service.

And this is the chain of events on booting:

2025-02-22T01:34:42.243481+02:00 R02 frrinit.sh[6807]: [6807|staticd] sending configuration
2025-02-22T01:34:59.396812+02:00 R02 networking[5561]: ifup: acquiring lock on /run/ifstate.lo0.lock
2025-02-22T01:34:59.396859+02:00 R02 networking[5561]: ifup: changing state of interface lo0 to 'up'
2025-02-22T01:34:59.396896+02:00 R02 networking[5561]: ifupdown: lo0: attempting to run link executor for phase create
2025-02-22T01:34:59.398237+02:00 R02 networking[10237]: + [ dummy = dummy ]
2025-02-22T01:34:59.398284+02:00 R02 networking[10237]: + [ ! -d /sys/module/dummy ]
2025-02-22T01:34:59.398320+02:00 R02 networking[10237]: + [ -z  ]
2025-02-22T01:34:59.398369+02:00 R02 networking[10237]: + [ -d /sys/class/net/lo0 ]
2025-02-22T01:34:59.398405+02:00 R02 networking[10237]: + ip link add lo0 type dummy
2025-02-22T01:34:59.399855+02:00 R02 networking[5561]: ifupdown: lo0: attempting to run multi-loopback executor for phase create
2025-02-22T01:34:59.401118+02:00 R02 networking[10240]: + [ dummy = multi-loopback ]
2025-02-22T01:34:59.401237+02:00 R02 networking[5561]: ifupdown: lo0: attempting to run link executor for phase pre-up
2025-02-22T01:34:59.402437+02:00 R02 networking[5561]: ifupdown: lo0: attempting to run multi-loopback executor for phase pre-up
2025-02-22T01:34:59.405298+02:00 R02 networking[5561]: ifupdown: lo0: attempting to run link executor for phase up
2025-02-22T01:34:59.406410+02:00 R02 networking[10252]: + IF_LINK_OPTIONS=
2025-02-22T01:34:59.406442+02:00 R02 networking[10252]: + [ -n  ]
2025-02-22T01:34:59.406479+02:00 R02 networking[10252]: + [ -n  ]
2025-02-22T01:34:59.406500+02:00 R02 networking[10252]: + ip link set up dev lo0
2025-02-22T01:34:59.407524+02:00 R02 networking[10252]: + [  ]
2025-02-22T01:34:59.407724+02:00 R02 networking[5561]: ifupdown: lo0: attempting to run multi-loopback executor for phase up
2025-02-22T01:34:59.409032+02:00 R02 networking[10255]: + ip link set up dev lo0
2025-02-22T01:34:59.410145+02:00 R02 networking[10255]: + [  ]
2025-02-22T01:34:59.424585+02:00 R02 networking[5561]: ifupdown: lo0: attempting to run link executor for phase post-up
2025-02-22T01:34:59.425936+02:00 R02 networking[5561]: ifupdown: lo0: attempting to run multi-loopback executor for phase post-up
2025-02-22T01:34:59.692430+02:00 R02 systemd[1]: Reached target network.target - Network.

If the interface lo0 is not present in the system at the moment when FRRouting is starting, even it has the configuration for the interface or is done in networking, is completely useless, because lo0 is not present in the OS.

Version

FRRouting 10.4-dev (R02) on Linux(6.12.12-amd64).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
configured with:
    '--build=x86_64-linux-gnu' '--prefix=/usr' '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' '--disable-option-checking' '--disable-silent-rules' '--libdir=${prefix}/lib/x86_64-linux-gnu' '--libexecdir=${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' '--sbindir=/usr/lib/frr' '--with-vtysh-pager=/usr/bin/pager' '--libdir=/usr/lib/x86_64-linux-gnu/frr' '--with-moduledir=/usr/lib/x86_64-linux-gnu/frr/modules' '--disable-dependency-tracking' '--enable-rpki' '--disable-scripting' '--enable-pim6d' '--disable-grpc' '--with-libpam' '--enable-doc' '--enable-doc-html' '--enable-snmp' '--enable-fpm' '--disable-protobuf' '--disable-zeromq' '--enable-ospfapi' '--enable-bgp-vnc' '--enable-multipath=256' '--enable-pcre2posix' '--enable-user=frr' '--enable-group=frr' '--enable-vty-group=frrvty' '--enable-configfile-mask=0640' '--enable-logfile-mask=0640' 'build_alias=x86_64-linux-gnu' 'PYTHON=python3'

How to reproduce

In my case, the system is an Intel(R) Xeon(R) CPU E5-2687W v2 @ 3.40GHz with 2x SATA SSD.
The system has 67 interfaces: teaming, bridges, vlans, VRRP interfaces.

On a VM on my PC Ryzen 5900X I wasn't able to reproduce because the CPU is much faster than E5-2687W, even with 1 core.
The logs on Ryzen 5900X VM looks like this:

2025-02-22T01:31:14.486427+01:00 EasyOS systemd[1]: Starting frr.service - FRRouting...
2025-02-22T01:31:14.486448+01:00 EasyOS systemd[1]: Starting networking.service - ifupdown-ng networking initialization...
2025-02-22T01:31:14.497917+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run link executor for phase depend
2025-02-22T01:31:14.497932+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run vrf executor for phase depend
2025-02-22T01:31:14.498092+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run link executor for phase depend
2025-02-22T01:31:14.498106+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run multi-loopback executor for phase depend
2025-02-22T01:31:14.498121+01:00 EasyOS frrinit.sh[552]: Starting watchfrr with command: '  /usr/lib/frr/watchfrr  -d   zebra mgmtd bgpd ospfd ospf6d isisd pimd pim6d ldpd nhrpd eigrpd pbrd staticd bfdd vrrpd pathd'.
2025-02-22T01:31:14.674511+01:00 EasyOS networking[852]: + echo mgmt
2025-02-22T01:31:14.695651+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run link executor for phase depend
2025-02-22T01:31:14.699295+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run vrf executor for phase depend
2025-02-22T01:31:14.766569+01:00 EasyOS networking[947]: + echo mgmt
2025-02-22T01:31:14.790955+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run link executor for phase depend
2025-02-22T01:31:14.791537+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run vrf executor for phase depend
2025-02-22T01:31:14.800494+01:00 EasyOS networking[980]: + echo mgmt
2025-02-22T01:31:14.819933+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run link executor for phase depend
2025-02-22T01:31:14.821674+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run vrf executor for phase depend
2025-02-22T01:31:15.157514+01:00 EasyOS frrinit.sh[1316]: [1316|mgmtd] sending configuration
2025-02-22T01:31:15.158487+01:00 EasyOS frrinit.sh[1317]: [1317|zebra] sending configuration
2025-02-22T01:31:15.227313+01:00 EasyOS networking[568]: ifup: acquiring lock on /run/ifstate.lo0.lock
2025-02-22T01:31:15.227519+01:00 EasyOS networking[568]: ifup: changing state of interface lo0 to 'up'
2025-02-22T01:31:15.227554+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run link executor for phase create
2025-02-22T01:31:15.240524+01:00 EasyOS frrinit.sh[1374]: [1374|staticd] sending configuration
2025-02-22T01:31:15.243151+01:00 EasyOS networking[1371]: + [ -d /sys/class/net/lo0 ]
2025-02-22T01:31:15.243162+01:00 EasyOS networking[1371]: + ip link add lo0 type dummy
2025-02-22T01:31:15.250714+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run multi-loopback executor for phase create
2025-02-22T01:31:15.250732+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run link executor for phase pre-up
2025-02-22T01:31:15.255483+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run multi-loopback executor for phase pre-up
2025-02-22T01:31:15.255501+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run link executor for phase up
2025-02-22T01:31:15.255654+01:00 EasyOS networking[1384]: + ip link set up dev lo0
2025-02-22T01:31:15.273529+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run multi-loopback executor for phase up
2025-02-22T01:31:15.280363+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run link executor for phase post-up
2025-02-22T01:31:15.281444+01:00 EasyOS networking[568]: ifupdown: lo0: attempting to run multi-loopback executor for phase post-up
2025-02-22T01:31:15.575654+01:00 EasyOS staticd[1220]: [VTVCM-Y2NW3] Configuration Read in Took: 00:00:00
2025-02-22T01:31:15.575700+01:00 EasyOS staticd[1220]: [G6NKK-8C6DV] end_config: VTY:0x56095d3ebab0, pending SET-CFG: 0
2025-02-22T01:31:15.601495+01:00 EasyOS frrinit.sh[1317]: [1317|zebra] done
2025-02-22T01:31:15.771420+01:00 EasyOS frrinit.sh[1374]: [1374|staticd] done
2025-02-22T01:31:16.853505+01:00 EasyOS staticd[1220]: [GH3PB-C7X4Y] Static Route to 0.0.0.0/0 not installed currently because dependent config not fully available
2025-02-22T01:31:16.853553+01:00 EasyOS staticd[1220]: [GH3PB-C7X4Y] Static Route to ::/0 not installed currently because dependent config not fully available
2025-02-22T01:31:16.853569+01:00 EasyOS staticd[1220]: [GH3PB-C7X4Y] Static Route to 0.0.0.0/0 not installed currently because dependent config not fully available
2025-02-22T01:31:16.853581+01:00 EasyOS staticd[1220]: [GH3PB-C7X4Y] Static Route to ::/0 not installed currently because dependent config not fully available
2025-02-22T01:31:16.977965+01:00 EasyOS frrinit.sh[1316]: [1316|mgmtd] done
2025-02-22T01:31:18.471452+01:00 EasyOS networking[568]: ifupdown: changing state of dependent interface mgmt (of lan0.2) to up
2025-02-22T01:31:18.471486+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run link executor for phase create
2025-02-22T01:31:18.472875+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run vrf executor for phase create
2025-02-22T01:31:18.475413+01:00 EasyOS networking[3378]: + /sbin/ip link add mgmt type vrf table 1040
2025-02-22T01:31:18.494045+01:00 EasyOS kernel: mgmt: entered allmulticast mode
2025-02-22T01:31:18.494910+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run link executor for phase pre-up
2025-02-22T01:31:18.496811+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run vrf executor for phase pre-up
2025-02-22T01:31:18.499095+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run link executor for phase up
2025-02-22T01:31:18.500791+01:00 EasyOS networking[3395]: + ip link set up dev mgmt
2025-02-22T01:31:18.501076+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run vrf executor for phase up
2025-02-22T01:31:18.503429+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run link executor for phase post-up
2025-02-22T01:31:18.504225+01:00 EasyOS networking[568]: ifupdown: mgmt: attempting to run vrf executor for phase post-up
2025-02-22T01:31:18.533318+01:00 EasyOS networking[3415]: + VRRP_VRF=mgmt
2025-02-22T01:31:19.574160+01:00 EasyOS networking[3415]: + [ -n mgmt ]
2025-02-22T01:31:19.574184+01:00 EasyOS networking[3415]: + ip link set v1ac9e641-02-4 master mgmt
2025-02-22T01:31:19.586534+01:00 EasyOS networking[3415]: + ip link set v1ac9e641-02-6 master mgmt
2025-02-22T01:31:19.603368+01:00 EasyOS systemd[1]: Started frr.service - FRRouting.
2025-02-22T01:31:19.611922+01:00 EasyOS networking[3451]: + [ -n mgmt ]
2025-02-22T01:31:19.611950+01:00 EasyOS networking[3451]: + /sbin/ip link set lan0.2 master mgmt
2025-02-22T01:31:21.948026+01:00 EasyOS networking[568]: ifupdown: skipping dependent interface mgmt (of lan0.16) -- already configured
2025-02-22T01:31:21.972571+01:00 EasyOS networking[3637]: + VRRP_VRF=mgmt
2025-02-22T01:31:23.022444+01:00 EasyOS networking[3637]: + [ -n mgmt ]
2025-02-22T01:31:23.022469+01:00 EasyOS networking[3637]: + ip link set v37560454-10-4 master mgmt
2025-02-22T01:31:23.040880+01:00 EasyOS networking[3637]: + ip link set v37560454-10-6 master mgmt
2025-02-22T01:31:23.064936+01:00 EasyOS networking[3672]: + [ -n mgmt ]
2025-02-22T01:31:23.064959+01:00 EasyOS networking[3672]: + /sbin/ip link set lan0.16 master mgmt
2025-02-22T01:31:23.089936+01:00 EasyOS networking[568]: ifupdown: skipping dependent interface mgmt (of lan0.17) -- already configured
2025-02-22T01:31:23.111082+01:00 EasyOS networking[3698]: + VRRP_VRF=mgmt
2025-02-22T01:31:24.167565+01:00 EasyOS networking[3698]: + [ -n mgmt ]
2025-02-22T01:31:24.167584+01:00 EasyOS networking[3698]: + ip link set ve54fc588-11-4 master mgmt
2025-02-22T01:31:24.186922+01:00 EasyOS networking[3698]: + ip link set ve54fc588-11-6 master mgmt
2025-02-22T01:31:24.207037+01:00 EasyOS networking[3738]: + [ -n mgmt ]
2025-02-22T01:31:24.207749+01:00 EasyOS networking[3738]: + /sbin/ip link set lan0.17 master mgmt
2025-02-22T01:31:28.012658+01:00 EasyOS networking[568]: ifup: acquiring lock on /run/ifstate.mgmt.lock
2025-02-22T01:31:28.012666+01:00 EasyOS networking[568]: ifup: skipping auto interface mgmt (already configured), use --force to force configuration
2025-02-22T01:31:28.015144+01:00 EasyOS systemd[1]: Finished networking.service - ifupdown-ng networking initialization.

Expected behavior

I believe frr.service should start after networking.service finished.

Actual behavior

Service frr.service is starting before networking.service and because can happen to not have all interfaces ready before staticd is booting, all routes with set src will fail if the source IP is configured on one of the interfaces which networking.service must complete the task.

Additional context

In systemd the network.target is described as following:

network.target:

This unit is supposed to indicate when network functionality is available, but it is only very weakly defined what that is supposed to mean. However, the following should apply at minimum:

At start-up, any configured synthetic network devices (i.e. not physical ones that require hardware to show up and be probed, but virtual ones like bridge devices and similar which are created programmatically) that do not depend on any underlying hardware should be allocated by the time this target is reached. It is not necessary for these interfaces to also have completed IP level configuration by the time network.target is reached.

At shutdown, a unit that is ordered after network.target will be stopped before the network — to whatever level it might be set up by then — is shut down. It is hence useful when writing service files that require network access on shutdown, which should order themselves after this target, but not pull it in. Also see Running Services After the Network Is Up for more information.

It must emphasized that at start-up there's no guarantee that hardware-based devices have shown up by the time this target is reached, or even acquired complete IP configuration. For that purpose use network-online.target as described above.

Checklist

  • I have searched the open issues for this bug.
  • I have not included sensitive information in this report.
@EasyNetDev EasyNetDev added the triage Needs further investigation label Feb 22, 2025
@EasyNetDev EasyNetDev changed the title frr.service starts before networking is fully booted frr.service starts before networking is fully booted and breaks set src for static routes if source IP is on an interface not configured Feb 22, 2025
@EasyNetDev
Copy link
Contributor Author

I've rebuild FRRouting with a patch similar to this:

From a388a1d4138a02caa2ef88e1cf04d31053ea29d4 Mon Sep 17 00:00:00 2001
From: EasyNet <[email protected]>
Date: Sat, 22 Feb 2025 03:03:15 +0200
Subject: [PATCH] Fix frr.service boot time for set src

---
 tools/frr.service.in  | 3 +--
 tools/[email protected] | 3 +--
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/tools/frr.service.in b/tools/frr.service.in
index b52ee3f..2cc33b0 100644
--- a/tools/frr.service.in
+++ b/tools/frr.service.in
@@ -2,8 +2,7 @@
 Description=FRRouting
 Documentation=https://frrouting.readthedocs.io/en/latest/setup.html
 Wants=network.target
-After=network-pre.target systemd-sysctl.service
-Before=network.target
+After=network-pre.target network.target systemd-sysctl.service
 OnFailure=heartbeat-failed@%n
 
 [Service]
diff --git a/tools/[email protected] b/tools/[email protected]
index c8a2d3b..6b47f74 100644
--- a/tools/[email protected]
+++ b/tools/[email protected]
@@ -2,8 +2,7 @@
 Description=FRRouting
 Documentation=https://frrouting.readthedocs.io/en/latest/setup.html
 Wants=network.target
-After=network-pre.target systemd-sysctl.service
-Before=network.target
+After=network-pre.target network.target systemd-sysctl.service
 OnFailure=heartbeat-failed@%n
 
 [Service]
-- 
2.47.2

Now I can boot the system without worry about static route using set src. Is booting perfect normal.
Do you want to create a patch a submit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage Needs further investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@EasyNetDev