WAN quality ping times rising
-
Apinger in 2.2 is broken maybe only in certain cases but for me its a huge step backwards from 2.1.5 there are several bug reports on redmine
-
Saying Apinger in 2.2 is a huge step backwards from 2.1.5 is quite a statement… I thought it had no where to go but up!
-
well it took a tank for me about 2 months prior to RC and just the other day it now reporting packet loss i cant find and a simple restart no longer fixes it i've been stopping it now for at least 30 seconds and then start it again
-
Apinger has issues hear are some bugs :
https://redmine.pfsense.org/issues/4081
https://redmine.pfsense.org/issues/4311
https://redmine.pfsense.org/issues/4354
https://redmine.pfsense.org/issues/3859
https://redmine.pfsense.org/issues/3815 -
Mine started behaving mo-betta when I changed:
Latency thresholds 500/100
Packet Loss thresholds 40/65
Probe Interval 10
Down 30Thats pretty relaxed settings.
It also worked quite well when I turned off gateway monitor all together… haha
-
wish turning it off was an option its just not with my isp's i could try backing off the setting, maybe ermal could weigh in on that
-
bit of an issue looks like it keeps getting pushed off
https://redmine.pfsense.org/issues/3191
dont know how any of the other firewalls on the market handle this but maybe the hold some clues?
-
i am using 8.8.8.8 and 8.8.4.4
250/500ms latency
10/15 packet loss
1 probe interval
10 down
10 Average Delay Replies Qty
50 Average Packet Loss Probes Qty
20 Lost Probe Delay -
So nothing wrong on the WAN side? This is a pfsense bug?
-
Until these issues are worked through, does anyone know a quick & easy way to just restart the apinger service every XX hours on a schedule using cron, or e.g. every day at midnight etc?
