From: Bjorn Ruberg <bjorn@ruberg.no>
To: netfilter@lists.netfilter.org
Subject: Re: nat & ip accounting
Date: 27 Mar 2003 00:37:53 +0100 [thread overview]
Message-ID: <1048721873.18895.33.camel@mikke> (raw)
In-Reply-To: <004401c2f3ce$812d08e0$0200a8c0@lynx>
On Wed, 2003-03-26 at 20:32, Alexandru Coseru wrote:
>
>
> Hello..
>
> I want to see using iptables -L -v the ammount of traffic generated by each of my LAN's IP..
>
> i have masq 192.168.0.2 to 192.168.0.50...
>
> and now i want to see the traffic generated by 192.168.0.4 since the last reset of counters..
>
> How can I do that ? I want to be able to see the download and the upload ...
You will need to create an iptables rule for the specific IP, one for
outgoing and one for incoming traffic. Iptables is not able to give you
this information if you have not instructed it to store the specific
IP's connection. First the rules, then the statistics.
For your future logging requirements:
iptables -A FORWARD -d 192.168.0.4 -j RETURN
iptables -A FORWARD -s 192.168.0.4 -j RETURN
will create two new lines of traffic statistics to read from when
running "iptables -L -v", giving you information to and from the given
host, respectively. Be sure to put them somewhere early in your rule
set.
The RETURN target passes the packets back to the rest of the iptables
rule set after having counted them. Thus, these lines do not affect the
functionality of your iptables rules.
Bjørn
next prev parent reply other threads:[~2003-03-26 23:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 19:32 nat & ip accounting Alexandru Coseru
2003-03-26 21:01 ` Kim Jensen
2003-03-26 21:11 ` Rowan Reid
2003-03-26 21:51 ` Kim Jensen
2003-03-26 22:51 ` alexb
2003-03-26 23:17 ` Bjorn Ruberg
2003-03-26 21:38 ` Bjorn Ruberg
2003-03-26 22:47 ` Kim Jensen
2003-03-26 23:37 ` Bjorn Ruberg [this message]
2003-03-26 23:50 ` Bjorn Ruberg
[not found] <000f01c2f3e6$8afbca60$0200a8c0@lynx>
2003-03-26 23:04 ` Rowan Reid
2003-03-27 15:04 ` Kelly Setzer
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=1048721873.18895.33.camel@mikke \
--to=bjorn@ruberg.no \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox