in 2.0 is the only options as of now. There is no more tos in the selection.
There will be even a special inbound handling of DSCP(diffserv) configurable by the user to its needs.

Feeling very stupid at the moment, the reason this message was displayed was due to the fact that I was putting in the lan and WAN P2P catch-all restrictions in the wrong way round. Thats what I get for not reading things thoroughly.
However now that I have set this correctly I cannot view the queues at all. After the filters are reloaded and I click the option to view queue status a single queue shows and then the whole pfSense gui becomes unresponsive for about 10-15 minutes. If I do not use the P2P catch all setting then this problem does not occur.
Does anybody have any ideas?
Thanks,
Michael

Its simple when you upload something you congest the line and than ALTQ does its magic.
When you are in normal mode the link is not saturated and all packets flow normally.

KEEP IN MIND: ALTQ is not work conserving by nature. On 2.0 Traffic Shaper-> Limiter is the one Work Conserving.

this isn't really a real solution…but what i do is use a single headless linux box for all torrent downloads....you could do the same thing and then do ip based traffic shaping....my client of choice is torrentflux which is web based so i have the added pleasure of being able to add torrents from anywhere with a internet connection.  I then use samba to share that box with the network.

i THINK utorrent now has a web client as well so if you hate linux that's always an option....like i said, it's not a REAL solution to your problem but for me, i've found it much nicer because it gave me a good use for otherwise useless junkpile hardware.

if you have a computer sitting dusty in the corner it might be something to think about....even a p2 or p3 would be fine

No those algorithms do their jobs when the queue is overloaded and the way ALTQ works it makes it magics only when network is congested.
So make sure you do not overload you VoIP queue.

That's good. To put it best you will see some drops with traffic shaping, but a lot could be a problem.
I was looking at http://forum.pfsense.org/index.php/topic,14485.0.html

Make sure you set your up and download right.

TY

@ipnet:

OK, I found this thread where it says that is being considered for future releases.

http://forum.pfsense.org/index.php/topic,2718.0.html

This posts are dated back in 2006…

BR

@http://forum.pfsense.org/index.php/topic:

This bounty is completed, for support, head to the 2.0 board.

Thats what I thought, it was a dumb question.

I have searched the forum for the keyword transparent and came up with lots of other people asking if it will do (trasparent shaping) and its seems it will with the 1.2 version i.e. ala brided mode. I will install that tomorrow and see how it works.

Thanks for the reply…

This is still a problem for me.

Here is the shaper rule for a local IP:

This IP is only able to upload to the internet at 300kbps.  All traffic coming from this system is supposed to fall into this queue.  All of it does, unless it is a connection that is forwarded over the NAT.

Here is my NAT rule:

When someone connects over SSH (the port 22 that is forwarded) from a remote site, they are able to download files from 192.168.75.51 at the full bandwidth of our connection.  The connection is not being placed properly by the shaper rule into the proper queue that would limit its bandwidth to 300kbps.

Thanks, I was hoping there was an easier way to do it.

Anxiously awaiting the stable 2.0…  :)

@ermal:

Or it is dropping cause the queues are too short.
Without proper analysis nobody can give a propper answer.

You cannot really say that a box routes 1Gbit traffic is overloaded by ALTQ, i would just say that there is no complete information to say anything. Beaware that HZ might need to be tweaked too to handle the load.

cough Yes I can.

–Bill