From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: rule is ignored for the localhost
Date: Tue, 17 Jun 2008 09:16:31 -0500 [thread overview]
Message-ID: <4857C73F.1090406@riverviewtech.net> (raw)
In-Reply-To: <4857C443.8080502@plouf.fr.eu.org>
On 06/17/08 09:03, Pascal Hambourg wrote:
> I beg to differ. AFAIK packets routed through the loopback interface
> don't go through the nat/PREROUTING chain, so the latter rule will never
> match any packet. My understanding is that only packets creating a new
> yet unconfirmed connection go through the nat chains, and the connection
> is confirmed right after the POSTROUTING chains, before the packet is
> looped back into the PREROUTING chains. I have the feeling that
> conntrack and NAT on loopback is somehow dodgy.
>
> So the rule must be added to the OUTPUT chain :
>
> iptables -t nat -I OUTPUT -o lo -p tcp --dport 30099 -j DNAT --to
> 192.168.10.119:22
I'll mostly agree with you (based on my (mis)understandings) on the
OUTPUT verses PREROUTING chain and the fact that only the first packet
in a connection pass through the nat table.
However I believe the dodyness is at least partially do to the kernel
treating the loopback subnet special. If I were to bind 192.0.2.1 to
the loopback or dummy interface and try to NAT them, I'd need to use the
OUTPUT chain for locally generated traffic.
Grant. . . .
prev parent reply other threads:[~2008-06-17 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 19:41 rule is ignored for the localhost Artem Y. Pervin
2008-06-16 20:49 ` Grant Taylor
2008-06-17 14:03 ` Pascal Hambourg
2008-06-17 14:16 ` Grant Taylor [this message]
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=4857C73F.1090406@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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