From: Patrick McHardy <kaber@trash.net>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Grzegorz Nosek <blackfire@metal.art.pl>,
netfilter-devel@lists.netfilter.org
Subject: Re: MARK target extension
Date: Sun, 13 Jun 2004 22:23:08 +0200 [thread overview]
Message-ID: <1087158188.11287.33.camel@ws> (raw)
In-Reply-To: <Pine.LNX.4.44.0406091535410.4854-100000@filer.marasystems.com>
On Wed, 2004-06-09 at 15:43, Henrik Nordstrom wrote:
> On Wed, 9 Jun 2004, Patrick McHardy wrote:
>
> I do agree that it is nice to have the functionality of xor.
>
> May I propose that to solve this a userspace option is added "--xor-mark
> value", and that mask 0 is probited in --set-mark if this representation
> is used.
Seems like a good way. I'm also going to add --and-mark and --or-mark as
alternative representations. I'll post the patch before applying it to
see if everyone is happy.
> > One of my concerns was that MARK and CONNMARK should look and behave
> > the same way. We should either change CONNMARK to also use xor, or
> > change your patch to using or. Henrik, what do you think ?
>
> I have no problem adjusting CONNMARK if a acceptable notation is found. It
> has not yet been submitted to the kernel even if this has been favorly
> discussed many times already.
Yes, I know. I hope it will go in soon ..
Regards
Patrick
next prev parent reply other threads:[~2004-06-13 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 22:09 MARK target extension Grzegorz Nosek
2004-05-27 9:53 ` Patrick McHardy
2004-06-05 22:06 ` Grzegorz Nosek
2004-06-06 14:25 ` Patrick McHardy
[not found] ` <20040608073821.M38174@metal.art.pl>
2004-06-09 8:51 ` Patrick McHardy
2004-06-09 13:43 ` Henrik Nordstrom
2004-06-13 20:23 ` Patrick McHardy [this message]
2004-06-14 17:26 ` Grzegorz Nosek
2004-06-14 20:59 ` Henrik Nordstrom
[not found] <20040609222646.M64@metal.art.pl>
2004-06-10 9:59 ` 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=1087158188.11287.33.camel@ws \
--to=kaber@trash.net \
--cc=blackfire@metal.art.pl \
--cc=hno@marasystems.com \
--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.