From: Amin Azez <azez@ufomechanic.net>
To: Henrik Nordstrom <henrik@henriknordstrom.net>
Cc: netfilter-devel@lists.netfilter.org,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: dangerous? Setting mark in nat table
Date: Wed, 14 Mar 2007 12:43:03 +0000 [thread overview]
Message-ID: <45F7EDD7.4070906@ufomechanic.net> (raw)
In-Reply-To: <1173868532.26913.39.camel@henriknordstrom.net>
* Henrik Nordstrom wrote, On 14/03/07 10:35:
> tis 2007-03-13 klockan 17:18 +0100 skrev Jan Engelhardt:
>
>
>> http://lkml.org/lkml/2006/8/22/26
>>
>> CONNMARK does in filter, MARK does not - I do not know what is
>> supposed to be going on.
>>
>
> It's due to the relation of the per-packet nfmark being as a channel to
> return routing information from netfilter to the kernel.
Thats exactly how I'm trying to use it, which is why I need to set it in
the nat table.
(I know that nat only applies to the first packet in a flow, I also use
CONNMARK later to save the mark combined with other data.)
> The
> per-connection conntrack mark used by CONNMARK does not have this
> property and does not need to be restricted in where it's modified.
>
> The restore operation of CONNMARK have the same restrictions as MARK as
> it too modifies the packet nfmark, and can therefore only be used from
> mangle just as MARK.
>
Now this at least makes a little sense.
Sam
next prev parent reply other threads:[~2007-03-14 12:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 15:25 dangerous? Setting mark in nat table Amin Azez
2007-03-13 15:36 ` Jan Engelhardt
2007-03-13 16:12 ` Amin Azez
2007-03-13 16:18 ` Jan Engelhardt
2007-03-14 10:35 ` Henrik Nordstrom
2007-03-14 11:02 ` Patrick McHardy
2007-03-14 12:43 ` Henrik Nordstrom
2007-03-14 12:52 ` [PATCH 1/1] " Amin Azez
2007-03-14 13:08 ` Patrick McHardy
2007-03-14 13:21 ` Jozsef Kadlecsik
2007-03-14 14:09 ` Jozsef Kadlecsik
2007-03-14 20:35 ` Patrick McHardy
2007-03-14 20:45 ` Henrik Nordstrom
2007-03-14 20:48 ` Jan Engelhardt
2007-03-14 22:21 ` Henrik Nordstrom
2007-03-14 22:58 ` Carl-Daniel Hailfinger
2007-03-14 23:02 ` Patrick McHardy
2007-03-14 23:12 ` Jan Engelhardt
2007-03-14 23:15 ` Patrick McHardy
2007-03-15 13:12 ` Roberto Nibali
2007-03-16 12:31 ` Patrick McHardy
2007-03-15 0:41 ` Henrik Nordstrom
2007-03-14 14:11 ` Amin Azez
2007-03-14 14:32 ` One unified table of nat/mangle/filter Henrik Nordstrom
2007-03-14 14:47 ` [PATCH 1/1] Re: dangerous? Setting mark in nat table Jozsef Kadlecsik
2007-03-14 16:47 ` Jan Engelhardt
2007-03-14 13:14 ` Henrik Nordstrom
2007-03-14 12:43 ` Amin Azez [this message]
2007-03-14 10:27 ` Henrik Nordstrom
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=45F7EDD7.4070906@ufomechanic.net \
--to=azez@ufomechanic.net \
--cc=henrik@henriknordstrom.net \
--cc=jengelh@linux01.gwdg.de \
--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.