From: George Alexandru Dragoi <waruiinu@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: How to "catch" FORWARD packets in POSTROUTING chain?
Date: Mon, 16 Aug 2004 05:25:28 +0300 [thread overview]
Message-ID: <3063e504081519253f1a7b1f@mail.gmail.com> (raw)
In-Reply-To: <1515101522.20040816035759@op.pl>
As long as you can "catch" it in FORWARD, i see no reason to catch it
in POSTROUTING, but if you still want this, try that
iptables -t mangle -A FORWARD -j MARK --set-mark 0x1
iptables -t nat -A POSTROUTING -m mark --mark 0x1 .... do stuff
On Mon, 16 Aug 2004 03:57:59 +0200, Marcin Sura <slacklist@op.pl> wrote:
> Hello
>
> I have lan (10.0.0.0/8) and server (10.1.1.1 for lan, dynamic ip
> from my ISP). I use MASQUERADE to allow lan computer connects to
> internet. eth0 connects to lan, ppp0 for internet.
>
> All traffic lan <--> internet passes through FORWARD chain. How
> can I "catch" this traffic in POSTROUTING chain?
>
> --
> Pozdrawiam
> Marcin mailto:slacklist@op.pl
>
>
--
Bla bla
next prev parent reply other threads:[~2004-08-16 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 1:57 How to "catch" FORWARD packets in POSTROUTING chain? Marcin Sura
2004-08-16 2:25 ` George Alexandru Dragoi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-16 2:23 Jason Opperisano
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=3063e504081519253f1a7b1f@mail.gmail.com \
--to=waruiinu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox