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 10:29:36 +0100 [thread overview]
Message-ID: <200406261029.36368.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <1088241658.2283.35.camel@joel.d2visp.com>
On Saturday 26 June 2004 10:20 am, Joel Solanki wrote:
> Good morning Antone and all.
>
> LINUX SERVER eth0 200.200.200.200 (public ip) --> switch
> eth1 192.168.0.1/24 -------------> switch
>
> Yes 192.168.0.2 is the ip of windows 98 machine.
Windows 98? And it's running an FTP server???
I'm surprised...
> Chain FORWARD (policy ACCEPT 5299 packets, 1571K bytes)
> pkts bytes target prot opt in out source destination
> 2672 1461K all -- eth1 * 192.168.0.2 0.0.0.0/0
> 2627 110K all -- eth0 * 0.0.0.0/0 192.168.0.2
>
> I have tested again this rules
> I just upload squid.tar.gz which is of 1.3M. and i found the above
> results. Its only showing the 110K bytes ...file is of 1.3M and traffic
> bytes are more in other rule ..its showing 1461K. so i cant get what is
> exactly going on with this chains...
Please let's clarify which machine is doing exactly what...
You say you have a Windows 98 machine on IP 192.168.0.2
Your rules have recorded 1461kbytes *sent from* that machine to somewhere
else, and 110kbytes *received by* that machine from somewhere.
That to me is entirely consistent with you saying you have uploaded (by which
I assume you mean "sent to somewhere else") 1.3Mbytes of data by FTP.
My suggestion is:
1. Clear the counters to zero with "iptables -Z FORWARD -t mangle"
2. Download (receive) a file on machine 192.168.0.2 of some known size.
3. Check the counters with "iptables -L FORWARD -t mangle -nvx"
4. Upload (send) some *other* file of a different size from machine
192.168.0.2
5. Check the counters again.
6. Let us know if the first rule shows a byte count noticeably different from
what you sent, or the second rule shows a byte count noticeably different
from what you received.
Hope this helps,
Antony.
--
Behind the counter a boy with a shaven head stared vacantly into space,
a dozen spikes of microsoft protruding from the socket behind his ear.
- William Gibson, Neuromancer (1984)
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-06-26 9:29 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 [this message]
2004-06-26 9:55 ` Joel Solanki
2004-06-26 10:23 ` Joel Solanki
2004-06-26 11:16 ` Antony Stone
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=200406261029.36368.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