pfSense

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.

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

I create the new limiters using the FQ_PIE scheduler and Taildrop queue.
I use the same floating rules that i use with FQ_CODEL which works fine with them.
I use separate rules for both in and out using the WAN interface
On the in rule i use action match and quick selected interface set to wan and direction set to in under in/out pipe i have qPIE_GATEWAY_IN for in and qPIE_GATEWAY_OUT for out.

On the out rule i use action match and quick selected interface set to wan and direction set to out under in/out pipe i have
qPIE_GATEWAY_OUT for in and qPIE_GATEWAY_IN for out.

After applying the changes the internet dies and stays dead even after a reboot.

I then change the floating rules back to using FQ_CODEL via qCODEL_GATEWAY_IN an qCODEL_GATEWAY_OUT and everything works normal again.

These same rules and limiters worked fine under 22.05.

This is all on hardware(not netgate) not a virtual machine.
.

I can confirm, I'm seeing this on 23.05.1 - if nothing else but the scheduler changes from FQ_CODEL to FQ_PIE under the upload/download limiters created, after saving and applying the traffic shaped interface/gateway sees progressive packet loss until it reaches 100% where it remains until the rules are disabled or scheduler reverted to FQ_CODEL. LMK if you have issues reproducing or need config/diag