pfSense 2.6.0 High latency and packet loss.

stephenw10

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?

Gerard64

@stephenw10
yes all ping tests I do are with dslreports.com/speedtest running

on dslreports bufferbloat is a D

on https://www.waveform.com/tools/bufferbloat:

3th bufferbloat test:

Gerard64

@stephenw10
Wen i setup the codel limiters like it is explained in the docs.
and then test it with a speedtest the wan stopts working all together i can't reach anything anymore on the Internet.

stephenw10

Do you see that same level of buffer-bloat with the laptop just connected to the modem?

That's a pretty bad connection if so.

Gerard64

@stephenw10
yes it is the same and yes very bad connection. That is what i try to figure out what and were is the problem exactly so i can think of the fix but before i can fix something i need to know exactly were the problem is.

First of all the internet connection is bad even with a system directly on the modem so that's what i know for sure.

Wen i connect my pfSense netwerk to the modem the ping peaks are way higher en bufferbloat also more bad.

Is there a relation between the two maybe?

Another weird thing is wen i use the codel limiter the wan blocks all traffic maybe there is a relation with the bad ping or maybe i configured the floating rule wrong of created the limiters wrong. I read them multiple times over but all seems like it is in the docs.

Cool_Corona

@gerard64 Check all cables and replace them.

Report back.

Gerard64

@cool_corona
I did all that already
tested all cables temperarly replaced them

I connected a 20 meter cable from modem to the pfSense wan. No change.

stephenw10

Do you have the captive portal enabled at all?

Gerard64

@stephenw10
I use the captive portal in a wlan network yes but not in my normal lan.

stephenw10

Ah, then you will hit this: https://redmine.pfsense.org/issues/12954
It's fixed in 2.7 and 22.05. You could upgrade to either of those as a test.

With a link exhibiting buffer-bloat that badly you probably need shaping of some sort.
You could try using an ALTQ shaper instead.

Steve