From: Jonathan Gazeley <jonathan.gazeley@bristol.ac.uk>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: iptables NAT logging
Date: Tue, 06 Nov 2007 16:38:52 +0000 [thread overview]
Message-ID: <4730989C.4020301@bristol.ac.uk> (raw)
In-Reply-To: <472B3B63.7000203@riverviewtech.net>
Grant Taylor wrote:
> On 11/02/07 03:47, Jonathan Gazeley wrote:
>> My NAT solution is implemented in iptables and works fine. The
>> logging partially works but the problem is this: I am logging pre
>> NAT, and my log shows the internal IP and port, and the destination
>> IP and its port. But it does not show the port used by the NAT box to
>> talk to the external IP. Logging post NAT would never detect any
>> packets. If I was able to long pre and post NAT I would be able to
>> log all the information I need.
>
> Ugh, this could be problematic. If I understand you correctly, you
> essentially need to log the following information. I also suspect
> that it needs to be per connection NOT per packet. Correct?
>
> Internal Source IP
> Internal Source Port
> External Source IP (post NAT)
> External Source Port (post NAT)
> External Destination IP
> External Destination Port
> Protocol
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!
> I'm presuming that you are already logging when the connection
> initiates. Do you also want to log when the connection terminates?
Yes, knowing when the connection terminates is also useful, otherwise we
won't know how long a user is connected to a server for.
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.
Thanks a lot for your help,
Jonathan
----------------------
Jonathan Gazeley
ResNet | Wireless Team
Information Services
University of Bristol
----------------------
next prev parent reply other threads:[~2007-11-06 16:38 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 [this message]
2007-11-06 18:07 ` Grant Taylor
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=4730989C.4020301@bristol.ac.uk \
--to=jonathan.gazeley@bristol.ac.uk \
--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