dpinger issue

[franco]

> WAN 1: 8.8.8.8
> WAN 2: 8.8.8.8

Set WAN 2 to 8.8.4.4, this won't work otherwise.


Cheers,
Franco

[newsense]

Hi franco,

While it's perfectly reasonable/logical to have different Monitor IPs, why would it matter if using the same DNS server(s) on both gateways ?

[franco]

Each DNS server will set a /32 host route through the specified gateway. You cannot have two routes through two gateways for the same destination. It will fail to resolve DNS when on WAN2.

[newsense]

Thanks franco, didn't knew the routes were actually set. Everything makes sense now.

[franco]

It's also described here in step 3:

https://docs.opnsense.org/manual/how-tos/multiwan.html

[alh]

Does it work in your scenario? We have the same issue with dpinger but on a single gateway. No matter what monitoring IP we enter after some time dpinger reports package loss and then the gateway goes offline.

[alh]

Just to feedback for someone having the same issue:

In our case the problem was caused by our ISP Unitymedia in Germany. After a certain period of time they activate some Anti-DoS rule and block our pings (according to their technical support this only happens if you use their DNS servers for name resolution and Google's or Cloudflare's DNS servers for monitoring due to the way that their IP is resolved). Our solution was to increase the probe interval to 15 sec and the time period to 120 sec and to eliminate their DNS servers from our setup.