From: Patrick McHardy <kaber@trash.net>
To: Nishit Shah <nishit@elitecore.com>
Cc: 'Thomas Jacob' <jacob@internet24.de>, netfilter-devel@vger.kernel.org
Subject: Re: Plans for future iptables versions / jumpset feature
Date: Fri, 23 May 2008 14:15:30 +0200 [thread overview]
Message-ID: <4836B562.6000302@trash.net> (raw)
In-Reply-To: <00d501c8bccb$d7922000$86b66000$@com>
Nishit Shah wrote:
> Hi,
> I am also looking/working for same thing as something like
> "jumpset", even discussed with Patrick in last workshop regarding how to do
> it, but it looks difficult to me by just seeing at code or understanding the
> code without the overall impact.
> It would be nice if someone can share the idea of how to do it or
> give a lead for how to proceed.
Basically, you'd change (in ipt_do_table):
int newpos = t->verdict;
to get the new position from the target module. This probably
requires to change the target function signature. Alternatively
you could try to encode it in the verdict. Loop detection
needs some way to get all possible jumps from the target
and check each possible path. Maybe the easiest way is probably
a target built into ip_tables.c
next prev parent reply other threads:[~2008-05-23 12:15 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
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 [this message]
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=4836B562.6000302@trash.net \
--to=kaber@trash.net \
--cc=jacob@internet24.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=nishit@elitecore.com \
/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.