RTT on gateway status

maverick_slo

Hi all!

See screenshot of gateways monitor and actual pfSense ping results.
Is this OK or not?

And if it is, somebody care to explain why?

Thanks!

WAN_DHCP gateway:

[2.3-BETA][root@]/root: ping XX.XX.15.1
PING XX.XX.15.1 (XX.XX.15.1): 56 data bytes
64 bytes from XX.XX.15.1: icmp_seq=0 ttl=64 time=2.382 ms
64 bytes from XX.XX.15.1: icmp_seq=1 ttl=64 time=1.747 ms
64 bytes from XX.XX.15.1: icmp_seq=2 ttl=64 time=2.117 ms
64 bytes from XX.XX.15.1: icmp_seq=3 ttl=64 time=1.748 ms
64 bytes from XX.XX.15.1: icmp_seq=4 ttl=64 time=1.716 ms
64 bytes from XX.XX.15.1: icmp_seq=5 ttl=64 time=1.732 ms
64 bytes from XX.XX.15.1: icmp_seq=6 ttl=64 time=1.658 ms
64 bytes from XX.XX.15.1: icmp_seq=7 ttl=64 time=1.756 ms
64 bytes from XX.XX.15.1: icmp_seq=8 ttl=64 time=1.737 ms
64 bytes from XX.XX.15.1: icmp_seq=9 ttl=64 time=2.200 ms
^C
--- XX.XX.15.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.658/1.879/2.382/0.241 ms

PPPOE_DHCP6 gateway:

[2.3-BETA][root@]/root: ping6 XXXX:XXXX:ffff::9
PING6(56=40+8+8 bytes) 2001:15c2:201:4:20e:cff:fe84:c04e --> XXXX:XXXX:ffff::9
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=0 hlim=64 time=2.420 ms
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=1 hlim=64 time=2.069 ms
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=2 hlim=64 time=2.152 ms
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=3 hlim=64 time=2.018 ms
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=4 hlim=64 time=2.012 ms
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=5 hlim=64 time=2.032 ms
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=6 hlim=64 time=2.027 ms
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=7 hlim=64 time=2.175 ms
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=8 hlim=64 time=2.030 ms
16 bytes from XXXX:XXXX:ffff::9, icmp_seq=9 hlim=64 time=2.575 ms
^C
--- XXXX:XXXX:ffff::9 ping6 statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 2.012/2.151/2.575/0.185 ms

PPPOE_PPPOE gateway:


[2.3-BETA][root@]/root: ping XXX.XX.XX.174
PING XXX.XX.XX.174 (XXX.XX.XX.174): 56 data bytes
64 bytes from XXX.XX.XX.174: icmp_seq=0 ttl=255 time=1.598 ms
64 bytes from XXX.XX.XX.174: icmp_seq=1 ttl=255 time=1.594 ms
64 bytes from XXX.XX.XX.174: icmp_seq=2 ttl=255 time=1.560 ms
64 bytes from XXX.XX.XX.174: icmp_seq=3 ttl=255 time=1.529 ms
64 bytes from XXX.XX.XX.174: icmp_seq=4 ttl=255 time=1.644 ms
64 bytes from XXX.XX.XX.174: icmp_seq=5 ttl=255 time=1.462 ms
64 bytes from XXX.XX.XX.174: icmp_seq=6 ttl=255 time=1.519 ms
64 bytes from XXX.XX.XX.174: icmp_seq=7 ttl=255 time=1.490 ms
64 bytes from XXX.XX.XX.174: icmp_seq=8 ttl=255 time=1.564 ms
64 bytes from XXX.XX.XX.174: icmp_seq=9 ttl=255 time=1.508 ms
^C
--- XXX.XX.XX.174 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.462/1.547/1.644/0.053 ms
```![gateways.png](/public/_imported_attachments_/1/gateways.png)
![gateways.png_thumb](/public/_imported_attachments_/1/gateways.png_thumb)

dennypage

It's not clear what you are asking after. If you are asking about the difference between the average reported by ping and the average shown by the gateway monitor, then it's important to keep in mind that these are averaging over different sample sets. Ping is looking at 10 samples over the 10 seconds you running the command, whereas by default, the gateway monitor is looking at 120 samples over the preceding 30 seconds. It's easy to have a high latency spike that has an extended effect on the 30 second average.

maverick_slo

Thanks man!
Exactly what I needed to know and your answer explains it :)