Second WAN strange behaviour / offline

[Okahzio]

Hello,

I've set up two WAN connections for failover. They worked well during tests. If one connection failed, the other took over and vice-versa.

But, I noticed something odd during setup. When I connected the second WAN, a regular router with the address 192.168.0.1, I could reach it from my LAN. I changed its IP to 172.20.0.1/24. After this, I couldn't access it from the LAN. However, WAN2 on OPNSense got an IP (172.20.0.100) from the router. Using the OPNSense diagnostics, I could ping 172.20.0.1, but not from the LAN. After turning the interface/gateway (I don't remember what exactly I switched) off and on, everything worked. i could access the WAN2 router from the LAN.

But, a day later, Monit told me WAN2 went offline (it was pinging 8.8.4.4). It hasn’t come back online till now. I’m facing the same issue – I can't access 172.20.0.1 from the LAN, but OPNSense can ping it. And now nothing helps. When I connect to the  WAN2 router directly to test, it's working just fine with internet connection being functional there.

Any ideas on where to start troubleshooting? Thanks!

[franco]

There is a fix in 23.7.2 today for the down->none transition of the gateway monitor that might be the cause this.


Cheers,
Franco