"
Upon further inspection, my issue may be different - my specific issue is that after a recent WAN drop, WG does not reconnect and I see the following error in the log:
/usr/local/opnsense/scripts/Wireguard/wg-service-control.php: The command '/sbin/route add -'inet' '192.168.28.13' -interface 'wg1'' returned exit code '1', the output was 'add host 192.168.28.13: gateway wg1 fib 0: route already in table'
Disabling and Re-enabling the WireGuard Peer, Disabling and Re-enabling the WireGuard Interface, and Restarting the WireGuard Service all yield no results, and even a reboot doesn't solve the issue. I will update with a solution when I find one.
Update: upgrading from OpenSense 24.7 to 25.1 solved my issue, interesting
/usr/local/opnsense/scripts/Wireguard/wg-service-control.php: The command '/sbin/route add -'inet' '192.168.28.13' -interface 'wg1'' returned exit code '1', the output was 'add host 192.168.28.13: gateway wg1 fib 0: route already in table'
Disabling and Re-enabling the WireGuard Peer, Disabling and Re-enabling the WireGuard Interface, and Restarting the WireGuard Service all yield no results, and even a reboot doesn't solve the issue. I will update with a solution when I find one.
Update: upgrading from OpenSense 24.7 to 25.1 solved my issue, interesting
