From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH 4/7] xt_mark match rev 1
Date: Mon, 17 Dec 2007 14:08:02 +0100 [thread overview]
Message-ID: <476674B2.8050808@netfilter.org> (raw)
In-Reply-To: <47666FF4.6040102@trash.net>
Patrick McHardy wrote:
> Pablo Neira Ayuso wrote:
>> Jan Engelhardt wrote:
>>> What will netlink bring us, with respect to the two states:
>>> - old iptables, new kernel
>>> - new iptables, old kernel
>>> so matching some UUIDs (and .revision is one, more or less) seems
>>> like the way
>>> to go.
>>
>> Netlink doesn't stick us to fixed structure layouts as it happens to the
>> current interface since we represent the messages kernel <-> userspace
>> in TLV (type-length-value) format. Thus, userspace and kernel won't
>> share structures and new features just require a new type. For that
>> reason, the netlink interface won't require such revision infrastructure.
>>
>> Not that I'm against your patches, I'm just stating the right direction
>> to go for those 5-10 years that you have mentioned. And of course, we
>> don't have a single line of such interface at the moment :)
>
>
> Actually we do, I've been working on it, but had to interrupt
> for some other stuff. I hope to get back to it over christmas
> and beginning of next year. The goal is to add a compat layer
> for old iptables userspace, but I don't really care about how
> ugly it gets since we hopefully never have to look at it again
> until its removal :)
Cool, consider putting it somewhere, I'm willing to contribute to it ;).
BTW, if nobody complains I'll release iptables 1.4.0 final between today
and tomorrow.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next prev parent reply other threads:[~2007-12-17 13:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 2:35 [PATCH 1/7] Use %u format specifiers Jan Engelhardt
2007-12-07 2:36 ` [PATCH 2/7] Introduce nf_inet_address Jan Engelhardt
2007-12-11 10:16 ` Patrick McHardy
2007-12-15 12:06 ` Jan Engelhardt
2007-12-15 16:21 ` Jan Engelhardt
2007-12-17 12:52 ` Patrick McHardy
2007-12-17 12:28 ` Patrick McHardy
2007-12-17 12:51 ` Jan Engelhardt
2007-12-17 13:00 ` Patrick McHardy
2007-12-07 2:40 ` [PATCH 3/7] xt_connlimit rev 1 Jan Engelhardt
2007-12-11 10:19 ` Patrick McHardy
2007-12-15 12:20 ` [PATCH 3/7] Let xt_connlimit use nf_inet_addr Jan Engelhardt
2007-12-17 12:33 ` Patrick McHardy
2007-12-17 12:52 ` Jan Engelhardt
2007-12-17 12:54 ` Patrick McHardy
2007-12-07 2:41 ` [PATCH 4/7] xt_mark match rev 1 Jan Engelhardt
2007-12-11 10:25 ` Patrick McHardy
2007-12-15 12:28 ` Jan Engelhardt
2007-12-15 15:55 ` Pablo Neira Ayuso
2007-12-15 16:10 ` Jan Engelhardt
2007-12-15 16:42 ` Pablo Neira Ayuso
2007-12-15 21:26 ` Jan Engelhardt
2007-12-17 12:49 ` Patrick McHardy
2007-12-17 12:47 ` Patrick McHardy
2007-12-17 13:08 ` Pablo Neira Ayuso [this message]
2007-12-17 13:44 ` Patrick McHardy
2007-12-17 12:37 ` Patrick McHardy
2007-12-17 12:55 ` Jan Engelhardt
2007-12-07 2:41 ` [PATCH 5/7] xt_MARK target rev 2 Jan Engelhardt
2007-12-11 10:27 ` Patrick McHardy
2007-12-15 13:59 ` Jan Engelhardt
2007-12-15 14:47 ` Jan Engelhardt
2007-12-07 2:42 ` [PATCH 6/7] xt_connmark rev 1 Jan Engelhardt
2007-12-07 2:42 ` [PATCH 7/7] xt_CONNMARK " Jan Engelhardt
2007-12-11 10:13 ` [PATCH 1/7] Use %u format specifiers 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=476674B2.8050808@netfilter.org \
--to=pablo@netfilter.org \
--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).