Messages

Hello!
I have a multiWAN setup with Starlink and another provider that is working mostly as expected, but whenever my Starlink WAN has an outage it stays offline until I manually toggle it disable/enable.
Once I do that it will immediately show online and the default gateway will switch to it.
"Allow Default Gateway Switching" enabled
"Upstream Gateway" is checked
"Monitor IP" is set for 8.8.8.8

Am I missing some setting that allows monitoring of a offline gateway until it is good to use again?

Thanks for any help!

Testing a bit more and it seems like I kind of have it worked out, but the clients keep getting a dhcp response, connect, then disconnect.
The dhcp servers on the WAN side be conflicting with mine or something?

Hey all!
I followed the guide to do a failover and load balanced multi-wan but it is 'breaking' alot of my firewall rules.
I have a hunch that it is because both WANs are using CG-NAT and thus I have a private IP assigned to each gateway. One is in 192.168.1.0/24 and the other is 192.168.10.0/24.

I have rules setup for my most VLANs to disallow rfc1918 (other that explicitly allowed destinations or ports) and to NAT back DNS to the firewall.
When I use one WAN everything works fine, but when I assign the gateway group to the VLANs they ignore all the other FW rules. Existing states still work so I know the routing is working to get internet.

Most of my VLANs have the following rules setup
Allow to this firewall for DNS/NTP/DHCP
Deny all RFC1918
Allow all

Does anyone have a setup like this and know how to setup FW rules and NAT to work correctly with the private IP interfaces?

Thanks!