All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Salim S I" <salim.si@cipherium.com.tw>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] NAT-aware traffic analysis
Date: Wed, 05 Sep 2007 03:36:48 +0000	[thread overview]
Message-ID: <000e01c7ef6d$fdb611f0$91021d0a@SalimSi> (raw)
In-Reply-To: <00af01c7ef6a$1c8a3560$0100a8c0@MingChing>

A different approach is to use iptables counters in FORWARD chain (-s
$CLIENT_IP -i eth0 -o ! eth0). That would require a  rule for each user.


-----Original Message-----
From: lartc-bounces@mailman.ds9a.nl
[mailto:lartc-bounces@mailman.ds9a.nl] On Behalf Of Ming-Ching Tiew
Sent: Wednesday, September 05, 2007 11:09 AM
To: lartc@mailman.ds9a.nl
Subject: [LARTC] NAT-aware traffic analysis


I have tried using iptraf for my NAT firewall to analyse the IP traffic.
Basically I am faced with this difficulty of related the source IP
to the outgoing interface to the internet, so I am wondering if
anyone has a suggestion for a different ways to do it, or a suggestion
for a better tool.

Details :-

Supposed : eth0 - LAN
                   eth1 - WAN1
                   eth2 - WAN2

And then all source IPs in the LAN are SNAT to the respective
WAN interface when leave for internet. There are also DNAT
traffic from internet to the LAN.

I want to breakdown the statistic of LAN users using the
internet. If I run iptraf on eth0, I will see the LAN stats, but I
don't know for sure which one really go out to which WAN
( some traffic does not even go out to the WAN at all ! ).

Then when I sniff at eth1 or eth2, I lost the information about the LAN
IPs.

How could I do a stateful or NAT-aware traffic analysis ? Anyone has
a good suggestion ?


--------------------------------------------------------
Important Warning! 

*************************** 

This electronic communication (including any attached files) may contain
confidential and/or legally privileged information and is only intended
for the use of the person to whom it is addressed. If you are not the
intended recipient, you do not have permission to read, use,
disseminate, distribute, copy or retain any part of this communication
or its attachments in any form. If this e-mail was sent to you by
mistake, please take the time to notify the sender so that they can
identify the problem and avoid any more mistakes in sending e-mail to
you. The unauthorised use of information contained in this communication
or its attachments may result in legal action against any person who
uses it.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2007-09-05  3:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05  3:09 [LARTC] NAT-aware traffic analysis Ming-Ching Tiew
2007-09-05  3:36 ` Salim S I [this message]
2007-09-05  4:00 ` Ming-Ching Tiew
2007-09-05  4:20 ` Martin A. Brown
2007-09-06  5:42 ` Marco Aurelio
2007-09-06  5:56 ` Ming-Ching Tiew
2007-09-06 18:20 ` Marco Aurelio

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='000e01c7ef6d$fdb611f0$91021d0a@SalimSi' \
    --to=salim.si@cipherium.com.tw \
    --cc=lartc@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.