You can do that with the squidGuard package on top of squid.

It lets you setup ACLs to match groups of IPs, and lists of sites can be set to pass/block based on the members of those groups.

There are several tutorials here on the forum and wiki for setting up squidGuard.

I see, my intention was to run everything on that box (a firewall, gateway and seedbox) and my idea was to catch all the traffic from the seedbox using an alias IP and then set it to go to the P2P traffic shaping queue but the filter can't catch the traffic going out the WAN on the box itself, wether its an alias IP or the real lan IP, just any upload or traffic going out the WAN iface initiated from the pfsense box itself is bypassing the traffic shaper according to my tests.

It does works with incoming traffic, i can see the incoming packets to the alias IP being caught and queued into the P2P queue, but unfortunately it seems it doesn't work the other way for outgoing packets. So, i guess i'll have to think on doing this in some other way, perhaps deploying pfsense using vmware ESX or some other virtualization technology so i'd run pfsense + a separate OS on the same box to get the seedbox traffic shaped.

Thanks again for clearing up this :)

It does not seem like your traffic shaper is even initialized properly.

Have you tried re-running the shaper wizard?

If all else fails, you can set the queues and rules manually.

so experts ?

i tried to do it configuring first a limiter and then using http video in the layer 7 section of trafic shaper and choose the limiter i created for this protocole. but didn't work.

i even tried on the lan interface to activate the limiter at the bottom of the pic, in front of ' l-7' advanced option ( i think) but also no result. help please !

ps : i have 2 interfaces : 1 wan and 1 lan

I've not used that.  I just prioritize RTP traffic, so I have no info on your issue, sorry…

@kirlox_kitoy:

It is the wizard configuration that set the values of 1 and 25 percent

I thought in 1.x the wizard sets default queues = 10% and ack queues = 10% (and 1% to the real-time bandwidth).

Anyway qwandef=1% is too small to suppress qP2P (unless you don't want to) and qwanack=25% is much larger than necessary for a symmetric link. I would prefer something like 5%-20% and 5%-10%, respectively.

Graphs tell you nothing about accuracy of the shaper. Queue loads should be calculated from systematic measurements with pftop.

TCP traffic needs to acknowledge that it received a packet. That is what the qAcks is for. UDP traffic doesn't acknowledge that it received a packet. If you look at the rules you will see that TCP traffic uses qACKs/qGames while the UDP traffic only uses the qGames queue.

good to hear!!

@ay01:

maybe it's little out of subject but i was asked to find out how to implement pfsense into an active directory server. is anyone has an idea about it ?

or in other word, how can pfsense features be usefull for me when implementing it into an active directory server.

search the forum, search http://doc.pfsense.org then post a new topic in the correct section…

Sir, can i boost my web browsing and download by modifying my qwanacks? which will i tweak the qlanacks or the qwanacks? I cant picture it out it seems that queues are still the same when i try to tweak it by percentage or by bandwidth.

hi everyone. i'm trying to understant what does " the httpvideo " or the "httpaudio" protocols means or how do pfsense work with so that the traffic shapper can lower the video downloads on web pages or the audio download etc.

i'm working on a project about l7 filtring and i choosed pfsense to demonstrate and explain l7 filtring. i work on pfsense 2.0 RC1 on virtuals machine on vm ware and i need to shape traffic beetween lan interface and wan interface.

anw, that's why i want to understand how do httpvideo in 'l7' section into the trafic shapper works.

thanks you and hope a quick answer.

didn't work, can you send me your rules? Maybe i'm missing something…

One more thing, the problem seems to occur only with UDP traffic, the activity i'm seeing on the qgames wan is TCP traffic...