RRD graphs / quality graph - higher than actual delays
-
In the Quality graph, my delay is very constant, and averages on about 53ms. However when I ping gateway from firewall, I get less than 1ms (0.130ms). Do you have similiar stats? Or is it something wrong in my setup?
-
I have a fairly similar issue. The Graph will work fine for a while then on any disruption that will fire off the apinger alarm it will drop to what appears to be the stddev rather than the average RTT.
Attached are related graphs and the following set of pings are taken from the pfSense box directly against the listed DHCP IPv4 gateway.
PING <redacted>(<redacted>): 56 data bytes 64 bytes from <redacted>: icmp_seq=0 ttl=64 time=9.573 ms 64 bytes from <redacted>: icmp_seq=1 ttl=64 time=7.227 ms 64 bytes from <redacted>: icmp_seq=2 ttl=64 time=7.479 ms 64 bytes from <redacted>: icmp_seq=3 ttl=64 time=8.459 ms 64 bytes from <redacted>: icmp_seq=4 ttl=64 time=7.100 ms 64 bytes from <redacted>: icmp_seq=5 ttl=64 time=7.493 ms 64 bytes from <redacted>: icmp_seq=6 ttl=64 time=7.792 ms 64 bytes from <redacted>: icmp_seq=7 ttl=64 time=7.877 ms 64 bytes from <redacted>: icmp_seq=8 ttl=64 time=9.792 ms 64 bytes from <redacted>: icmp_seq=9 ttl=64 time=9.007 ms --- <redacted>ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 7.100/8.180/9.792/0.926 ms</redacted></redacted></redacted></redacted></redacted></redacted></redacted></redacted></redacted></redacted></redacted></redacted></redacted>Apinger log for an entry during the time it is "broken"
Sep 3 17:10:23 apinger: #87242 from WAN_DHCP(<redacted>) delay: 7.140ms/7.425ms/4.248ms received = 3076 Sep 3 17:10:23 apinger: (avg. loss: 0.0%) Sep 3 17:10:23 apinger: (avg: 0.790ms)</redacted>Upon restarting the apinger service:
Sep 3 17:15:17 apinger: #34 from WAN_DHCP(<redacted>) delay: 7.831ms/7.664ms/77.859ms received = 33 Sep 3 17:15:17 apinger: Polling, timeout: 0.985s Sep 3 17:15:17 apinger: (avg. loss: 0.0%) Sep 3 17:15:17 apinger: (avg: 7.676ms)</redacted>Any thoughts or ideas?
Edit: Rummaging through the Redmine I see the issue has been reported: https://redmine.pfsense.org/issues/4081. It appears it is being corrected in Version 2.3. :)
