Messages

Interesting Point.

If I use the same DNS-Servers as monitoring IP they must match, since they both set a Route to the specified IP with the corresponding gateway.
I might have messed something up there, will check that as soon i get on site.

Which also means, if one of the Clients has an fixed DNS entry of one of those DNS/monitoring-IPs, there will be trouble too.

Thanks for the reply.

According to the documentation opnsense is a stateful firewall.
As i understand it, "Sticky connections" is there to force established connections to use the same WAN.

The Problem occurs before any sort of idle-timeout.
On the second WAN no connection is established / routes to nowhere (as far i can tell). Any idea how to verify/troubleshoot that assumption?

I have the same problem with a pretty similar setup.
Execpt with 2 DSL Lines as WAN, no shaping (yet), running 20.1.5

I followed the steps in the Multi WAN documentation, the steps (1-8) you mentioned above.

Same result as yours, each connection works as a single Gateway.
As soon as i direct the traffic through the Gateway Group with the Firewall Rule, half the the connection don't work.

I'm new to opnsense too and don't know how to troubleshoot this, so my Post is more a bump up.