pfSense » pfSense Plus

After updating to 23.01 limiters using the fq_pie scheduler don't pass any traffic.

I'm using floating rules to assign traffic to the limiters these same rules work with fq_codel.
These same rules worked with fq_pie in 22.05.

I am not the only one with the problem: https://forum.netgate.com/topic/177555/fq_pie-no-internet?_=1680451711804

This is the second time i have opened a ticket on this subject.

Chris W responed to the original ticket 13996 with:

Updated by Chris W 8 days ago
I'm unable to reproduce this on a virtual machine which was upgraded to 23.01 from 22.05 (and to 22.05 from 22.01 previously). Steps I'm taking are:

1. Create a new limiter using the FQ_PIE scheduler.
2. Create a floating rule (in my case, for the LAN interface) which passes any traffic and uses th new limiter on the In pipe.
3. Disable the default allow any rule on LAN.
4. Install the iperf package in pfSense and start it as the server with the default settings.
5. Use another VM as the iperf client pointed at the pfSense LAN's IP address for the iperf server (iperf3 -c 192.168.1.1 -p 5201).

Using FQ_PIE, FQ_CODEL, and the worst-case weighted fair, iperf traffic was limited to the 100 Mb/s cap I set in the limiter. Disabling the limiter in the floating rule of course restores full bandwidth.

Are you on your own hardware? If not, I suggest contacting TAC for a 23.01 firmware image to reflash directly to that version. If you're on your own machine, it's now possible to upgrade directly to Plus 23.01 from pfSense CE 2.6, so 22.05 isn't in the picture.

In both cases, I suggest getting the system to 23.01 before importing your configuration file. If the reflash/upgrade is successful, test the limiter using the steps above (doesn't have to be a virutal machine). If that's successful,then import your configuration and test again. Marking as Not a Bug for now.

And closed the ticket without even giving me a chance to respond.

The Problem is Chris W didn't setup his limiter correctly.

He didn't add a Queue after setting up the limiter. FQ_CODEL and FQ_PIE won't work correctly without it.

Try going to a site like: https://www.waveform.com/tools/bufferbloat
and see how well it works the way he set it up it will work like crap.

He should be using a floating rule to match traffic rather then pass it. Then there would have been no reason to have to disable his default allow any rule on LAN.

I have tried to get this to work on hardware, virtual machine and a vlan nothing works.