And is possible regulate speed and priority for each user by their IP addresses as is in MONOWALL possibly now? Thanx.
----- Original Message ----- From: "Bill Marquette" <[EMAIL PROTECTED]> To: "RoboK" <[EMAIL PROTECTED]> Cc: <support@pfsense.com> Sent: Wednesday, December 14, 2005 3:44 PM Subject: Re: [pfSense Support] Traffic shaper question All traffic hits qWANdef and qLANdef by default unless overridden by specific rules which place that traffic in a different queue. That's why we don't need (or have) a fallthrough catch all rule. --Bill On 12/14/05, RoboK <[EMAIL PROTECTED]> wrote: > > My question is simple. What rule in RULES in Traffic Shaper "regulate" all > other traffic, that isn`t specified in this rules created by Magic Wizard ? > > You comprehend if you look on MONOWALL`s Magic Wizard created rules. You > see on the end of rules that rule, what i don`t see in pfSense. > To this rule come under all what isn`t specified above it. > > if proto source destination > target > WAN any any any > catch all > > this simmillar i don`t see in PFSENSE TS , but traffic flows normally > > In pfSENSE TS are only rules which "regulate" ..... such items as ... > Port: 6699 - 6701 or LAN net > Port: 53 (DNS) atc. > > But rule as this: > > if proto source destination > target > WAN any any any > catch all > > i don`t see but traffic flows normally. > I want to know how works TS in pfSense in spite of this. > > I don` know how explain detailed this yet :-} > Thank you very much > > ----- Original Message ----- > From: "Bill Marquette" <[EMAIL PROTECTED]> > To: <support@pfsense.com> > Sent: Tuesday, December 13, 2005 7:59 PM > Subject: Re: [pfSense Support] Traffic shaper question > > > I'm still not sure what you're asking. I assume you want queues by IP > address. We don't do that, you can manually create the queues, it'll > be painful, but it's not a feature I'm looking to add at this time and > isn't a design requirement for the shaper. > > --Bill > > On 12/13/05, RoboK <[EMAIL PROTECTED]> wrote: > > Sorry my bad question. > > Under users I mean computer with IP address or range of LAN. > > > > In MONOWALL i have specified speeds according to IP addresses of clients > on > > LAN and on the end of rules i have one common rule for on non specified IP > > from range LAN IP adresses .... etsc. > > This I don`t see in traffic shaper rules created by magic shaper wizard > of > > pfSense. Magic shaper in MONOWALL create that rule. > > Hmm. > > thanx > > > > > > ----- Original Message ----- > > From: "Scott Ullrich" <[EMAIL PROTECTED]> > > To: <support@pfsense.com> > > Cc: <[EMAIL PROTECTED]> > > Sent: Tuesday, December 13, 2005 5:24 PM > > Subject: Re: [pfSense Support] Traffic shaper question > > > > > > On 12/13/05, RoboK <[EMAIL PROTECTED]> wrote: > > > > > > Hi Bill, please, i don`t see any rule in traffic shaper, that handle > > users. > > > There are only rules that handles particular ports or services or > > protocols. > > > I didn`t see any general rule. But traffic from various clients wents > ok. > > > > The traffic shaper handles ports (services). Not users. Same as > > m0n0wall. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > ---------- > > * www.inMail.sk - Vasa emailova adresa na cely zivot ZDARMA > > * www.php5.sk - novy freehosting s php5 a MySQL, forum o php5 > > * http://interval.cz - webdesign a e-komerce denne > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
