Plugin that needs to be configured before certain modules (and/or before device process is started)

[jbemmel]

For a wireguard VPN plugin I'm having an issue that OSPF is trying to establish adjacencies across a tunnel that is still under construction.

A race condition similar to how BIRD needs the VRF devices to exist before the configuration is deployed. Any thoughts on how we should solve this?

Perhaps we could define a pseudo datapath module and allow plugins to activate it and add scripts to be executed. Then ospf (and other modules) could have config_after: [ datapath ]

Note that the vrf Linux devices need to exist before wireguard tunnels get created, so even amongst datapath scripts there may be a partial ordering

[ipspace]

It looks like your main problem is that the wireguard device is not there when FRR is configured. I have no problem if you create the devices in the initial script, similar to how we create/configure interfaces for all other network devices (where, for example, a tunnel interface is created but without any parameters).

You might need to set the _linux_device_type or something similar in device quirks to create the right type of device.

[jbemmel]

Thank you, implemented in #3569

It works, but there are still some things that would ideally be configured in a different order:

2026/07/02 23:23:00 OSPF: [S5P8P-AJE73][EC 100663299] *** sendmsg in ospf_write failed to 224.0.0.5, id 62165, off 0, len 64, interface tun0, mtu 1420: Required key not available
2026/07/02 23:23:10 OSPF: [Y05P2-YJVXY] AdjChg: Nbr 10.0.0.2, NbrIP 10.1.0.2 (default) on tun0:10.1.0.1: Loading -> Full (LoadingDone)

i.e. configure the Wireguard tunnels (dataplane) before the controlplane (OSPF)