Thanks - I will try this :-)

The limit is in BIT per second. Make sure that you enter the correct value. For limiting with freeradius2 as backend you have to restart CP when changing the limits and the user needs to reconnect. So in both cases try to reconnect the user on CP so that the limits can take effect.

You are correct sir.  thank you very much!

Is there some "best practices guide" in choosing between the various traffic shaping algorithms offered in ALTQ? I understand that HFSC is supposed to be the most flexible, yet also more complex to configure correctly.

I'm currently using priq i just want to limit the bandwidth going to a single ip so that it doesn't slow down the entire office when someone is uploading a video to our company server.

Delete your "Floating" rule, and create on LAN Action: pass Source: your "particular LAN IP" Dest: any and in advanced features –> In/Out  choose your limiters Put this rule "on top" of any other "pass" rule.

@cmb: Alternatively if you have a proxy server or can set one up, you can set TOS based on URL and then shape on TOS. Talking about setting TOS in Squid, there is an interesting feature called ZPH (Zero Penalty Hit) included in recent Squid versions, which can be used to set TOS of already cached content (cache "HIT") so it can be delivered to local users at full speed, i.e. only shape un-cached traffic. Is anyone using such a setup with pfsense? I just started to configure it (added zph_local to squid.conf, checked with tcpdump that squid cache HIT entries sent out packets with correct TOS set etc) and will probably complete the setup tomorrow.

Sorry for being a newbie, but can you give me step-by-step examples to your #1 and #2 answers please. It will be greatly appreciated! Thanks!

Hi thestealth, thanx for posting.

You can select PRIQ algorithm by this way Firewall -> Traffic Shaper -> by Interface -> Schedular Type . Then you must attach  the queue to proper rule.