2009/5/30 Henning Brauer <[email protected]>:
> * Anton Maksimenkov <[email protected]> [2009-05-30 07:58]:
>> In the last stage I want implement automatically creation of subqueues
>> by using some keyword for parent queue. For example:
> I don't think that is the right approach.
If so, isn't it ugly to create about 252 queues and each rule must be
multiplied 252 time to put each dst IP in it's queue?
That's impossible to do without some automatization. Ok, It may be
script which create some "blowed" pf.conf from template. But template
(and so the rules) itself becomes less understandable...
> to write code, you have to read a lot of code first.
By the way, I already done some ;-). As you may seen, I provided a new
conception:
...
I imagine to add SLIST_QUEUE into struct pf_altq for keeping "qid"s
and "index number"s of child queues (automatically created). Then I
plan to add creation of child queues into function 'eval_pfqueue' (in
pfctl_altq.c). And "qid"s and "index number"s of these created queues
will be stored in SLIST_QUEUE of parent rule ("pq").
So, in pf_test() instead of searching child queue by name I can just
walk through r->...(SLIST_QUEUE)... and get one with needed "index
number" (with index_number == i_diff, see my "patch" in first mail)
and use it's qid.
...
Anyhow, I see that my idea is not welcomed and so it will not be
commited. I think I'll drop it.
--
antonvm
