Dashboard gateway showing very high ping time
Take a look at the images.
Its from a 2.4.2 firewall.
Notice how high those ping times to the gateways are when they are viewed from the dashboard.
Look how much less (normal) they are when I ping the gateways.
Does anyone know if its a bug in this version?
![DF gateway.JPG](/public/imported_attachments/1/DF gateway.JPG)
![DF gateway.JPG_thumb](/public/imported_attachments/1/DF gateway.JPG_thumb)
![df primary gateway ping.JPG](/public/imported_attachments/1/df primary gateway ping.JPG)
![df primary gateway ping.JPG_thumb](/public/imported_attachments/1/df primary gateway ping.JPG_thumb)
![df secondary gateway ping.JPG](/public/imported_attachments/1/df secondary gateway ping.JPG)
![df secondary gateway ping.JPG_thumb](/public/imported_attachments/1/df secondary gateway ping.JPG_thumb)
Can not duplicate this.. Running 2.4.2
PING 220.127.116.11 (18.104.22.168): 56 data bytes
64 bytes from 22.214.171.124: icmp_seq=0 ttl=255 time=10.638 ms
64 bytes from 126.96.36.199: icmp_seq=1 ttl=255 time=9.671 ms
64 bytes from 188.8.131.52: icmp_seq=2 ttl=255 time=8.606 ms
64 bytes from 184.108.40.206: icmp_seq=3 ttl=255 time=8.534 ms
64 bytes from 220.127.116.11: icmp_seq=4 ttl=255 time=8.371 ms
64 bytes from 18.104.22.168: icmp_seq=5 ttl=255 time=8.460 ms
64 bytes from 22.214.171.124: icmp_seq=6 ttl=255 time=12.785 ms
64 bytes from 126.96.36.199: icmp_seq=7 ttl=255 time=8.492 ms
64 bytes from 188.8.131.52: icmp_seq=8 ttl=255 time=8.178 ms
64 bytes from 184.108.40.206: icmp_seq=9 ttl=255 time=10.264 ms
–- 220.127.116.11 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.178/9.400/12.785/1.395 ms
Ping from pfsense avg shows 9.4 and widget shows
If I ping from a laptop on the LAN side its less than 1 ms too.
so pinging from the firewall interface and a laptop shows < 1ms but the dashboard shows between 2 and 8 ms, mostly around 4 or so.
So this gateway is on your lan? less than 1 ms is lan speeds, normally this would not be a ISP/WAN connection speed..
So dpinger would be sending 0 sized pings.. While your normal pings would be sending some data in the ping.. Maybe the gateway takes longer to answer the zero sized pings? That is a wild ass guess… But only thing that comes to mind that could be different.
In your gateway monitor you can tell it to send some data to match up with what your normal pings are sending.. "56 data bytes"
No the gateway is on the WAN but its in a data center so its a gig connection to a device in the same building.
But thats kind of the same thing you mentioned of being a lan.
In the other data center we have 2.2.6 and we are seeing real numbers like as in .6ms and it matches the ping when done.
so that does not match this behavior.