Gateway latency wrong?



  • I added another pfsense box to my network to work as an AP. It's on the LAN and working perfectly but in the main pfSense on the Gateway status page, the latency to the AP is wrong, it shows more than 22ms but if I ping it from the console the result is completely different, like this:

    192.168.1.1: main pfSense
    192.168.1.90: AP pfSense

    /tmp/apinger.status on main:
    192.168.1.90|192.168.1.1|AP|39187|39185|1334340340|22.698ms|0.0%|none

    Direct ping from main console:
    64 bytes from 192.168.1.90: icmp_seq=0 ttl=64 time=0.256 ms
    64 bytes from 192.168.1.90: icmp_seq=1 ttl=64 time=0.140 ms
    64 bytes from 192.168.1.90: icmp_seq=2 ttl=64 time=0.138 ms
    64 bytes from 192.168.1.90: icmp_seq=3 ttl=64 time=0.141 ms
    64 bytes from 192.168.1.90: icmp_seq=4 ttl=64 time=0.144 ms
    64 bytes from 192.168.1.90: icmp_seq=5 ttl=64 time=0.140 ms

    Both pfSense are v.2.0.1 and another strange fact is that the gateway status from the AP pfSense shows the right RSS.
    Any ideas? It probably is some mistake I made but can't find it  ???



  • I sometimes do have the same behaviour. two pfsense 2.0.1 connected with a crossover cable and one pfsense shows high ms and the other shows low ms.

    Perhaps this is sometimes the reason why my gateway goes down because of high latency but there isn't any real high latency.



  • get a packet capture of the ICMP that apinger generates and check the timestamps. I've never seen it be anything other than accurate.



  • @cmb:

    get a packet capture of the ICMP that apinger generates and check the timestamps. I've never seen it be anything other than accurate.

    OK today we had a power outage and the both pfSense servers were restarted, and now it shows the right latency. I didn't change anything. That was weird, a windows-like solution :D


Log in to reply