Thanks Bill!
It seems that if i get some free time I'll attempt to fix that
function to be recursive, and I'll let you know.
Meanwhile the config the wizard generates is a pretty good start for everything.
On 10/9/05, Bill Marquette <[EMAIL PROTECTED]> wrote:
> On 10/9/05, Szasz Revai Endre <[EMAIL PROTECTED]> wrote:
> > Okay, so I linked the qWanRoot and qLanRoot to the overallWan and
> > overallWan respectively, each of them being "parent queues" (parents
> > to the real root queue(hfsc))
> > but this is the generated config(rules.debug )
> >
> > altq on fxp1 hfsc queue { qWANRoot }
> > altq on fxp0 hfsc queue { qLANRoot }
> > queue overallLAN bandwidth 100Mb priority 5 hfsc { qLANRoot }
> > queue overallWAN bandwidth 100Mb priority 5 hfsc { qWANRoot }
> >
> > the overallLAN, and overallWAN should have been the parent queues
> > which are only children to the `real root queue(hfsc)` and nothing
> > else.
>
> Yep. You and I are getting the same thing.
>
> > If I were to modify rules.debug by hand, could the system then use
> > that? How would I load that configuration up?
> >
>
> pfctl -f /tmp/rules.rules.debug
> and
> /sbin/pfctl -a {$queue['name']} -f /tmp/{$queue['name']}.rules
>
> on each of the rules files in /tmp.
>
> Any reboots and any webgui change will likely blow your manual configs away.
>
> --Bill
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
