From: Patrick McHardy <kaber@trash.net>
To: johnpeng <johnpeng@unitytek.com.tw>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Multiple calls of check functions
Date: Mon, 02 Apr 2007 14:52:52 +0200 [thread overview]
Message-ID: <4610FCA4.10208@trash.net> (raw)
In-Reply-To: <20070402123757.8117C948BF@stinky.trash.net>
johnpeng wrote:
>>No, that has always been the case. Every rule you add results in an
>>entire new ruleset from the kernels POV, so each rule is completely
>>validated again.
>
>
> This means that we need use some flag (in the targetinfo) in the check
> function to block the process of some code-flow if we want to the code-flow
> to be processed only one time?
Depends on what you want to do.
>>The SAME target is obsolete and SNAT should also uses the same IPs
>>for the same source nowadays, so I'd suggest you simply use SNAT.
>>
>
>
> Because I want to use multiple ranges of SAME, however, multiple range has
> been removed from 2.6 ... any solution, thanks!!
Mhh .. maybe use multiple SNAT rules and balance using the statistic
match.
next parent reply other threads:[~2007-04-02 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070402123757.8117C948BF@stinky.trash.net>
2007-04-02 12:52 ` Patrick McHardy [this message]
[not found] <20070402110756.409EE9489E@stinky.trash.net>
2007-04-02 11:28 ` Multiple calls of check functions Patrick McHardy
2007-04-02 12:37 ` johnpeng
2007-04-02 9:22 johnpeng
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=4610FCA4.10208@trash.net \
--to=kaber@trash.net \
--cc=johnpeng@unitytek.com.tw \
--cc=netfilter-devel@lists.netfilter.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.