pfSense 2.6.0 High latency and packet loss.
-
@stephenw10 Yes i am using the default for ipv4 and ipv6 and added quad9 thats right.
I have not yet tested the pfSense directly to the WAN yet. I was planning to do that this afternoon to go thru my backyard with a 20 meter long network cable i have.I did test with a laptop directly connected to the modem and connection is then bad too but the ISP Ziggo tells me there is nothing wrong with the modem or connection.
This laptop directly to the modem test is a bit longer ago and in the mean time i got a new modem so will test that again also today and let you know.
@chpalmer My isp is Ziggo (The Netherlands) with 350mbps down and 35 mbps up.
The modem is a so called connectbox https://www.ziggo.nl/klantenservice/apparaten/wifi-modems/connect-boxI belief this is a DOCSIS 3.0 few weeks ago i had a very old UBEE with only ipv4. With the new Connectbox i have dual stack ipv4 and ipv6 and both work besides the high ping and stuttering.
Before i got this new modem i got a letter from my isp telling me that my modem is going to be swapped to a new more modern moden and they did and from then on i could do dual stack wich is pretty nice well besides the problems i also had with the old ubee modem.
Ubee modem was a modem only not a router.
This new Connectbox is a router switched to bridge mode. -
@gerard64 said in pfSense 2.6.0 High latency and packet loss.:
This laptop directly to the modem test is a bit longer ago and in the mean time i got a new modem so will test that again also today and let you know.
Ah, definitely confirm that first then. We have seen modems that introduce bad latency before. Though never this bad....
-
@gerard64 You'd need to check the exact model number, but it looks like the Ziggo modem may be a Puma 6 modem which are subject to enormous ping spikes:
https://pypi.org/project/compal/ -
-
-
@gerard64 Yeah from everything I can tell, that's a Puma 6 modem:
-
Yup 600ms is still very high. That's above the default 500ms that pfSense uses for gateway monitoring to indicate the gateway is down.
If you're seeing that with a laptop on the modem directly pfSense isn't going to be able to improve that much. FQ-Codel can only do so much.
However you should either set the gateway monitoring latency value to something much higher or disable monitoring for now. That will prevent pfSense restarting services repeatedly which is probably what was causing the extreme latency you saw earlier.Steve
-
@TheNarc Interesting. I am going to communicate that with my provider maybe they have a fix or i can get a other modem. I still have to read all the links in your reply but wanted to thank you first for this information. Thank you!
@stephenw10 Very helpful information. I wasn't aware of pfSense used the gateway latency to restart surten services wen it is above 500ms. That explains a lot. And nice new information about the behavior of pfSense i didn't know. Thank you!
-
-
@stephenw10 This is very helpful for me. Why didn't i think of this
Thank you again! -
I contacted my ISP and we talked about the know modem latency problems. They are sending me a other (Ubee) modem to test. So fingers crossed this Ubee modem works better
-
@gerard64 Great news! I'll be very surprised if that does not fix it. Those Puma 6 modems were a rather large scandal, largely because ISPs have not been proactive about replacing them (from what I can tell they usually only will when people complain, even though they know that they're fundamentally flawed). Good luck!
-
@thenarc yeah I noticed that i had to write and prove several times what the problems exactly was. After i posted your story about the known puma chipset latency problems a other community user pointed out to trade my modem for a Ubee type. This morning a ziggo worker confirmed the problem and offered to send me a Ubee modem. Tomorrow or the day after tomorrow i will receive the new modem. I will let you know how it goes.
-
Yessterday i recieved the new UBEE modem (UBC1318ZG).
I tested it right away. Ping peaks were still as high as before ~ 650-1000ms.A ziggo community user suggested to test again with a computer connected directly to the modem. Today i did that and ping times are way lower ipv4 was ~ 45ms and ipv6 102ms.
Then I connected the modem to my pfSense devide again and run two ping test from the pfsense device with wan source and ipv4 gateway and ipv6 from the isp. Ping was high again. so it is save to say i think this high ping is the pfsense wan problem.
Al tests are don't while running a dslreports.com/speedtest.
My pfSense device has 4x Intel i225 B3 2.5 mbps Interfaces.
Do you guys have idea's what could be the problem?
Are the network interfaces settings below correct?
-
@gerard64 Sorry to hear it, I was optimistic about the modem being the problem. Your settings look good as far as I'm aware. I don't have any experience with the Intel i225 NICs on pfsense but as luck would have it I have hardware on the way intended to replace an aging pfsense machine of mine. So I might have a point of comparison at some point, but it could still be a while before it arrives. I apologize but I don't have any other immediate ideas for diagnosis, but if I think of anything I'll certainly let you know.
-
@thenarc Well the modem seems to work well ping times are way lower wen i connect a pc directly onto it but with the modem connected to the pfSense wan ping times are high again.
That would be interesting to know how your new hardware will work out at your place with the i225 nic(s).
Thank you for your help this far.
-
@thenarc btw somebody suggested to uncheck all the offload options reboot en test again. I did that few minutes ago but ping times still high around 850ms.
-
To be cleat the 45 and 102ms latency you saw was pinging from a laptop dircetly connected to the modem to the ISPs gateway IPs?
If so that's still very high. 102ms is about what I see over a VPN from London to Austin!Steve
-
Yes laptop directly connected to the modem.
45 and 102 milliseconds still high oke thanks, good to know.I am used to peaks of > 650 ms.
Then 45 and 102 sound a lot less.Still big difference between pfSense and laptop directly onto the modem.
Wen i ping from pfsense with source wan to the isp gateway while doing a speedtest on dslreports.com ping peaks to ~ 1000ms.
I unchecked all the offloading in pfSense rebooted.
Test again no change
-
Are all of those whilst running a speedtest?
You would expect to see higher ping times when the line is congested without any shaping to prevent that.
Have you tried running a buffer-bloat test?
