From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: James King <t.james.king@gmail.com>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: Targets with "mangle" table limiting (Was: Re: Troubles with MARK target in 2.6.28)
Date: Fri, 16 Jan 2009 08:33:52 +0100 [thread overview]
Message-ID: <49703860.1020805@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0901151744020.20619@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Thursday 2009-01-15 14:47, Patrick McHardy wrote:
>>>> Namely that MARK.2 is available for all tables. It looks like an error,
>>>> given that the previous ones were all limited to the mangle table.
>>>> But, I would have to ask - what do we gain from limiting it to mangle?
>>>> [...]
>>>> I could imagine it having to do with routing (nfmark can be used as
>>>> a routing key, as can TOS/DSCP):
>>>> [...]
>>>> What do others think?
>> Agreed, it doesn't make sense to restrict it to mangle only.
>>
> Are there perhaps other targets besides MARK whose table restriction
> should be relaxed?
I can think of CONNMARK, CLASSIFY, TCPOPTSTRIP for consistency with
TCPMSS and possibly CONNSECMARK (after consulting with James Morris).
next prev parent reply other threads:[~2009-01-16 7:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86617ABF8F494F2A940C18251E3DC8D0@Hakkenden>
2009-01-12 6:19 ` Troubles with MARK target in 2.6.28 Patrick McHardy
2009-01-12 7:08 ` Patrick McHardy
2009-01-12 7:15 ` Jan Engelhardt
2009-01-12 7:18 ` Patrick McHardy
2009-01-14 5:39 ` Jan Engelhardt
2009-01-15 8:06 ` Targets with "mangle" table limiting (Was: Re: Troubles with MARK target in 2.6.28) Jan Engelhardt
2009-01-15 12:08 ` James King
2009-01-15 13:47 ` Patrick McHardy
2009-01-15 16:44 ` Jan Engelhardt
2009-01-15 22:38 ` James King
2009-01-16 8:04 ` Patrick McHardy
2009-01-18 7:32 ` James King
2009-01-16 7:33 ` Patrick McHardy [this message]
2009-01-16 8:15 ` Jan Engelhardt
2009-01-16 8:19 ` Patrick McHardy
2009-01-18 7:08 ` James King
2009-01-19 14:29 ` Patrick McHardy
2009-01-15 13:57 ` Troubles with MARK target in 2.6.28 Patrick McHardy
2009-01-15 14:06 ` Pablo Neira Ayuso
2009-01-15 15:51 ` Jan Engelhardt
2009-01-15 15:54 ` Patrick McHardy
2009-01-15 15:58 ` Jan Engelhardt
2009-01-15 16:03 ` Patrick McHardy
2009-01-15 16:20 ` Jan Engelhardt
2009-01-16 7:33 ` Patrick McHardy
2009-01-16 8:14 ` Jan Engelhardt
2009-01-12 18:12 ` Nikolay S. Rybaloff
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=49703860.1020805@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=t.james.king@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).