From: Pascal Hambourg <pascal@plouf.fr.eu.org>
To: Robert White <rwhite@pobox.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Full NAT forward and source routing - possible without packet marking?
Date: Sun, 2 Jul 2017 13:19:48 +0200 [thread overview]
Message-ID: <f297920c-6ca4-d912-a870-099c24674bcc@plouf.fr.eu.org> (raw)
In-Reply-To: <f3f547d7-738a-b01e-3dd1-0cc914043e79@pobox.com>
Le 02/07/2017 à 12:33, Robert White a écrit :
> On 07/02/2017 07:29 AM, Pascal Hambourg wrote:
>> Le 01/07/2017 à 22:26, Robert White a écrit :
>> I think you missed the point and focused on an irrelevant detail in the
>> OP. This topic is about advanced routing.
>
> Read the OP again. Traffic is coming in on ppp0, hitting a server
> hanging off eth1, and then the replies are supposed to go back to eth1
> and go out on ppp0.
>
> There is literally no simpler task in DNAT.
>
> This was not an "advanced routing" question, this was an "introduction
> to DNAT" level question.
Again, you missed the important point : reply packets must go out
through ppp0 but the default route is through eth0, not ppp0. Without
advanced routing, reply packets will go out through eth0.
next prev parent reply other threads:[~2017-07-02 11:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:55 Full NAT forward and source routing - possible without packet marking? Øyvind Kaurstad
2017-07-01 10:05 ` Pascal Hambourg
2017-07-01 20:26 ` Robert White
2017-07-01 22:17 ` zrm
2017-07-01 23:50 ` Robert White
2017-07-03 18:07 ` Hairpin NAT " zrm
2017-07-04 1:14 ` Robert White
2017-07-04 5:48 ` K
2017-07-04 7:07 ` Neal P. Murphy
2017-07-04 10:21 ` Robert White
2017-07-04 20:53 ` Pascal Hambourg
2017-07-04 21:20 ` Neal P. Murphy
2017-07-05 5:28 ` Robert White
2017-07-08 19:54 ` zrm
2017-07-08 21:55 ` Robert White
2017-07-02 7:29 ` Full NAT forward and source routing " Pascal Hambourg
2017-07-02 10:33 ` Robert White
2017-07-02 11:19 ` Pascal Hambourg [this message]
2017-07-02 15:58 ` Øyvind Kaurstad
2017-07-02 17:10 ` Pascal Hambourg
2017-07-02 23:20 ` Øyvind Kaurstad
2017-07-02 21:10 ` Robert White
2017-07-02 23:09 ` Øyvind Kaurstad
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=f297920c-6ca4-d912-a870-099c24674bcc@plouf.fr.eu.org \
--to=pascal@plouf.fr.eu.org \
--cc=netfilter@vger.kernel.org \
--cc=rwhite@pobox.com \
/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.