From: Richard Weinberger <rw@linutronix.de>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: Netfilter: New target: RLOG
Date: Thu, 19 Jan 2012 11:31:14 +0100 [thread overview]
Message-ID: <4F17F0F2.6060807@linutronix.de> (raw)
In-Reply-To: <alpine.LNX.2.01.1201191045530.27900@frira.zrqbmnf.qr>
On 19.01.2012 10:46, Jan Engelhardt wrote:
> On Thursday 2012-01-19 10:26, Eric Dumazet wrote:
>
>> Le jeudi 19 janvier 2012 à 10:21 +0100, Richard Weinberger a écrit :
>>
>>> Yeah, I could add --ring, --ring-size and --add-timestamp to LOG.
>>> What about a rlog_common.o which can be used by ipt_LOG and ip6t_LOG?
>>>
>>
>> or merge ipt_LOG and ip6t_LOG into xt_LOG ?
>
> yes please :)
Will do.
Thanks,
//richard
next prev parent reply other threads:[~2012-01-19 10:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 22:43 Netfilter: New target: RLOG Richard Weinberger
2012-01-18 22:43 ` [PATCH 1/5] ring_buffer: Export for_each_buffer_cpu() Richard Weinberger
2012-01-19 1:18 ` Steven Rostedt
2012-01-18 22:43 ` [PATCH 2/5] xt_log: Make printk() in sb_close() optional Richard Weinberger
2012-01-19 1:20 ` Steven Rostedt
2012-01-18 22:43 ` [PATCH 3/5] nf_log: Export dump_packet() and dump_mac_header() functions Richard Weinberger
2012-01-19 1:21 ` Steven Rostedt
2012-01-18 22:43 ` [PATCH 4/5] netfilter: Implement xt_RLOG Richard Weinberger
2012-01-18 22:43 ` [PATCH 5/5] xt_RLOG: add userspace-components Richard Weinberger
2012-01-19 9:12 ` Netfilter: New target: RLOG Pablo Neira Ayuso
2012-01-19 9:21 ` Richard Weinberger
2012-01-19 9:26 ` Eric Dumazet
2012-01-19 9:26 ` Eric Dumazet
2012-01-19 9:46 ` Jan Engelhardt
2012-01-19 9:46 ` Jan Engelhardt
2012-01-19 10:31 ` Richard Weinberger [this message]
2012-01-19 9:25 ` Pablo Neira Ayuso
2012-01-19 9:29 ` Richard Weinberger
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=4F17F0F2.6060807@linutronix.de \
--to=rw@linutronix.de \
--cc=eric.dumazet@gmail.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rostedt@goodmis.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.