From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: iptables NAT logging
Date: Tue, 06 Nov 2007 12:07:56 -0600 [thread overview]
Message-ID: <4730AD7C.6090302@riverviewtech.net> (raw)
In-Reply-To: <4730989C.4020301@bristol.ac.uk>
On 11/06/07 10:38, Jonathan Gazeley wrote:
> Yes that's correct. Per connection is fine; we just need to know which
> users were talking to what, when. Logging every packet simply isn't
> feasible (or useful) on a network that shifts 38TB every single day!
That's a LOT of traffic and will equally be a LOT of logs.
> Yes, knowing when the connection terminates is also useful, otherwise we
> won't know how long a user is connected to a server for.
That may be more problematic to detect, especially with UDP. For TCP
streams that shut down normally, you could watch for the FIN packets and
log them. However I'm not sure how to detect the non continuance of a
UDP stream, much less other protocols. The only thing that I can think
of is to watch for the lack of traffic for a specific amount of time and
presume that the connection is terminated.
I suppose you could augment the connection tracking code to log when it
expired a tracked connection. You could at least get the end of a
connection this way. However this is probably kernel coding.
> I'll let you know how this goes, although this isn't my highest priority
> project at the moment so I may not get a chance to play for a few days.
Please do, I'm interested to know fore future projects.
> Thanks a lot for your help.
You are welcome.
Grant. . . .
next prev parent reply other threads:[~2007-11-06 18:07 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 [this message]
2007-11-07 0:53 ` Philip Craig
2007-11-07 2:29 ` Grant Taylor
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=4730AD7C.6090302@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 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.