NetBird Interface breaks boot

[franco]

I agree. I'll try to extract this from the original commit stream and directly commit it with the original authorship.

One of the many reasons why small PRs make more sense.


Cheers,
Franco

[Greg_E]

Thanks, I may update (again) and see if the patch helps me. I see there is an update to the current OPN version anyway.

[franco]

That change should be available in the latest Netbird plugin now.

[franco]

I was mistaken. It will be released in 26.1.8 later today.

[JoopB]

Updated to 26.7.1_1. Tested this by adding Netbird Interface and rebooting, it works now.

Thanx for the fix guys! Can finally reach router itself through Netbird

[RaphaelAlbrecht]

This does sound like a boot-order/race issue rather than something you're doing wrong, especially since it only happens once the NetBird device is assigned as an interface. At that point OPNsense treats it more like a normal interface during config/interface setup, but NetBird itself still needs working routing/DNS to come up cleanly. If it tries to resolve the control server before the system has a usable path, things can get ugly.

The fallback to default config is the worrying part though — that should not happen just because a tunnel interface cannot start. I'd suggest opening an issue for the plugin/OPNsense side with the boot log and config snippet for the assigned NetBird interface. As a workaround, I'd leave the NetBird interface unassigned for now and use floating/rule aliases if possible, or test with an IP-only control server plus reliable early DNS to confirm whether DNS timing is the trigger.