Line quality measurements

vielfede

I'm little bit frustrated by monitoring ip system: what you see (And I think pfsense sees) on rrd graph is not what it is!
As you can see in the picture in attachment, I have a min delay of 142ms… where if I ping "Monitor IP" from fw I get the following...


PING 80.18.114.145 (80.18.114.145) from 88.36.185.244: 56 data bytes
64 bytes from 80.18.114.145: icmp_seq=0 ttl=253 time=12.752 ms
64 bytes from 80.18.114.145: icmp_seq=1 ttl=253 time=14.079 ms
64 bytes from 80.18.114.145: icmp_seq=2 ttl=253 time=14.243 ms

It seems like something is going wrong in time measurement…
Moreover (see picture) I can notice delay increment week by week.... where I have always the same response time pinging Monitor IP (i.e. my DSL is ok) from fw or lan.

That is that bad because of load balancing.... If the dalay is too big it continue switch back and forth on the other line with connections loss.

Am I the only one with this issue?
Thanks in advance

Quality_rrd_today.JPG_thumb

Quality_rrd_month.JPG_thumb

grandrivers

My understanding is its all Apinger and yes messes with load balancing and failover

heper

apinger will not be completely fixed any time soon.
afaik they are planning a complete rewrite/method to the current montoring system, but no ETA has been announced.

theres a current bug report that might be related to your situation, but no fix has been created and it's pushed to 2.2.2 because it wouldn't make the pending 2.2.1-release (see details here: https://redmine.pfsense.org/issues/4081)

vielfede

@heper:

apinger will not be completely fixed any time soon.
afaik they are planning a complete rewrite/method to the current montoring system, but no ETA has been announced.

theres a current bug report that might be related to your situation, but no fix has been created and it's pushed to 2.2.2 because it wouldn't make the pending 2.2.1-release (see details here: https://redmine.pfsense.org/issues/4081)

Thanks!

Meanwhile I found a workaround: change the Monitor IP to another address (eg. google.com) and than change it back to original one solve (for a while >>days) the problem, without restart.

grandrivers

just restart Apnger changing IP would restart Apinger