Messages

Normally, this should work without doing some special configurations. So I asume, that there is something wrong in your setup not passing the traffic to the non-default gateway.
Did you policy-route the traffic to the gateway group by any chance?

I do. The idea being to ensure that the general rules push traffic to the group, which is configured for failover, rather than to the specific interfaces.

I do have static routes defined, but after you've mentioned that I wonder if I actually need need specific rules to pass the management traffic to the indivudual interfaces instead or as well as the static routes?

Bump.  Anyone know how to keep the web UI accessible on a gateway that's a backup gateway for failover?

Thanks. I've got the failover working just fine though, which is what this guide covers.

What's not working is when gateway 1 is active I can't get to the web UI on gateway 2, and vice versa. If I'm on the failover gateway I'd like to be able to look at the web UI for gateway 1 to see what's up with the link, but I'm stuck on being able to see the web UI on gateway 2 only.

I know there'll be a way to do this. I just can't figure out what the neatest way of doing it is.

I've seen a number of examples of how to route traffic to a cable modem web UI when it's on a different subnet than the DHCP network it is providing, and that works fine for me.

The troube is, I have the same type of setup on my 5G failover modem, which I don't want to pass traffic across unless the cable modem circuit is down, and I'm struggling to find the right way to configure each of the interfaces so I can route traffic to the respective web UIs, but have the internet connection properly identified as up or down, and have the secondary link only pass any traffic in a failver scenario.

Does anyone have any posts, documentation, or other pointers I can look at for how to most effectively set this up?

Thanks.