Bug #14489
openFRR needs delayed startup
0%
Description
Hi,
FRR is currently started before completing Wireguard tunnels initialization:
[FRR startup]
2023-06-17 18:48:30 ,754 INFO: Called via "Namespace(input=None, reload=True, test=False, debug=False, log_level='info', stdout=False, pathspace=None, filename='/var/etc/frr/frr.conf', overwrite=False, bindir='/usr/local/bin', confdir='/var/etc/frr', rundir='/var/run/frr', vty_socket=None, daemon='')"
[Wireguard initialization]
Jun 17 18:48:31 fw1 kernel: wg2: changing name to 'tun_wg2'
Jun 17 18:48:31 fw1 kernel: tun_wg2: link state changed to UP
Note that Wireguard starts 1 second after FRR, but in FRR there are already references to the renamed interfaces, which doesn't exist until 1 second later. To workaround this I have to manually restart FRR after each boot.
Just delaying the startup of FRR until Wireguard is fully set up would be enough.
Regards
Updated by Tjabo T. 4 months ago
Spike R.D. wrote:
Hi,
FRR is currently started before completing Wireguard tunnels initialization:
[FRR startup]
2023-06-17 18:48:30 ,754 INFO: Called via "Namespace(input=None, reload=True, test=False, debug=False, log_level='info', stdout=False, pathspace=None, filename='/var/etc/frr/frr.conf', overwrite=False, bindir='/usr/local/bin', confdir='/var/etc/frr', rundir='/var/run/frr', vty_socket=None, daemon='')"[Wireguard initialization]
Jun 17 18:48:31 fw1 kernel: wg2: changing name to 'tun_wg2'
Jun 17 18:48:31 fw1 kernel: tun_wg2: link state changed to UPNote that Wireguard starts 1 second after FRR, but in FRR there are already references to the renamed interfaces, which doesn't exist until 1 second later. To workaround this I have to manually restart FRR after each boot.
Just delaying the startup of FRR until Wireguard is fully set up would be enough.
Regards
+1 (fully patched system, same behavior and fix request)