From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: iptables NAT logging
Date: Tue, 06 Nov 2007 20:29:19 -0600 [thread overview]
Message-ID: <473122FF.9000800@riverviewtech.net> (raw)
In-Reply-To: <47310CA5.5080901@snapgear.com>
On 11/6/2007 6:53 PM, Philip Craig wrote:
> No kernel coding needed, it already generates netlink events. You
> just need to listen for this event in userspace and log it from
> there.
Ok, it must have been a very long day. How and where would you listen
to said netlink events? Or are you referring to some sort of daemon
that would behave like a user space filtering application via netlink?
Grant. . . .
next prev parent reply other threads:[~2007-11-07 2:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 8:47 iptables NAT logging Jonathan Gazeley
2007-11-02 9:33 ` G.W. Haywood
2007-11-02 9:36 ` Martijn Lievaart
2007-11-02 14:59 ` Grant Taylor
2007-11-04 1:46 ` 李伟华
2007-11-06 16:38 ` Jonathan Gazeley
2007-11-06 18:07 ` Grant Taylor
2007-11-07 0:53 ` Philip Craig
2007-11-07 2:29 ` Grant Taylor [this message]
2007-11-07 3:01 ` Philip Craig
2007-11-07 3:06 ` Grant Taylor
2007-11-05 0:43 ` Philip Craig
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=473122FF.9000800@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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