Ping spikes on new install
-
I performed a factory reset, and configured ONLY the WAN as a DHCP interface.
I am still seeing latency issues when pinging the internet (23ms, 23ms, 23ms, 106ms, 23ms, 23ms, 23ms, 23ms, 44ms, 24ms, 23ms, 23ms, 33ms, 23ms, 101ms) etc.
I see the same results when using my Intel PCI card NIC as WAN and also the onboard motherboard NIC.
I also see the same results after I make sure all Hardware Offloading is dissabled in the Advanced menu. My changes to /boot/loader.conf.local persisted through the factory reset. Still same latency issues.
I do not see these issues when am pinging directly from the TalkTalk modem. The cable between the two is around 1M long. Really can't think what the issue is.. Any other ideas here would be greatly appreciated. Could it be an issue with the Apollo Lake? I read some people have issues with this with newest pfSense. Didn't read anything about latency spikes though.
Edit: Managed to get into the BIOS and changed C-States from C6 to Disabled. STILL getting the latency spikes. Anything else I may be able to change in the BIOS? Everything will be default apart from now c-states.
Thanks -
Are you using any of the altq traffic shapers?
-
Are you using any of the altq traffic shapers?
Everything is unchecked in firewall-> traffic shaper. I am using a completely out of the box install here with WAN and LAN configured.
Thank you -
-
Fresh install 2.4.2. Only config is LAN/WAN ports and:
-
Everything is unchecked in firewall-> traffic shaper->By interface
-
All three Hardware Offloading settings are Disabled
-
Added the following to /boot/loader.conf.local:
net.isr.maxthreads=1
hw.igb.num_queues=1
machdep.hyperthreading_allowed="0" -
powerd is not running
-
BIOS: CPU C States Support = Disabled
-
-
So having read all this, the only thing I can think of is the ethernet port on your ISP router maybe?
i.e. when you test from your ISP router, are you testing from a device plugged into it, or from it directly?
What I mean is that running a ping on the router itself might be telling you "the router is fine" when actually if there's a problem with the router that causes latency/issues only on it's "LAN" port (the port you plug your pfSense into) you won't see it.
What if you plug a laptop into the TeamTalk device and test using it? Does that show you the latency spikes?
Also, what if you remove "the internet" from the equation and configure two laptops. One pretends to be the Internet and one is a LAN client, then you ping between the laptops via the pfsense (you'll need two NICs on your pfSense box)
Does that show you latency?
-
@muppet:
So having read all this, the only thing I can think of is the ethernet port on your ISP router maybe?
i.e. when you test from your ISP router, are you testing from a device plugged into it, or from it directly?
What I mean is that running a ping on the router itself might be telling you "the router is fine" when actually if there's a problem with the router that causes latency/issues only on it's "LAN" port (the port you plug your pfSense into) you won't see it.
What if you plug a laptop into the TeamTalk device and test using it? Does that show you the latency spikes?
Also, what if you remove "the internet" from the equation and configure two laptops. One pretends to be the Internet and one is a LAN client, then you ping between the laptops via the pfsense (you'll need two NICs on your pfSense box)
Does that show you latency?
Hi muppet, thanks for your time. I did come to the same thought but unfortunately disproved it by:
*** Plugging Windows laptop into TalkTalk Router directly, and pings were fine-
I also have latency on the LAN
-
Running FreeBSD on the server seems to work fine regarding latency**
-
-
So even ping between two laptops, via pfSense, shows the problem?
Can you post the output of dmesg? I'm not a FreeBSD guru, but maybe we can spot something in there that might be the cause of the problems.
-
@muppet:
So even ping between two laptops, via pfSense, shows the problem?
Can you post the output of dmesg? I'm not a FreeBSD guru, but maybe we can spot something in there that might be the cause of the problems.
Unfortunately so :( and strange that FreeBSD live USB didn't have the problems! Must be some sort of setting in PfSense
Me neither re FreeBSD guru but I thank you for having a skim over incase!
Here's the output https://pastebin.com/3wCFpKqW -
I'm completely lost for ideas now, may have to scrap pfSense and go back to DD-WRT :'( Or at least buy a new motherboard/processor combination…
Any suggestions for ITX motherboard/CPU that has AES-NI and a proven record of being good for pfSense? Or alternatively any other troubleshooting options to test the LAN/WAN latency issues
I've also tried setting the Cryptographic Hardware from BSD Crypto Device to None, to no avail :(
Thank you all -
Maybe try disabling MSX-I and/or Flow Control?
https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards
Also try running using a RAM disk (System->Advanced->Misc), maybe your pfSense writing logs to disk causes the system to pause/freeze up for a moment?
These are all just stab-in-dark guesses now :(
-
Hi all, this is my first pfSense build and have noticed some issues with ping spikes while gaming. The issue is not severe - it seems that I have random ping spikes (around three in my last test of 100 pings to 8.8.8.8 ). The latency will be around 24 or 25 and then will shoot up to the hundreds or even 200 ms then go straight back down again.
…Hi,
Delayed answer, but in case someone else is struckling with same problem…
I had exactly same issue for months, and tried to find cause from every component in network. Yet it was my pfsense hardware afterall.
Solution:
disable 'Monitor M-Wait' in bios
Could be under Features tab > CPU ConfigurationAt least work with my Zotac Ci-327