All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Thomas Jacob <jacob@internet24.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Plans for future iptables versions / jumpset feature
Date: Thu, 22 May 2008 22:18:25 +0200	[thread overview]
Message-ID: <4835D511.7030503@trash.net> (raw)
In-Reply-To: <20080522201419.GA28832@internet24.de>

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 :)



  reply	other threads:[~2008-05-22 20:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 19:00 Plans for future iptables versions / jumpset feature Thomas Jacob
2008-05-22 19:18 ` Patrick McHardy
2008-05-22 19:57   ` Jan Engelhardt
2008-05-22 20:15     ` Patrick McHardy
2008-05-22 20:27     ` Thomas Jacob
2008-05-22 20:14   ` Thomas Jacob
2008-05-22 20:18     ` Patrick McHardy [this message]
2008-05-22 20:47       ` Thomas Jacob
2008-05-22 20:51         ` Patrick McHardy
2008-05-22 21:43           ` Thomas Jacob
2008-05-23 11:55   ` Nishit Shah
2008-05-23 12:15     ` Patrick McHardy
2008-05-23 12:47       ` Thomas Jacob
2008-05-23 13:28         ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4835D511.7030503@trash.net \
    --to=kaber@trash.net \
    --cc=jacob@internet24.de \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.