@KOM ok thanks will try that

I would tend to do it the way that Netgate suggests you do it. Put your shaping rules on WAN.

@Digital-Storm

What you are running into is this: https://docs.netgate.com/pfsense/en/latest/routing/troubleshooting-traceroute-output.html

Not specific to the use of FQ-CoDel but rather the use of policy routing in your egress floating rules. Use this guide and you should be good to go:
https://forum.netgate.com/post/807490

I will have to check it out, thanks!

Based on my limited knowledge it is working as designed.

This is based on a single queue and scheduler; you have to setup dynamic limiters to see the individual traffic streams.

Dynamic limiters would negate the benefits of FQ-Codel and/or Codel since each clients stream would be separate from the rest which would prevent the magic of Codel from happening since it would only see single streams.

@wormuths P2P.png

@Morad__T - Why not setup a limiters for this particular host / IP and then apply them to a new LAN firewall rule that controls outbound (i.e. internet bound) traffic for just that host / IP (be sure to place it above the rule that controls outbound i.e. internet bound traffic for the rest of the hosts of the LAN).

If you want to make sure that LAN traffic (which passes across the firewall) is not limited for that host / IP, place one or more additional rules above that newly created rule (that has the limiters applied), with the source being that host / IP and destination being whichever LAN / subnet you don't want speed limited. Remember firewall rules are evaluated from the top down. Essentially it would be similar to this:

Type Src Dst
Pass Host/IP Local Subnet1....N (No Limiters)
Pass Host/IP Any (Limiters Applied)
Pass LAN Any (No Limiters)

Hope this helps.

Update: The queue length only made a very minor improvement. You can leave the queue length at the default in most situations. Changes you should make is with quantum and limit. In the following script gives some recommended settings https://github.com/dtaht/deBloat/blob/master/src/debloat.sh . After the changes CoDel was more responsive and overall worked better. The recommendations for quantum is 3000 for 100M, 1514 for 10M connection, and 500 for low latency if desired. A limit setting of 1200 for 100M and 800 or 10M. And a flows setting of 2048 as an optional setting.

@fsr
Thanks a lot
Really appreciate your help and replying to my thread even a month later
Also thanks to whatever algorithm that got you to me

Why not just define the IN and OUT pipes in the first rule? I have traffic shaping defined in floating rules with "direction: in", and they seem to work just fine for downloads too. I suppose that as the firewall is stateful, you only need to match it when the LAN PC connects to the WAN, as that's when the state is created. Then, as long as the state remains, any download and upload traffic is going to the correct pipe as defined in the rule.

Did you reset all states? (or even reboot the firewall, if that's ok, just to be sure)