From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Dave <finalglide@gmail.com>,
netfilter@vger.kernel.org
Subject: Re: POM Xtables???
Date: Tue, 01 Jul 2008 13:43:33 +0200 [thread overview]
Message-ID: <486A1865.40106@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0807011326351.12878@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Tuesday 2008-07-01 11:46, Patrick McHardy wrote:
>
>> Jozsef Kadlecsik wrote:
>>> On Mon, 30 Jun 2008, Patrick McHardy wrote:
>>>
>>>> - LOGMARK - haven't seen it or can't remember
>>> It adds the possibility to log the mark values of the packet/corresponding
>>> conntrack entry via syslog.
>>> The feature should simply be added to the LOG target, there's no real point
>>> to keep a separated target, as far as I see.
>> I agree. In fact I already added this to ipt_LOG/ip6t_LOG in
>> 2.6.26-rc :)
>
> You only added the nfmark, and it is printed unconditionally at that,
> the latter of which I do not see as thrilling. Seems like it is time
> for a new revision? Also I think the two modules should be unified
> first.
It doesn't need a new revision, it doesn't affect the userspace
API in any way. As for the argument of parsers that might not
handle this: any parser needs to expect new things to be added
at the end of the line, otherwise its giving us no possibility
of ever extending the output, which is not reasonable.
next prev parent reply other threads:[~2008-07-01 11:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 17:54 POM Xtables??? Dave
2008-06-27 18:58 ` Jan Engelhardt
2008-06-27 20:08 ` Dave
2008-06-27 21:16 ` Jan Engelhardt
2008-06-29 2:20 ` Grant Taylor
2008-06-30 16:04 ` Dave
2008-06-30 16:20 ` Patrick McHardy
2008-06-30 20:46 ` Jan Engelhardt
2008-06-30 20:52 ` Patrick McHardy
2008-07-01 9:43 ` Jozsef Kadlecsik
2008-07-01 9:46 ` Patrick McHardy
2008-07-01 11:38 ` Jan Engelhardt
2008-07-01 11:43 ` Patrick McHardy [this message]
2008-07-01 11:50 ` Jan Engelhardt
2008-07-01 11:57 ` Patrick McHardy
2008-07-01 14:05 ` Grant Taylor
2008-07-01 14:10 ` Patrick McHardy
2008-07-01 14:27 ` Grant Taylor
2008-07-01 14:34 ` Patrick McHardy
2008-07-01 14:30 ` Jan Engelhardt
2008-07-23 20:19 ` Jan Engelhardt
2008-07-23 23:21 ` Patrick McHardy
2008-07-24 8:31 ` James King
2008-07-24 9:21 ` Pablo Neira Ayuso
2008-07-24 9:43 ` Patrick McHardy
2008-08-15 8:17 ` James King
2008-08-19 11:35 ` Brent Clark
2008-08-15 8:48 ` James King
2008-06-30 21:11 ` Jozsef Kadlecsik
2008-06-30 21:47 ` Jan Engelhardt
2008-07-01 10:00 ` Jozsef Kadlecsik
2008-07-01 11:19 ` Jan Engelhardt
2008-06-30 20:18 ` Jan Engelhardt
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=486A1865.40106@trash.net \
--to=kaber@trash.net \
--cc=finalglide@gmail.com \
--cc=jengelh@medozas.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter@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