From: "Kaloyan Kovachev" <kkovachev@varna.net>
To: Patrick McHardy <kaber@trash.net>,
Jan Engelhardt <jengelh@computergmbh.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: new target or new option
Date: Mon, 1 Oct 2007 10:04:06 +0300 [thread overview]
Message-ID: <20071001065330.M72816@varna.net> (raw)
In-Reply-To: <46FD3DF2.10709@trash.net>
On Fri, 28 Sep 2007 19:46:26 +0200, Patrick McHardy wrote
> Jan Engelhardt wrote:
> > On Sep 28 2007 20:06, Kaloyan Kovachev wrote:
> >
> >>Hello,
> >>i need to mark the connection with the realm number, but it seems there is no
> >>'easy way' and there should be separate rule for each realm.
> >>
> >>Are there any plans to add this functionality and which is the preferable way
> >>to go:
> >> 1) create new REALMCONNMARK target with and/or mask
> >
> >
> > Yeah, since there is already an xt_realm, a xt_REALM would be
> > the logical counterpart.
>
> The realm belongs to the route, it can not be changed.
>
> I'm currently working on the netlink based iptables successor,
> perhaps we should split matches into a "collector" part that
> gathers the data and some generic range/mask/... matching.
> That would allow to tell a target like CONNMARK to gather
> the data from somewhere else.
Great, this will also replace IPMARK, IPCLASSIFY etc with only common targets
MARK, CONNMARK and CLASSIFY. It would be good to use the same sintax for match
and for the mark value i.e. if the entry is a macth return true or false and
if it is in the target - return the matched value.
next prev parent reply other threads:[~2007-10-01 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 17:06 new target or new option Kaloyan Kovachev
2007-09-28 17:36 ` Jan Engelhardt
2007-09-28 17:46 ` Patrick McHardy
2007-10-01 7:04 ` Kaloyan Kovachev [this message]
2007-10-01 6:52 ` Kaloyan Kovachev
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=20071001065330.M72816@varna.net \
--to=kkovachev@varna.net \
--cc=jengelh@computergmbh.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.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 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).