After switching to pfSense, ping is VERY slow

riahc8

Hello

Finally made the switch but there is a huge problem....

I used to get 30ms pings....Now im around 80-90ms....This is very noticeable in game

Its extremely strange. From the pfSense size, I dont see the hardware overloaded....

What tests can I run?

stephenw10

What are you testing to? What is your WAN? What's the ping time from pfSense itself?

Steve

riahc8

@stephenw10 Ive justed tested a lot of things.

Cable to cable, direct ethernet from pfsense to laptop, same speeds 1.5Mb....

On the ISP router, the speeds basically never stop rising before a download ends.

This is very strange.

Ping from the pfSense to a host are meh as well.....2,3 9ms.....None below 1ms

johnpoz

@riahc8 said in After switching to pfSense, ping is VERY slow:

pfSense to a host are meh as well.....2,3 9ms.....None below 1m

Are you saying ping from pfsense to some host on your own wired network is like 9ms? What about to pfsense?

What about host to host?

pfsense to wired pc

[23.01-RELEASE][admin@sg4860.local.lan]/: ping 192.168.9.100
PING 192.168.9.100 (192.168.9.100): 56 data bytes
64 bytes from 192.168.9.100: icmp_seq=0 ttl=128 time=0.599 ms
64 bytes from 192.168.9.100: icmp_seq=1 ttl=128 time=0.380 ms
64 bytes from 192.168.9.100: icmp_seq=2 ttl=128 time=0.562 ms
64 bytes from 192.168.9.100: icmp_seq=3 ttl=128 time=0.366 ms
64 bytes from 192.168.9.100: icmp_seq=4 ttl=128 time=0.405 ms
64 bytes from 192.168.9.100: icmp_seq=5 ttl=128 time=0.558 ms
64 bytes from 192.168.9.100: icmp_seq=6 ttl=128 time=0.714 ms
64 bytes from 192.168.9.100: icmp_seq=7 ttl=128 time=0.541 ms

nas to pfsense, etc..

ash-4.4# ping 192.168.9.253
PING 192.168.9.253 (192.168.9.253) 56(84) bytes of data.
64 bytes from 192.168.9.253: icmp_seq=1 ttl=64 time=0.545 ms
64 bytes from 192.168.9.253: icmp_seq=2 ttl=64 time=0.320 ms
64 bytes from 192.168.9.253: icmp_seq=3 ttl=64 time=0.210 ms
64 bytes from 192.168.9.253: icmp_seq=4 ttl=64 time=0.201 ms
64 bytes from 192.168.9.253: icmp_seq=5 ttl=64 time=0.198 ms

riahc8

@johnpoz said in After switching to pfSense, ping is VERY slow:

@riahc8 said in After switching to pfSense, ping is VERY slow:

pfSense to a host are meh as well.....2,3 9ms.....None below 1m

Are you saying ping from pfsense to some host on your own wired network is like 9ms? What about to pfsense?

What about host to host?

pfsense to wired pc

[23.01-RELEASE][admin@sg4860.local.lan]/: ping 192.168.9.100
PING 192.168.9.100 (192.168.9.100): 56 data bytes
64 bytes from 192.168.9.100: icmp_seq=0 ttl=128 time=0.599 ms
64 bytes from 192.168.9.100: icmp_seq=1 ttl=128 time=0.380 ms
64 bytes from 192.168.9.100: icmp_seq=2 ttl=128 time=0.562 ms
64 bytes from 192.168.9.100: icmp_seq=3 ttl=128 time=0.366 ms
64 bytes from 192.168.9.100: icmp_seq=4 ttl=128 time=0.405 ms
64 bytes from 192.168.9.100: icmp_seq=5 ttl=128 time=0.558 ms
64 bytes from 192.168.9.100: icmp_seq=6 ttl=128 time=0.714 ms
64 bytes from 192.168.9.100: icmp_seq=7 ttl=128 time=0.541 ms

nas to pfsense, etc..

ash-4.4# ping 192.168.9.253
PING 192.168.9.253 (192.168.9.253) 56(84) bytes of data.
64 bytes from 192.168.9.253: icmp_seq=1 ttl=64 time=0.545 ms
64 bytes from 192.168.9.253: icmp_seq=2 ttl=64 time=0.320 ms
64 bytes from 192.168.9.253: icmp_seq=3 ttl=64 time=0.210 ms
64 bytes from 192.168.9.253: icmp_seq=4 ttl=64 time=0.201 ms
64 bytes from 192.168.9.253: icmp_seq=5 ttl=64 time=0.198 ms

This is from pfsense to wired

