From: "Gáspár Lajos" <swifty@freemail.hu>
To: Kamal <kamash@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: NAT POSTROUTING accounting
Date: Mon, 16 Oct 2006 16:03:20 +0200 [thread overview]
Message-ID: <45339128.4010609@freemail.hu> (raw)
In-Reply-To: <8a1be4700610160622q533ac28di9ab37f5735ddd554@mail.gmail.com>
Kamal írta:
> This is one way, but isn't there a more graceful way other than
> putting duplicate entries in NAT POSTROUTING & mangle POSTROUTING.
>
> Thanks
>
Hmm... I do not understand you clearly... What do you mean "more
graceful"... ? :)
1. You may do some changes on the packets... (SNAT/DNAT, etc...)
2.a. You have to mark or identify the packets you want to count in other
chains ... (MARK target or direct rules)
2.b. You can use the mangle POSTROUTING chain for counting specified
packets because this is the "last" chain BEFORE every packet leaves the
system.
(I know that there is a "raw" table...)
So... How do you want to do it "more graceful" ?
Swifty
next prev parent reply other threads:[~2006-10-16 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 14:43 NAT POSTROUTING accounting Kamal
2006-10-15 18:09 ` Martijn Lievaart
2006-10-16 12:00 ` Kamal
2006-10-16 12:28 ` Gáspár Lajos
2006-10-16 13:22 ` Kamal
2006-10-16 14:03 ` Gáspár Lajos [this message]
2006-10-16 17:40 ` Kamal
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=45339128.4010609@freemail.hu \
--to=swifty@freemail.hu \
--cc=kamash@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.