From: Patrick McHardy <kaber@trash.net>
To: Patrick Schaaf <bof@bof.de>
Cc: netfilter-devel <netfilter-devel@lists.samba.org>
Subject: Re: [PATCH}: Make MARK target terminate (resend)
Date: Tue, 02 Jul 2002 15:02:10 +0200 [thread overview]
Message-ID: <3D21A452.5060302@trash.net> (raw)
In-Reply-To: 20020629120320.K4136@oknodo.bof.de
Hi.
Patrick Schaaf wrote:
>>After not receiving a response for two weeks second try:
>>
>
>Sorry. Here we go:
>
>>The attached patch adds a new option --terminate to the MARK target
>>which lets the user choose if MARK should return IPT_CONTINUE
>>(normal behaviour) or NF_ACCEPT (to terminate further rule processing).
>>
>[...]
>
>>A CONNMARK patch will follow
>>
>
>Will you also add this to LOG, ULOG, and any other IPT_CONTINUE target
>that may come up in the future? In my opinion, this is misguided, because
>it leads to much code duplication in target modules.
>
Hmm probably not :) Although i can't see why someone would like (U)LOG
to return NF_ACCEPT
you're point is clear ..
>
>
>There is already a flexible, but somewhat ugly, way to do what you want:
>create a user defined chain that first MARKs then ACCEPTs (or does whatever
>else one may want to be done after MARK). Obviously, this is a bit ugly
>because you need one such chain per MARK value.
>
Thats not really what i want to do .. especially since we need lots of
marking rules, basically everything
allowed needs to be marked with different values.
>
>The good way to do it, in my opinion, would be to permit more than one
>target per iptables rule. You could then write
>
> iptables -A somewhere -m something -j MARK --mark 1 -j ACCEPT
>
>Note that I do _not_ oppose adding your --terminate option to MARK, as a
>stopgap measure. If that is helpful now, it should be done, IMHO.
>
>However, I'd like to hear people's opinions on the multitarget approach.
>
I like that idea very much, although (like Henrik already suggested) i
favour the idea of something new
between targets and matches for IPT_CONTINUE targets ..
Bye,
Patrick
next prev parent reply other threads:[~2002-07-02 13:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-29 9:46 [PATCH}: Make MARK target terminate (resend) Patrick McHardy
2002-06-29 10:03 ` Patrick Schaaf
2002-07-02 13:02 ` Patrick McHardy [this message]
2002-06-29 10:36 ` Henrik Nordstrom
2002-06-29 12:53 ` Brad Chapman
2002-07-01 7:50 ` Balazs Scheidler
2002-07-02 14:24 ` Harald Welte
2002-07-03 11:24 ` Jozsef Kadlecsik
2002-07-03 11:36 ` Patrick Schaaf
2002-07-03 12:41 ` Fabrice MARIE
2002-07-03 14:45 ` Hervé Eychenne
2002-07-03 23:50 ` Henrik Nordstrom
2002-07-04 23:58 ` Harald Welte
2002-07-05 4:01 ` Fabrice MARIE
2002-07-05 14:21 ` Harald Welte
2002-07-05 19:25 ` Patrick Schaaf
2002-07-05 1:15 ` Joakim Axelsson
2002-07-01 9:47 ` Jozsef Kadlecsik
2002-07-01 10:11 ` Henrik Nordstrom
2002-07-01 12:08 ` Jozsef Kadlecsik
2002-07-02 15:45 ` Harald Welte
2002-07-02 13:32 ` 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=3D21A452.5060302@trash.net \
--to=kaber@trash.net \
--cc=bof@bof.de \
--cc=netfilter-devel@lists.samba.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.