<![CDATA[Bad ping times to router]]>I'm not sure if this really is the right forum, but it is a network performance issue.

We had a storm go through a day ago and some power fluctuations, and now I am getting really bad latency times on the network.  Downloads seem to work fine, but ping times are really bad.  Here are the times to go from a CentOs server to pfSense connected to the same switch:

64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=3000 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=2000 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1000 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.106 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=3000 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=2000 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1000 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.102 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=3000 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=2000 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1000 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=0.110 ms

I get really good times going from CentOs to a Win7 machine that is 2 switches away from the first one:

64 bytes from 192.168.1.3: icmp_seq=4 ttl=128 time=0.184 ms
64 bytes from 192.168.1.3: icmp_seq=5 ttl=128 time=0.199 ms
64 bytes from 192.168.1.3: icmp_seq=6 ttl=128 time=0.202 ms
64 bytes from 192.168.1.3: icmp_seq=7 ttl=128 time=0.194 ms
64 bytes from 192.168.1.3: icmp_seq=8 ttl=128 time=0.215 ms
64 bytes from 192.168.1.3: icmp_seq=9 ttl=128 time=0.192 ms

So I think the problem is in PF.

I have rebooted all switches and pfSense, but still am getting these bad ping times.  Any suggestions as to what to look at?
status_rrd_graph_img.php.png
status_rrd_graph_img.php.png_thumb

]]>https://forum.netgate.com/topic/82598/bad-ping-times-to-routerRSS for NodeSun, 14 Jun 2026 04:10:36 GMTFri, 10 Apr 2015 03:31:50 GMT60<![CDATA[Reply to Bad ping times to router on Fri, 10 Apr 2015 13:50:02 GMT]]>1.  Traffic shaping forum is specifically for issues involving the traffic shaper.

2.  You likely had an environmental issue with your line after the storm.  I've seen cases of excess water shorting out a connection that fixed itself with the help of evaporation.

]]>https://forum.netgate.com/post/535320https://forum.netgate.com/post/535320Fri, 10 Apr 2015 13:50:02 GMT<![CDATA[Reply to Bad ping times to router on Fri, 10 Apr 2015 04:29:39 GMT]]>I have no idea what happened as I have been fighting this for a day or so, but now it just started working fine.  Ping times to the router look like this:

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=12.3 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=18.2 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=5.47 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.18 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=3.16 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=17.0 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=12.9 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.32 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=2.56 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=63.5 ms

I'm just glad it's working again  :D though I have no explanation.

]]>https://forum.netgate.com/post/535203https://forum.netgate.com/post/535203Fri, 10 Apr 2015 04:29:39 GMT