"
Hi, I've been experiencing the same issue described here where WireGuard (Mullvad in my case) goes stale after a WAN IP change.
As a workaround, I've been using a script triggered by WAN reconnect to run:
sh
Copy
Edit
service wireguard restart
This restores connectivity immediately.
Would it be possible for OPNsense to have built-in handling so WireGuard tunnels auto-restart when the WAN reconnects or the IP changes — similar to how OpenVPN handles it? This would remove the need for external scripts.
System details:
OPNsense 25.7.x
WireGuard plugin
WAN: DHCP (em0)
As a workaround, I've been using a script triggered by WAN reconnect to run:
sh
Copy
Edit
service wireguard restart
This restores connectivity immediately.
Would it be possible for OPNsense to have built-in handling so WireGuard tunnels auto-restart when the WAN reconnects or the IP changes — similar to how OpenVPN handles it? This would remove the need for external scripts.
System details:
OPNsense 25.7.x
WireGuard plugin
WAN: DHCP (em0)
