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...

Add a rule to shape ICMP traffic and send it to the highest priority queue.

So I have looked into this a bit more, and read up on ALTQ etc. I understand now a bit more about how it works, and why you can only shape traffic the leaves an interface (because if you think about it once the traffic has entered the interface its already there and used up the bandwith). What I would like to know though is if I have multiple VLANs assigned to the same physical interface, can I think add a queue to that interface and shape all the traffic across the multiple VLANs? Regards Ben

diagnostics > backup/restore, remove the ".txt" of the file name before upload to the firewall i also recomend to update pfsense to the lastest version

Just noticed this relatively old thread - is the OP still affected/interested?

There isn't a mechanism to do custom fields there. If you open a ticket at http://redmine.pfsense.org and explain this there, it can probably be added. If you want to test it first, you can edit usr/local/www/guiconfig.inc and add it to the array $firewall_rules_dscp_types there.

Hi, I think you should use floating rules for this. They apply before interface specific rules. Regards, Joel.

Don't bother trying to shape the inbound voip traffic - you have no real control over that.  Try to set a reasonable guess for the uplink speed and prioritize the voice traffic…

I haven't tried this in 2.0, but on 1.2.3 all you had to do was run through the wizard and set the WAN interface bandwidth to the limit you want, say 60Mbit, and then activate at least one other shaper action (like prioritizing DNS), and then the queues and rules that were made would accomplish that limiting. You could use a limiter on 2.0 to do that, but you'd have to make sure that all of your traffic in and out of WAN was run through that limiter. Probably with a floating rule on WAN would be easiest.

I with you on this one…I'm confused with how to setup. I've tried a few things and have run into trouble... I'm running a fiber connection with 15Mbps is both directions. I want to guarantee 100 kbps UP/DOWN to my VoIP device but cannot seem to figure it out. I've used the new wizards but it appears to setup only in one direction. Also, for me, it appears that once I use the wizard the default queue is already maxed without moving any traffic... I'm running 2.0RC1. It appears that the wizard doesn't QoS in both directions. Is there a reason for this? Hopefully someone will point us in the right direction...

I'm running 2.0 and I was able to prioritize the whole tunnel and shape traffic within the tunnel. Its still a work-in-progress but it can be done with 2.0… I did have to assign interfaces for the OpenVPN tunnels. Its been a while but i thought it if you assign interfaces to your OpenVPN tunnels within 1.2.3, you can prioritize the whole tunnel. But I can be wrong, been a while since I worked on 1.2.3

yes  he's right, you need to pick one other thing in the wizard,  like prioritize your outbound DNS.  that will be enough for the wizard to complete and is not a bad idea to have set anyway.

i set it up manually and it seems to work well now.  set the default as lowest and all my torrents are going there, and elevated priority through the floating rules for services i use (ie html, pop3, etc) anyone looking for a read on traffic shaping should give this a go, helped me alot: https://calomel.org/pf_hfsc.html

You might have better luck on 2.0 using limiters (pipes) with hard limits, and direct the traffic into them instead of traditional shaper queues.

2.0 is taking quite a bit longer than anyone expected, but we won't bind a cycle to a given date just for the sake of releasing it. It'll be ready when it's ready. :-) Hopefully the cycle will be much shorter for 2.1, but 2.0 is very ambitious, so much was added and changed it's taking quite a while to shake out all the bugs.

On my 1.2.3 pf system I run the shaper wizard and selected a few games from the list for higher priority then changed the mapped ports and names to the ports I actually wanted to use. This seems to work fine. Teamspeak Witch is already in the wizard (I host a server) and I Host an Urban Terror server . I have 6 other users that at any time could be using the connection for what ever 1 pounding on xbox live ( also shaped) and more on the lan playing Urban with 3 to 4 connecting from the internet to Urban and teamspeak. I also selected a few services I don't use to lower priority and most of the rest selected and left to normal. I have tested it by down loading a couple of torrents while we are all playing and the wan side players seemed fine.