I have two gateways: WAN and WAN2, which are in a gateway group, with gateway monitoring, and WAN is assigned highest priority.
My problem is with WAN2, which is assigned to on-board Intel adapter. When I lose internet connectivity to WAN2, either because my ISP has an outage or because I unplug the ethernet cable for testing purposes, WAN2 correctly shows in OPNsense as going offline, but the problem is that it remains offline even after internet connectivity is restored. The only way to get WAN2 to show as back online is to reboot OPNsense.
(Incidentally, WAN works perfectly, even though it's assigned to a NIC with a 2.5 GB Realtek adapter, but WAN comes back online after an outage with no problem.)
So here is my question: why is that, after going offline due to loss of connectivity, gateway monitoring will not show WAN2 as back online even after connectivity is restored, yet rebooting OPNsense will somehow cause gateway monitoring to show that WAN2 is back online?
Can anyone offer any troubleshooting tips?
Hi,
did you check if the dpinger service for the WAN2 gateway is still down after connection loss? There was an issue with that on IPv6 with statically assigned IPs. The gateway.log can tell you more about possible shortcomings or error messages.
Furthermore, what is your configuration on WAN/WAN2 in terms of address assignment and upstream gateway?
I did not check dpinger for WAN2 after a connection loss but will do so. I cannot take WAN2 offline right now to test because it's the middle of the day where I am and my spouse works from home and needs online connectivity, so I cannot risk doing something that will probably require me to reboot OPNsense. However, tonight I will test this, take WAN2 offline, and look at dpinger.
Regarding upstream, both WAN2 and WAN are assigned IPv4 addresses through DHCP.
https://forum.opnsense.org/index.php?topic=36558.msg180685#msg180685
reapplying makes it come back online for me under gateway