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.
There were error(s) loading the rules: /tmp/rules.debug:32: queue
overallLAN has no parent /tmp/rules.debug:32: errors in queue
definition /tmp/rules.debug:33: queue overallWAN has no parent
/tmp/rules.debug:33: errors in queue definition pfctl: Syntax error in
config file: pf rules not loaded - The line in question reads [32]:
queue overallLAN bandwidth 100Mb priority 5 hfsc
If I were to modify rules.debug by hand, could the system then use
that? How would I load that configuration up?
>
> overallWAN and overallLAN need to be marked as parents. As do qWANroot and
> qLANroot. qLAN/WANroot need to then be set as children of overallWAN and
> overallLAN. This is, however, where I suspect you'll run into trouble. I
> don't recall offhand, how recursive I made the parent queue detection :) pf
> does support this configuration, but our code doesn't do the recursion
> correctly (just tested what you are trying). I did take a quick peek at the
> code and thought I had a workaround, but it didn't work.
>
> --Bill
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
