You can prioritize traffic leaving an interface, but you cannot make interfaces work together and prioritize among interfaces.

Unless you're running a VoIP call center, rate limiting UDP is not an issue. Except for BitTorrent, then UDP is sensitive to to rate limiting and will function similarly to TCP.

One of the ways the traffic is limited is by slowing it down. When the limiter is "full" then traffic will take longer to get through, so you see that as increased latency. Or to put it both simply and more confusingly: There isn't a way to slow the traffic down without slowing the traffic down.

@KOM: But Ill go ahead, read and see if I can figure it out. That's how the rest of us do it.  Nobody has time to spoon-feed solutions, and you learn more by doing it yourself. Best response ever!!!

https://doc.pfsense.org/index.php/Traffic_Shaping_Guide https://doc.pfsense.org/index.php/Limiters

All of my LAN shaping works fine. While the first interface rule gets processed first, floating rules get processed before even those.

With pftop, confirm that everything is going to the proper queues. This is usually my problem. Queue bitrates on sending interface must be the lowest bitrate of the route. (I think you have success already) What you have seems like it should work. I dunno crap about IPSEC/VPN.

First off, the main issue of traffic shaping is you must set the interface to rate limit to just below the minimum amount of bandwidth you expect to have. I have a dedicated 100Mb connection, so I can safely set my bandwidth to 98Mb/s. If you have a 100Mb connection of lesser quality during peak hours, you need to rate limit to your lowest, so if you dip to 80Mb, you need to limit to 78Mb/s, or some value below 80Mb. Next problem. You cannot see into a VPN tunnel, PFSense will see a single encrypted flow. If you want to rate limit inside the tunnel, you need to set your tunnel interface to rate limit to the minimum rate you want to give the tunnel as a whole. This does mean in order to properly rate limit, you need to give it a maximum rate if you want to shape the bandwidth with something like HFSC inside the tunnel. If you don't want to artificially set a maximum, but instead want the tunnel to be able to use an "free" bandwidth, then you could probably use PRIQ or FAIRQ. I would recommend trying FAIRQ first. CoDel may also work. If we had fq_Codel or Cake, I would recommend those because they do well with fluctuating bandwidth where your interface is doing the buffering.

PRIQ doesn't need to know the bandwidth, but your interface still needs to have the bandwidth rate limited, otherwise your interface will just pump out data as fast as the interface, which is probably 1Gb/s. When data comes in faster than 1Gb/s, PRIQ will start to re-arrange packets.

Thanks Harvey, worked like a charm…

PFSense has two types of shaping, interface shapers like HFSC and limiters. HFSC can shape the egress of an interface. In other words, you can shape the data leaving your WAN and you can shape the data leaving each of your VLAN interfaces, but you cannot have your interfaces share state. Each interface does not know anything about the shaping of another interface. Some people claim there are some round-about ways to effectively share bandwidth across several interfaces, but at least for easy setups, you'll need to forget sharing bandwidth and instead just carve out dedicated bandwidth.

@stephenw10: You are probably hitting this: https://redmine.pfsense.org/issues/4326 Set the limiter on the LAN side or try a 2.2.3 snapshot where I believe a patch has now gone in: https://redmine.pfsense.org/issues/4596 Steve Steve, Thank you!  A quick scan of that bug looks like it's a good bet as to the source of the problem.  I've been pulling my hair out trying to figure out what's wrong.  Everything's working and then I insert the two limit queues into the firewall rule and everything just stops. Regards,   Fred

Ah thank you. I was trying to make sense of why such a broad rule was created by the wizard.

@mcwtim: Proper upgrade procedure is to backup your config, uninstall any packages, do your upgrade, reinstall your packages then re-import your config. RTFM  ;) Thank you, all this time and I did not know that. What must have happened was that I tried to setup traffic shaping on the old release, it failed, updated to latest, re-ran the traffic wizard and failed. Could have been that the box did not reboot. Couldn't get to a prompt on the local console .Had to have someone on site hit the power button. Client is still up. I'll build a new box and ship it to them. Thanks again TL

jr.fenol, could you create your own thread instead of spamming someone else's?

Hi Harvy, If applied to both WAN Interfaces, both WAN Queues are working for Upload. –> This should be OK. Currently, i'm not load balancing because i'm afraid for overloading 1 of the Download Lines. I want to shape the Download, and this seems to only work when the LAN Interface is selected in floating Rule.

Maybe disable ECN?