High Latency on WAN only with ping to google, but not when laptop is direct connected.
-
Hi everyone, I thought I would have been able to solve this without a post, but hours of Google and forums have turned up no results for my scenario.
Here is my situation:
Version: 2.7.2
I have a small business I support with around 20 computers and a Proxmox server cluster with about 6 VMs.
PFsense box is on an old independent Dell R200. Thing has been running like a top for a decade now with no HW issues and PFsense never appears to overload it.
PFsense is up to date, and was recently set to factory defaults for a fresh start due to a network/hardware refresh.
When I ping google (or any web address or any public IP) I get latency in the range of 230-300ms.
I am doing these pings from the console or WebGUI Diagnostics > ping. I can also do them from any device on the network with almost exactly the same response times.
I just have a cable modem attached to WAN and a switch attached to LAN.Troubleshooting:
I have tried reassigning the WAN to the internal Broadcom ethernet and I reassigned to an Intel add-on card to eliminate potential driver issues or just bad/failing ports with no luck.If I eliminate the PFsense box entirely and hook a laptop directly to the cable modem my latency drops to a much more reasonable 30ms.
The LAN isn't doing anything crazy, and I have tested this after hours on many different intervals to see make sure LAN devices aren't overwhelming WAN requests.
I sure hope you all have some ideas because I really love PFsense and don't want to use anything else.
Thanks in advance!
-
Try running a traceroute and see where that latency appears in the route.
Do you see that latency on the WAN gateway monitoring?
What changed relative to the previous setup? Assuming the latency issue didn't appear there.
Do you have any sort of traffic shaping configured?
Steve
-
@stephenw10
WAN GW monitoring shows the high latency when I have it set to 8.8.8.8, but if I set it to my ISPs GW for my static IP it drops to 10ms or less.
I don't have any traffic shaping configured since it is such a small network.
I am unsure on the old network to be honest... I just had a set it and forget it for a long time until this upgrade.
Below is the tracert I ran from one of my virtual windows servers:Tracing route to google.com [142.251.15.138]
over a maximum of 30 hops:1 <1 ms <1 ms <1 ms [PFSENSE] [192.168.0.1]
2 2 ms 10 ms 6 ms syn-PUBLIC-IP.biz.spectrum.com [PUBLIC IP]
3 * * * Request timed out.
4 214 ms 212 ms 220 ms lag-59.dtr03dctral.netops.charter.com [96.34.75.188]
5 258 ms 263 ms 275 ms lag-31.crr01mtgmal.netops.charter.com [96.34.79.76]
6 216 ms * * lag-22.rcr01sghlgaao.netops.charter.com [96.34.15.24]
7 309 ms 242 ms 237 ms lag-810.bbr01atlnga.netops.charter.com [96.34.15.19]
8 274 ms 333 ms 230 ms lag-803.prr02atlnga.netops.charter.com [96.34.3.37]
9 266 ms 274 ms 266 ms 142.250.172.234
10 261 ms 278 ms 283 ms 172.253.71.67
11 223 ms 226 ms 231 ms 74.125.243.142
12 299 ms 268 ms 278 ms 142.251.51.223
13 258 ms 256 ms 269 ms 142.251.51.237
14 252 ms 246 ms 261 ms 72.14.239.237
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * ^CI thought it was odd when I ran one before and saw the huge spike just past the FW, but that doesn't explain (at least to me) why a direct connect laptop doesn't have high latency.
-
So the second hop there is the pfSense WAN IP or the ISP gateway?
Is this a new WAN connection?
We have seen some ISPs that default to some test connection profile for unrecognised devices.
-
2nd hop is the ISP GW.
Not a new connection, and it's the same IP we have had for years.Side note: we have the ISP swapping out the modem and upgrading the speed on Friday (Modem is several years old, but that still doesn't explain why the laptop acts fine).
-
Mmm, latency like that can really only be traffic shaping in pfSense, if it was something in pfSense.
Some cable modems are known to behave like that though.