-
I'm not sure if this should be posted in packages or routing as it's a default gateway issue I'm having with a WireGuard gateway but I'm uncertain if it's limited to just WireGuard gateways.
So, I'm using WireGuard with a commercial VPN provider, I have the WireGuard gateway set as my default gateway with a static route on the WAN to the server's endpoint address to stop the VPN trying to reach the remote server via itself.
The issue I'm having is that after a reboot I have to go into routing > gateways and hit save, otherwise the system has no default gateway after the reboot and can't fetch updates and packages etc.
I've switched back to using OpenVPN for the time being as I don't have the problem with an OpenVPN gateway set as a default gateway (or a regular WAN gateway).
Also, maybe worth noting, I didn't get this issue with WireGuard on pfSense 2.5.0 with the initial WireGuard implementation that was removed.
Has anyone else experienced this with a WireGuard gateway set as a default gateway?