Re: [pfSense-discussion] Traffic Shaper wizard thoughts
On 3/21/06, Josh Stompro [EMAIL PROTECTED] wrote: I think this would be a great idea, I am also in this boat where I would like to shape on more than one interface. I realize it can be done manually, but it would be nice if the wizard took care of it. Is there any more documentation on pfsense's traffic shaping that what is listed in the monowall handbook? http://doc.m0n0.ch/handbook/trafficshaper.html I would like to limit the opt interface to 384kbits up/down and guarantee that a certain machine or machine's on the lan side get higher priority than anything else, for any traffic they send. Along with the Ack rules so that downloads don't kill latency. Since you can only shape traffic what is sent on an interface, the Wan queue has to deal with limiting traffic coming from opt1, which I don't understand how to do yet. The code to do this got backed out 9 months ago. It'll be put back in later after I get positive feedback on the current code. I'm tired of tracking down shaper bugs and trying to get the simple stuff we have working right (it should now, but I want to work on other stuff for a while - I'm kinda burnt out on it). --Bill
Re: [pfSense-discussion] Traffic Shaper wizard thoughts
Understood. Next month I'll have some free time and will try to sit down and chew through it myself to understand better. Appreciate all your work as-is! RB On 3/26/06, Bill Marquette [EMAIL PROTECTED] wrote: On 3/21/06, Josh Stompro [EMAIL PROTECTED] wrote: I think this would be a great idea, I am also in this boat where I would like to shape on more than one interface. I realize it can be done manually, but it would be nice if the wizard took care of it. Is there any more documentation on pfsense's traffic shaping that what is listed in the monowall handbook? http://doc.m0n0.ch/handbook/trafficshaper.html I would like to limit the opt interface to 384kbits up/down and guarantee that a certain machine or machine's on the lan side get higher priority than anything else, for any traffic they send. Along with the Ack rules so that downloads don't kill latency. Since you can only shape traffic what is sent on an interface, the Wan queue has to deal with limiting traffic coming from opt1, which I don't understand how to do yet. The code to do this got backed out 9 months ago. It'll be put back in later after I get positive feedback on the current code. I'm tired of tracking down shaper bugs and trying to get the simple stuff we have working right (it should now, but I want to work on other stuff for a while - I'm kinda burnt out on it). --Bill
[pfSense-discussion] Traffic Shaper wizard thoughts
Not being very familiar with the traffic shaper, I find it hard to fully grasp yet (all the queues and such), but something you might consider adding eventually is an ultra-simple shape by interface setup. For example - I have a LAN, a DMZ, and an untrusted wireless DMZ. I want the LAN and DMZ to have unfettered, top-priority access to the WAN bandwidth, and give some of what's leftover to the wireless DMZ, with a cap of, say, 512Kb/s. I _think_ I have most of this set up, but had to go through several iterations of the wizard and cutting out chunks it added in to get it where I want it. Now I have to go test. Anyone else smell what I'm standing in? Is this a bad or untenable idea? RB
