Monitor is FALSE detecting one of my WANs as DOWN and another WAN as UP
-
It is smart enough to run automatically. You have the special case/requirements.
Sure, this is what I am saying: pfSense does not work in "special case" of having 3 WANs round robbin.
-
exactly if the monitors are going out bad and not getting a response
Why this can happen? Taking into consideration, that normal
pingworks? -
Only your ISP can tell you why sent echo requests are not responded to.
Set all of those settings back to the default. Does it work?
If not, take a quick packet capture for posting here then try setting the data payload to 2. Does it work?
If not, take a quick packet capture for posting here then try setting the data payload to 64. Does it work?
If not, take a quick packet capture for posting here then post all of the above.
-
Only your ISP can tell you why sent echo requests are not responded to.
How provider can technically distinguish pings from ping command and from dpinger?
-
The payload size of a normal ping from the ping command is 56 bytes. The payload size of a dpinger ping is 0 by default.
Hence why I asked you to do what I did.
It's pretty rare but some devices freak out with the 0-byte payload even though it's completely legal.
-
Setting payload to 56 immediately made monitor think gateway is up, thank you!
I have set it to 56 in other monitors, and picture also became better: now zeros in RTT and RTTsd columns!
-
No, last statement was wrong: after some time these columns got some positive values.
-
I had flase GW down reports when I first configured multi-wan. Then changed Monitor IP's from google to OpenDNS, and problems went away.
Also this gives RTT & RTTsd figures which are probably more realistic for internet connectivity, rather than using the next-hop provider IP.
DSL GW = 7.5mS & 0.2mS
Cable GW = 15mS & 3.5mSCable is always longer due to the way Docsis works !!
-
I am have same issue and same scheme as in author of topic with gateway group:
1 gateway is tier 2 (connected directly to the internet provider, used as backup)
2 gateway is tier 1 (connected to external router 1 with VLAN2 by DHCP)
3 gateway is tier 1 (connected to external router 2 with VLAN3 by DHCP)
and last 3 gateway can't resolve "UP" state of gateway WAN when external router 2 changes WAN IP. Monitoring IP on 2 gateway is 8.8.4.4, on 3 gateway 8.8.8.8.
Payload and changing monitoring IP did not help at all, when i set "Trigger Level' as "High Latency" it works a little better, but when i set it to "Packet Loss" and in time when router 2 on 3 gateway changes WAN ip - on pfSense in100% case it will marks 3 gateway as offline forever, but in Diagnostics -> Ping i can ping any address from 3 gateway without any problems. If i will go to System -> Routing and save and apply any gateway without changes - 3 gateway will back to Online state till router 2 changes WAN IP address.
2 gateway have same type router as on 3 gateway, but when it's change IP - pfSense make it Offline for few minutes and then make it back to Online state in any types of Trigger Level.
It seems that pfSense buggy with dpinger on some scenarios. -
It's more interesting, i switch Trigger Level to High Latency, and some time later pfSense himself switch it to Packet Loss! I didn't understand, why it happens.
And for sure it's dpinger bugs related, case i have checked "Disable Gateway Monitoring Action" and then made reconnect on router 2 (3 gateway) and in "Gateway status" i get on 3 gateway "Danger, Packetloss: 100%" on 3 gateway, i have check - traffic still goes through 3 gateway (router 2) without any problems, but dpinger thinks that it's dead for sure forever, till i make "save and apply" in any gateway settings.
I didn't now how to make monitoring work in pfSense. :(
