From: Harald Welte <laforge@netfilter.org>
To: Chris Green <cmg@dok.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Logging NAT translations?
Date: Sun, 1 Aug 2004 19:01:53 +0200 [thread overview]
Message-ID: <20040801170153.GC14539@sunbeam2> (raw)
In-Reply-To: <87isc7on6q.fsf@ion.xlipstream.com>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
On Wed, Jul 28, 2004 at 05:07:41PM -0400, Chris Green wrote:
> The closest I've found is nfnetlink-ctnetlink.
Yes, this should provide you with all information you need.
> Anyone know what the status of this is? I know it doesn't work with
> 2.6 and I've been told it doesn't work with recent 2.4s either.
then someone needs to do some porting/merging work... patches
appreciated ;)
This is still not in the mainline kernel, because the netlink message
format is still not stable.
> Cheers,
> Chris
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-01 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 21:07 Logging NAT translations? Chris Green
2004-08-01 17:01 ` Harald Welte [this message]
2004-08-02 15:16 ` Chris Green
2004-08-02 15:42 ` Chris Green
2004-08-02 16:11 ` Sven Schuster
2004-08-02 17:13 ` Harald Welte
[not found] ` <20040802180031.GA22839@zion.homelinux.com>
2004-08-03 15:10 ` Sven Schuster
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=20040801170153.GC14539@sunbeam2 \
--to=laforge@netfilter.org \
--cc=cmg@dok.org \
--cc=netfilter-devel@lists.netfilter.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.