Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Askar Ali Khan <askarali@gmail.com>
To: netfilter <netfilter@lists.netfilter.org>
Cc: antony@soft-solutions.co.uk
Subject: Re: Ip accounting Help--> Urgent
Date: Sat, 26 Jun 2004 13:33:10 +0500	[thread overview]
Message-ID: <a0f69e5040626013325251ac5@mail.gmail.com> (raw)
In-Reply-To: <200406260922.14221.Antony@Soft-Solutions.co.uk>

Antony www.freshmeat.net got lot of tool for ip accounting :)


On Sat, 26 Jun 2004 09:22:14 +0100, Antony Stone
<antony@soft-solutions.co.uk> wrote:
> On Saturday 26 June 2004 5:30 am, Joel Solanki wrote:
> 
> > Hello all, ANTONY ...hoping something from u :)
> 
> Good morning :)
> 
> > I am testing ip accounting on my production server for last 2 days but i
> > can sort the things. Any body if u could throw little light that would
> > be really helpful to me.
> > This is my testing results.
> >
> > # $IPT -t mangle -i eth1 -A FORWARD -s 192.168.0.2
> > # $IPT -t mangle -o eth0 -A FORWARD -d 192.168.0.2
> >
> > Results:-
> >
> > Chain FORWARD (policy ACCEPT 6853 packets, 2981K bytes)
> >  pkts bytes target     prot opt in     out     source        destination
> >  3267 1483K            all  --  eth1   *       192.168.0.2   0.0.0.0/0
> >     0     0            all  --  *      eth0    0.0.0.0/0     192.168.0.2
> >
> > I download squid-2.5.STABLE5.tar.gz from my ftp server.
> > The size of squid is 1.3M
> >
> > Now when i did upload same squid package from local machine to remote
> > ftp server it doesnt show any bytes counter in second command :--you can
> > see that above ...counters bytes are 0.
> 
> Two very obvious questions first - I don't think these will be the problem,
> but I might as well check:
> 
> 1. Is the machine you are uploading to connected via eth0?
> 2. Does the machine you are uploading to have IP address 192.168.0.2?
> 
> Both the above must be "yes" for the second rule you have (the one that's not
> apparently working properly) to count packets.
> 
> Now for the suggestion where I think you *may* have an error:
> 
> 3. Do you have any PREROUTING nat rules which mean that by the time packets
> hit the FORWARD chain, they're no longer addressed to 192.168.0.2?
> 
> A good way to answer this would be to show us the rule in your FORWARDing
> filter table which allows the connection (the upload connection which you are
> having problems measuring) to work.
> 
> I cannot think of any reason why a rule in the FORWARD mangle table would not
> see packets which are correctly being processed by the FORWARD filter table.
> 
> Regards,
> 
> Antony.
> 
> --
> "There has always been an underlying argument that we should open up our
> source code more broadly. The fact is that we are learning from open source
> and we are opening our code more broadly through Shared Source.
> 
> Is there value to providing source code? The answer is unequivocally yes."
> 
> - Jason Matusow, head of Microsoft's Shared Source Program, in response to
> recent leaks of Windows source code on the Internet.
> 
>                                                     Please reply to the list;
>                                                           please don't CC me.
> 
>


  reply	other threads:[~2004-06-26  8:33 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 [this message]
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
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=a0f69e5040626013325251ac5@mail.gmail.com \
    --to=askarali@gmail.com \
    --cc=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