From: Pascal Hambourg <pascal@plouf.fr.eu.org>
To: Serge Kosyrev <skosyrev@ptsecurity.ru>
Cc: netfilter@vger.kernel.org
Subject: Re: DNAT on loopback
Date: Sat, 31 Aug 2013 12:33:58 +0200 [thread overview]
Message-ID: <5221C696.4070301@plouf.fr.eu.org> (raw)
In-Reply-To: <87vc38taw7.fsf@wintermute.ptsecurity.ru>
Hello,
Serge Kosyrev a écrit :
>
> Is it possible to DNAT locally-originated, locally-destined packets to a
> non-local destination?
Sometimes, but not alway.
> The use-case is port forwarding to a locally-routed VM guest.
> For externally originating access the following is adequate:
>
> iptables -t nat -A PREROUTING -d external.iface.ip -p tcp --dport 80 -j DNAT --to-destination target.ip.add.ress
>
> A logical complement for locally originating accesses would have been:
>
> iptables -t nat -A OUTPUT -d 127.0.0.0/16 -p tcp --dport 80 -j DNAT --to-destination target.ip.add.ress
>
> ..but all I can observe is silent packet disappearance, which I presume
> takes place during routing decision-making immediately following the
> processing by the OUTPUT chain of the nat table.
Yes, packets are discarded because the output interface is non-loopback
and the source address is within 127.0.0.0/8, which is restrited to
loopback. Unfortunately you can only change the source address in
POSTROUTING, which comes too late.
> So, is it possible at all, or should I go the userspace port forwarding way?
It is possible if the original source adress is not within 127.0.0.0/8.
For local destinations the default source adresse is the same as the
destination, but some applications allow to specify a different address.
However why don't you use the same destination address external.iface.ip
as in the PREROUTING rule, so that the default source adress would not
be a loopback address ?
prev parent reply other threads:[~2013-08-31 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 14:10 DNAT on loopback Serge Kosyrev
2013-08-31 10:33 ` Pascal Hambourg [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=5221C696.4070301@plouf.fr.eu.org \
--to=pascal@plouf.fr.eu.org \
--cc=netfilter@vger.kernel.org \
--cc=skosyrev@ptsecurity.ru \
/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