Does it work in 1.01 and 1.2.1? Thanks jigp Davao City

Okay… after some more testing, here goes.  Please correct me if I'm wrong! It seems that what breaks the RRD graphs is when I put in rules to shape the OPT1 interface.  It also seems to cause the odd bug with the queue status page as well. Odd thing is, that even though traffic shaping from what I'm reading does not work on multiple interfaces, it still seems to be working, as without the added rule, all OPT1 traffic goes to the default queues, which kinda makes shaping not work well for what I'm wanting to do. So, the odd thing is that I'm reading that pfSense's traffic shaper does not support shaping over more than LAN/WAN interfaces, but if what I'm looking at is right, then it indeed does work, but it just screws up the queue status page and the RRD graphs. Considering I may just be reading things incorrectly, can anyone confirm/deny this?? [Edit] I think I might have figured out what was going on with the queue status page.  Now, I'm not a guru, nor do I have a lot of experience and knowledge, but I can think fairly logically, and I've been muddling over the problem here and there throughout the week, and I think I figured it out. When we make a rule that includes another interface, I think the queues are being duplicated which would use that interface.  Would kinda make sense the way I was thinking about it, and would explain the oddity on the queue status page, and may explain somewhat why the RRD graphs are broken. What is killing me is that if what I'm seeing is correct, the traffic is entering the queue that it is supposed to when I make a few rules to shape traffic and go downloading/browsing to test it.  I'm just not sure if the queues are being duplicated, or halved, or what.  Haven't really gotten that far. Since Ermal seems to be the traffic shaping god-person here, hopefully he'll read this.  For now though, I figured my work-around was to put another box in front of the normal router with just the basic stuff, the port-forwards, and traffic shaping – then use the 'real' router to route the traffic where it should go.  Would really love to eliminate the extra box though, as I'm running out of room to stuff extra junk :P

Is 2.0 stable enough that it is passable, or should I hold out for official?  I know it is in alpha, but sometimes even alphas are pretty good :P –--Disregard this bit as I've found a work-around, but would like to know about 2.0 beign stable enough for general use?---- Hey ermal, in light of what I'm finding in the other post I have here… are you sure it doesn't work?  So far I at least notice that my roommate's torrents are now properly going into the p2p queue when I make the rule for OPT1... still alot of traffic in default queues but that may be because he has random ports in his torrent config

Set up a NAT rule in addition to the 1:1 mapping and you should get reflection for that service.

You probably want to look at the Traffic Shaping forum.

Thank you for info.

just think of it in terms of upstream and downstream and it's much easier wan = downstream lan = upstream

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