From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Ip accounting Help--> Urgent
Date: Sat, 26 Jun 2004 12:16:37 +0100 [thread overview]
Message-ID: <200406261216.37373.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <1088245438.2121.22.camel@joel.d2visp.com>
On Saturday 26 June 2004 11:23 am, Joel Solanki wrote:
> [root@joel root]# iptables -L FORWARD -t mangle -nvx
>
> Chain FORWARD (policy ACCEPT 6375 packets, 1886840 bytes)
> pkts bytes target prot opt in out source destination
> 3200 1742989 all -- eth1 * 192.168.0.2 0.0.0.0/0
> 3175 143851 all -- eth0 * 0.0.0.0/0 192.168.0.2
>
> This is the result when i uploaded to remote ftp server which is in our
> network . File Uploaded php.pdf size=1:53 MB
Looks completely correct to me.
File uploaded=1.53Mbytes
1742989 bytes shown coming from 192.168.0.2
> [root@joel root]# iptables -L FORWARD -t mangle -nvx
>
> Chain FORWARD (policy ACCEPT 8923 packets, 3794033 bytes)
> pkts bytes target prot opt in out source destination
> 4308 1803901 all -- eth1 * 192.168.0.2 0.0.0.0/0
> 4615 1990132 all -- eth0 * 0.0.0.0/0 192.168.0.2
>
> This is the result when i download squid.tar.gz from ftp server which is
> in my network. file size is 1.25MB
File downloaded = 1.25Mbytes
1990132-(some allowance for the traffic already counted) bytes shown going to
192.168.0.2
I see no discrepancies here.
> This is according to your suggestion but i have used the ftp server
> which is in my network. I havent used ftp server of my linux server on
> which iptables and nat is done.
Hang on a minute!
Are you saying that the FTP server you are trying to count the traffic from/to
is *on* the netfilter machine!?
Well, first of all, you shouldn't be running applications on your firewall,
and secondly, all the rules we've been talking about are in your FORWARD
chain - they will count packets routed *through* the machine, not packets
sent to or from the machine itself.
If you want to count traffic to & from the machine itself then you need to put
the rules in INPUT and OUTPUT.
Regards,
Antony.
--
These clients are often infected by viruses or other malware and need to be
fixed. If not, the user at that client needs to be fixed...
- Henrik Nordstrom, on Squid users' mailing list
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-06-26 11:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 3:49 Ip accounting Help Joel
2004-06-23 9:01 ` Antony Stone
2004-06-23 10:57 ` Joel
2004-06-23 11:41 ` Antony Stone
2004-06-24 3:29 ` Joel Solanki
2004-06-25 11:27 ` Joel Solanki
2004-06-26 4:30 ` Ip accounting Help--> Urgent Joel Solanki
2004-06-26 8:22 ` Antony Stone
2004-06-26 8:33 ` Askar Ali Khan
2004-06-26 9:20 ` Joel Solanki
2004-06-26 9:29 ` Antony Stone
2004-06-26 9:55 ` Joel Solanki
2004-06-26 10:23 ` Joel Solanki
2004-06-26 11:16 ` Antony Stone [this message]
2004-06-26 11:40 ` Joel Solanki
2004-06-23 9:16 ` Ip accounting Help Dharmendra T.
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=200406261216.37373.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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