Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: bytes counting
Date: Fri, 23 Apr 2004 16:04:32 +0100	[thread overview]
Message-ID: <200404231604.32275.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <086C43C9A9A1A541BFDFABCFDA05F58901448BAB@mailnew.tecnun.es>

On Friday 23 April 2004 2:42 pm, Arrizabalaga, Saioa wrote:

> Hello everyone,
>
> I have been reading some mails in this listing and it is said the best
> place to count bytes/packets is the mangle table, but I have a problem.
>
> iptables -A POSTROUTING -t mangle -o eth2 -s 192.168.0.50
>
> With this rule I catch all the packets going from 192.168.0.50 to eth2,
> but I don't know where to put the rule to catch the packets going from eth2
> to 192.168.0.50, because as far as I can see it, when I put the rule:
> iptables -A PREROUTING -t mangle -i eth2 -d 192.168.0.50 nothing is
> caught because the packet has not been SNAT-ed yet. Am I wrong?

You are not wrong, no, so put the rule in the FORWARD mangle table - then you 
will see all the packets with their real addresses.

PS: If you don't have a FORWARD mangle table, then upgrade your version of 
netfilter :)

Regards,

Antony.

-- 
Christmas was just an opportunity to upgrade to kernel 2.6 while no-one was 
around to notice the downtime.

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-04-23 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 13:42 bytes counting Arrizabalaga, Saioa
2004-04-23 15:04 ` Antony Stone [this message]
2004-04-23 17:22 ` Joao TERRA
2004-04-23 17:54   ` Antony Stone
2004-04-23 20:13     ` Joao TERRA
2004-04-23 20:27       ` Antony Stone

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=200404231604.32275.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