WireGuard preventing startup when WAN (dhcp) not available?

[iorx]

Hi!

Had a strange behaviour when restarting OPNsense when WAN was down (ISP had trouble, got no address for WAN). It took more time than I expected to access (no response from ssh or web UI) so I physically checked with a display attached to the firewall.
The startup was at initiating the wireguard tunnel and exponentially increased the time 1,2,4, 8 sec for each try. I hit ctrl+c on it and it continued and was then able to access it trough ssh and https.

Sadly don't have logs for this event. Could be rather easily reproduced though.

But to the question is this by design or should it continue? If so, how long will it prevent the firewall from finish booting?

Latest version of OPNsense,
OPNsense 23.7.1_3-amd64
FreeBSD 13.2-RELEASE-p2
OpenSSL 1.1.1v 1 Aug 2023

Brgs