Thomas Jacob wrote:
Thats one of the things I also want to add (halfway finished yet).
Jumps are regular verdicts in my new design and verdicts can be
gathered though lookups in sets, hashes etc. So you could do:
unnamed ... -j { 192.168.0.1:chain_1, 192.168.0.2:chain_2, ...}
Great news, that's more or less what I'm looking to do.
Would those plans also include some way to incrementally
manipulate these verdict sets, maybe like:
unnamed ... -j dstset:targets
settool --name targets --add 192.168.0.10:chain_10
?
Not implemented yet, but I'm probably going to add this as an option
(since it may affect the choice of data structure). For jumps its
tricky though because loop detection has to be performed.
It would be great to have this in shape by next year, but I won't
promise anything. Should be doable though.
Looking forward to be an avid beta tester then ;-)
Great :)
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
