@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)

Probably better to just configure it with the method explained in this thread: https://forum.netgate.com/topic/57476/per-ip-traffic-shaping-share-bandwith-evenly-between-ip-addresses That's as fair sharing as it gets.

That’s an install on official Netgate hardware - an SG-2440. I’ve upgraded it as they arrive from pfsense, but it’s simply a factory install of the software, from the manufacturer. Jeff

@akuma1x Hey thank you, it helped a lot, I've just set things up and it worked by vlan.

Fortunately i found the problem by accident :) As my shaper config did not work i started to work on my ipv6 config. After finishing the LAN config i tried the shaper once more due to another post i found on reddit and it worked. If you hitting the same problem check your IPv6 config on your lan interface. This solved my problem. Sorry for the post a mod may delete it or keep it for helping people hitting this issue.

I've got a very similar setup as yours. Some traffic going through PIA, multi-vlans, etc. I tried the wizard with HSFC. The low priority (VPN) traffic seems to be going to the correct queue, but higher priority (Web) doesn't seem to be taking precedence, ie the low priority traffic still hogs the bandwidth. Like many, I just want a method to make the most of the bandwidth available at any given point in time. But seems it's easier said than done.

yeah that is what I was going to suggest, although the pfsense docs say to use floating rules I have always used interface specific rules for my shaping.

I spoke too soon :( Apparently the gateway field is not a matching field, but instead it forces traffic out that gateway. So, back to square one!

I think if you limit via ALTQ its not possible, because if you ommit the queue, it will use the default queue which still will have a limit set. Everything on the interface is forced through the root queue. But using the limiter (dummynet), you can choose to route per rule which is far more flexible as Derelict said.

can't limit the upload. only working is download. found the tutorial here https://forum.netgate.com/topic/107276/howto-multi-wan-traffic-shaper-with-bandwidth-limits-per-interface

how create queue for upload? I tried creating queue on wan interface like on lan interface and apply it to floating rules, direction is IN but not working.. thanks

@jimp although i have no gateway specified, i wondered whether the IPV6 configuration type i have on the LAN interface, may be the culprit. I switched it from DHCP6 to None and... bingo!! The traffic shaping error message is gone. I don’t understand much ipv6 and i remembered having changed the default setting wthout really knowning what i was doing. but since i am not really using ipv6 on my network, i didn’t care too much. That was apparently a mistake. Not 100% sure setting it to none is the right thing to do but at least, i know that influences the shapping.