From: Florian Westphal <fw@strlen.de>
To: Marcin Kabiesz <marcin.kabiesz@smarthost.pl>
Cc: Florian Westphal <fw@strlen.de>, netfilter@vger.kernel.org
Subject: Re: NAT translation problem - leakage of packets with original source address
Date: Thu, 10 Mar 2022 15:53:31 +0100 [thread overview]
Message-ID: <20220310145331.GD13772@breakpoint.cc> (raw)
In-Reply-To: <613d3843bf5e37cdf890b64b416471f3@smarthost.pl>
Marcin Kabiesz <marcin.kabiesz@smarthost.pl> wrote:
> My question is where do I create a rule for invalid packets? in NAT
> POSTROUTING? or MANGLE POSTROUTING or other place leaving the server? I am
> waiting for your opinion.
INVALID packets do not traverse NAT table, so NAT POSTROUTING won't
work.
I would suggest mangle postrouting or filter forward, depending on
wheter you want to include locally generated packets or not.
next prev parent reply other threads:[~2022-03-10 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 11:40 NAT translation problem - leakage of packets with original source address Marcin Kabiesz
2022-03-10 12:08 ` Florian Westphal
2022-03-10 12:33 ` Marcin Kabiesz
2022-03-10 14:53 ` Florian Westphal [this message]
2022-03-11 9:11 ` Marcin Kabiesz
2022-03-11 12:53 ` Florian Westphal
2022-03-11 13:45 ` Marcin Kabiesz
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=20220310145331.GD13772@breakpoint.cc \
--to=fw@strlen.de \
--cc=marcin.kabiesz@smarthost.pl \
--cc=netfilter@vger.kernel.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