[2.7.0-DEVELOPMENT][james@pfsense]/home/james: ping 192.168.1.13
PING 192.168.1.13 (192.168.1.13): 56 data bytes
64 bytes from 192.168.1.13: icmp_seq=0 ttl=128 time=0.372 ms
64 bytes from 192.168.1.13: icmp_seq=1 ttl=128 time=0.234 ms
64 bytes from 192.168.1.13: icmp_seq=2 ttl=128 time=0.220 ms
64 bytes from 192.168.1.13: icmp_seq=3 ttl=128 time=0.220 ms
64 bytes from 192.168.1.13: icmp_seq=4 ttl=128 time=0.235 ms
64 bytes from 192.168.1.13: icmp_seq=5 ttl=128 time=0.222 ms
64 bytes from 192.168.1.13: icmp_seq=6 ttl=128 time=0.226 ms
64 bytes from 192.168.1.13: icmp_seq=7 ttl=128 time=0.201 ms
64 bytes from 192.168.1.13: icmp_seq=8 ttl=128 time=0.217 ms
64 bytes from 192.168.1.13: icmp_seq=9 ttl=128 time=0.243 ms
64 bytes from 192.168.1.13: icmp_seq=10 ttl=128 time=0.228 ms

Something else wired to pfsense

root@R01:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.410 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.338 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.368 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.335 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.318 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.326 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.364 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.348 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.342 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.356 ms

So it seems that locally traffic is working correctly. It also seems that traffic thru the switch seems fine.

Ive also changed cables (even if it was working fine). This has also changed in Wi-Fi

SteveITS

@riahc8 So what “to a host” is 9ms, and where is it? <1ms is generally going to be on your wired network.

riahc8

Another example is 400ms+ pings to Google.com...

SteveITS

@riahc8 Try a traceroute and see if that has slow legs.

johnpoz

@steveits said in After switching to pfSense, ping is VERY slow:

see if that has slow legs

Yeah that would be good test.

$ tracert -d 8.8.8.8                                 
                                                     
Tracing route to 8.8.8.8 over a maximum of 30 hops   
                                                     
  1    <1 ms    <1 ms    <1 ms  192.168.9.253        
  2    11 ms    10 ms    11 ms  209.122.32.1         
  3    10 ms    11 ms    12 ms  216.80.79.9          
  4    11 ms    10 ms    11 ms  207.172.18.38        
  5    10 ms    12 ms    11 ms  207.172.19.243       
  6    23 ms    13 ms    13 ms  72.14.205.48         
  7     9 ms    10 ms    12 ms  142.251.249.49       
  8    20 ms    12 ms    10 ms  142.251.60.23        
  9    11 ms    10 ms    11 ms  8.8.8.8

Your not using vpn are you?

riahc8

@johnpoz said in After switching to pfSense, ping is VERY slow:

@steveits said in After switching to pfSense, ping is VERY slow:

see if that has slow legs

Yeah that would be good test.

$ tracert -d 8.8.8.8                                 
                                                     
Tracing route to 8.8.8.8 over a maximum of 30 hops   
                                                     
  1    <1 ms    <1 ms    <1 ms  192.168.9.253        
  2    11 ms    10 ms    11 ms  209.122.32.1         
  3    10 ms    11 ms    12 ms  216.80.79.9          
  4    11 ms    10 ms    11 ms  207.172.18.38        
  5    10 ms    12 ms    11 ms  207.172.19.243       
  6    23 ms    13 ms    13 ms  72.14.205.48         
  7     9 ms    10 ms    12 ms  142.251.249.49       
  8    20 ms    12 ms    10 ms  142.251.60.23        
  9    11 ms    10 ms    11 ms  8.8.8.8

Your not using vpn are you?

No VPN.

OK, this is showing more...

$ traceroute -nd 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 40 byte packets
 1  192.168.254.2  1.414 ms  1.279 ms  1.285 ms
 2  * * *
 3  * * *
 4  81.46.76.185  57.189 ms
    81.46.76.186  36.357 ms  38.483 ms
 5  5.205.25.121  39.625 ms  39.745 ms *
 6  81.46.0.17  38.746 ms  52.124 ms  69.724 ms
 7  * 176.52.253.93  55.098 ms *
 8  5.53.0.176  65.955 ms
    5.53.0.110  78.607 ms  48.093 ms
 9  108.170.253.225  114.364 ms
    108.170.253.241  134.007 ms
    108.170.253.225  42.631 ms
10  142.250.232.7  56.630 ms
    142.250.214.41  38.121 ms
    74.125.253.203  49.488 ms
11  8.8.8.8  37.857 ms  66.030 ms  81.046 ms

I also just tried a traceroute on my phone: 5G vs Wi-Fi; The Wi-Fi shows similar results to this vs 5G

Thank you for the help

riahc8

While I THINK I might have a slight idea what is happening...I have no idea or clue how to solve it.

Is there a Discord server?

Gertjan

@riahc8 said in After switching to pfSense, ping is VERY slow:

1 192.168.254.2 1.414 ms 1.279 ms 1.285 ms
2 * * *
3 * * *
4 81.46.76.185 57.189 ms

The nearly first hop already adds a 57 ms.
Your uplink / downlink is really 1,5 Mbits/sec ?

You've tested https://www.waveform.com/tools/bufferbloat ?

stephenw10

Yeah, if your WAN connection is actually 1.5Mbps then I wouldn't expect to see anywhere near 1ms to anything external. I assume that's DSL? The 30ms you were previously seeing is probably about right but what was that to?