Recent Realtek Gigabit cards are nice.  The ones with the bigger buffers.

Pick Halo2 in the wizard.  It uses the same ports.  Meanwhile I commited a "Xbox 360" option which is identical to Halo 2 but added it for completeness.

Yes Make a queue for pc1 and 2, edit that queue to have a max as described above, set it to have a priority of 3 or so just make it smaller then the next queue you will make. Make another queue for pc3, edit that queue to have the max described, give it a priority of 5. Go status > Dhcp server > and statically map the macs of those three computers to an IP under aliases make an alias for each group Make rules that tell each alias to go to its corresponding queue, make sure to make both an inbound and an outbound rule for both. The aliasing is optional, but will make it more dynamic and easier to change in the future.

We still got this problem, about once a day the router barely working. We caught a queue graph (when the router is stinky) and we saw a huge lanack speed. (300-1000Kbit/s) We do not have a rule which use the ack queues, expecting default ack queue. I think we found the problem. Do you have any idea? I made some tests with Traffic Shaper and I think we found the ideal speedlimit. We will try to reconfig the pfsense from default setting.

qwanack is quite small. Please have a look at http://wiki.pfsense.com/wikka.php?wakka=TrafficShapingGuide&show_comments=1#comments Also, try qwanroot = 600 kb/s, qlanroot = 4800 kb/s. Sometime it helps.

do not crosspost that is not helping !!

Ok Thx

databeestje has added a penalty option that exactly does this integrated as additional step in the wizard. Give it a try: http://forum.pfsense.org/index.php/topic,3135.msg18892.html#msg18892

@Helix26404: Hmm. Tell me if my logic is correct: if the WAN interface is shaped properly, and the traffic flows over the VPN (which goes out the WAN interface), will that traffic be shaped? It will be shaped as part of one class.  Although, since the tunnel originates from the pfSense box and our shaper setup classifies traffic as it enters the LAN interface so it can be appropriately shaped going out the WAN, what you'll likely see is the VPN traffic hitting the default class on the way out.  This would apply to both the traffic outbound from your network, but also the traffic inbound to your network.  At some point, I'd love to see the layer 7 changes I was working on completed so we can dynamically move traffic to appropriate queues.  But until that's done, I don't expect we'll be able to shape VPN traffic of any kind properly. –Bill

hmmm this give me nothing … As I understand each queue has a anchor... I'd like to display traffic currently attached to the queue... I mean source IP dest IP and using ports... thanks for any suggestions. Michael

I have a few newer files which might be of help. They need more testing. And it seems I can borrow some of your time for a bit :-) replace /usr/local/www/wizards/ traffic_shaper_wizard.inc and traffic_shaper_wizard.xml with the files from my site. http://iserv.nl/files/pfsense/?M=D Those should work. Any comments please.

I think this could have a great for some individual user control…a few questions though since I don't speak polish... Nazwa which I'm assuming is username checked against the user file...? Is the mac address is what is checked in authentication, or the username, or both? Anyways, I'll look at it, I'm not the best in the world at this kind of thing though.

we have only 1300/250 kbit/s. We have about 100 computers going to the Internet and a web server accessed from the Internet. 1300 : 8 = 162 kbyte /sec 250  : 8  = 31,5 kbyte /sec 162 / 100 pc's = 1,62kbyte /sec pro pc 31,5 /100 pc's = 0,315 kbyte /sec pro pc this is slow real slow I want to put P2P connections to the lowest priority possible. So, I used only default, ACK and P2P queues. you need more queu's sins p2p can chanche its ports to non standerd p2p ports so then  the p2p trafic is comming in the default queues and using up all youre upload speed when this happends alt-q will drop packets to make room

for this to work you need a lot of manuel tweeking of the trafic shaper rules the som of the total defined ip's up and download speeds can not be more then the speed of youre line so with a 3000 kb/sec line you can define maximum 10 clients with 300 kb/sec if you define 11 of them then the shaping stops

Hello! I think if you activate FTP-Proxy Helper at your LAN and put a firewall rule to permit your traffic from your LAN to 127.0.0.1 (localhost pfSense FTP-Proxy) you will by-pass your Traffic Shaper. Like this, port 21 and dynamic ports for FTP access will not be in your queues. Best regards, Josep Pujadas

hmm I do not want to block P2P, that is simple with snort ruleset… I'd like to limit these type traffic effectively. Will be great to redirect all P2P to separated designated queue. Nowdays I have lot off outgoing P2P traffic on http port, beside I'm trying to shape fairly all traffic.

oh thanks! i did a search on usage login in this forum but only come across non-related stuffs… will read into the details!