Multi-wan failover not working

Started by shtech, June 12, 2020, 02:01:07 PM

Previous topic - Next topic
OPNsense 19.7.1-amd64

Wan1 -  DHCP
Wan2 -  static ip

Previously they had att uverse on wan2 in dhcp and wan1 in DHCP from it's carrier, failover worked just fine. They switched to a new carrier with a static ip for wan2, failover stopped working. I followed this doc originally and have checked and re-checked the config: https://docs.opnsense.org/manual/how-tos/multiwan.html

It matches the how to doc. internally, once wan1 has been disconnected, you cannot ping by FQDN or IP to anywhere outside the firewall.

I can force traffic out wan2 and it works fine, when wan 1 is also working.

Outside of changing the connection to wan 2 carrier to a static IP and new gateway address (which was added to the GW group), nothing else has changed.

We have rules in the firewall that allow us to login remotely. When they pull wan1 from the firewall,  we cannot login using wan2 IP and they never start routing out wan2. When wan1 is reconnected, we can login via both public IP's of the firewall. Which seems extremely strange to me.

I understand that version 20 is available and we will plan to upgrade this unit to 20. I just don't understand why it has stopped working after changing the connection on wan2. There seem to be a few bugs related to DHCP and wan failover. Wan1 is a DHCP connection from that carrier and wan2 is static.