From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] NAT-aware traffic analysis
Date: Wed, 05 Sep 2007 04:00:46 +0000 [thread overview]
Message-ID: <011501c7ef71$56d6f760$0100a8c0@MingChing> (raw)
In-Reply-To: <00af01c7ef6a$1c8a3560$0100a8c0@MingChing>
From: "Salim S I" <salim.si@cipherium.com.tw>
> 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.
>
>
Well sort of theoretically possible but bad in pratice. If I have 300
internal users, I will have to create 300 iptable rules. Then if I
want to analyse based on sport or dport, you can imagine the
number of rules will be quite many.
Anyone has other suggestions ?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-09-05 4:00 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
2007-09-05 4:00 ` Ming-Ching Tiew [this message]
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='011501c7ef71$56d6f760$0100a8c0@MingChing' \
--to=mingching.tiew@redtone.com \
--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.