Upgraded for 2.3.2 to 2.3.3 packet loss issues
-
After installing 2.3.3 on my Active/Passive APU PFSense cluster I was having issues with packet loss on my Comcast business, disabling monitoring seems to fix the issue and the internet works properly.
on another note, when ever I have a packet loss the web interface becomes very unresponsive. This has been going on long before I upgraded to 2.3.3.
I do have the "Synchronize states" un-checked as it seamed to crash my backup router.
-
There is new option:
Added the ability to disable gateway monitoring actions without disabling gateway monitoring #3151
Try enabling it.
If issues would go - you definitely have problem with failover. -
This problem too.
Upgraded from 2.3.2 to 2.3.3 today.
2 WAN, both same packetloss - 33%. When this happens web interface unresponsive.P.S. From diag - traceroute monitor IPs go through different gateways (as expected).
-
This was not happening before 2.3.3 upgrade on my router.
As you can see the ping had no where near the packet loss reported.
Before upgrading I would regularly do tests pinging google dns and I'm surprised by the 2% lose on this ping.
my Comcast Internet is 50/10.
-
We have sites where ping to 8.8.8.8 is rate limited. We have sites where it's blocked by Google. I wouldn't use that for monitoring. Not reliable/useful.
-
Just for references : Every 10 minutes, I have 4-5s packet loss
-
We have sites where ping to 8.8.8.8 is rate limited. We have sites where it's blocked by Google. I wouldn't use that for monitoring. Not reliable/useful.
While what you say is valid point, I have been using google DNS for several months with no issues. I preformed an upgrade and have had issues. Google blocked / rate limited me on the same day I upgraded?
I just swapped my gateway monitors, my Comcast was using 8.8.8.8 now its 8.8.4.4 and swapped my other internet from 8.8.4.4 to 8.8.8.8. I still get packet-loss that is miss reported.
