Hi, Did you change the priority of DNS in the wizard? I noticed (months ago, also with 2.0) that DNS request from my pfsense box to external NS servers does not work if I set the priority of DNS to high in the wizard. Never got an answer why this happened?

Thank you very much!

I have ended up flashing my slingbox back to factory code.  I then moved the connection directly to the firewall on a switch that was directly connected.  It connect at a odd speed just like my vonage device which runs at 10/half.  Now it is working fine.  I still would like to setup QOS for this to give it higher priorty so we don't have so much lag. RC

In 1.2.3 there is a limit that you are hitting. This has been upped quite a lot in 2.0

you can use layer7 for this. Just create a regex for facebook and map it to the queue pipe you want. The only problem is you cannot filter on https and that's most of their traffic now days.

Solution found in this post: How to set the limited bandwidth for client ? http://forum.pfsense.org/index.php/topic,33160.msg172696.html#msg172696

In firewall/traffic shaper /limiter section in ur web-guy create 2 pipe with the speed u need to limit. in mask field use "destination" for both pipe. now in firewall/rules/lan section create a rule with following action–------pass interface ------lan protocol-------any(to shape all kinds of traffic) source-------------(single host or alias)  ip address u want to shape destination----------any now in advance features ------in/out tab click on "advance" & select 1 pipe for in field & other for out. dont use same pipe for both. now save & apply change. now in firewall/rules page put this rule to above the default rule. done for 1 ip. you may confused about the mask of pipes as they are both destination. dont worry they will work.

@jimp: Use the single WAN multi LAN wizard, and enter 1 for the number of LANs. That works. Thanks for the advise, just tried and still no luck. "You do not have 1 of local interfaces!"

The point of QoS is NOT to have the queues build up, not use all the bandwidth, so if you keep accepting packet at the maximum rate (and thus increasing latency for incoming packets), it's already to late to do shaping, the packets already arrive with a delay. You can't control what packets are sent to you directly.

You can manage and control bandwidth through conference manager application. This will allow the minimum bandwidth required for video conferencing and will not make the whole system busy

So it reaches 100% CPU?  ??? If so, polling might help: http://blog.pfsense.org/?p=115

Thank you!  That makes complete sense to me now.