From: "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Hairpin NAT - possible without packet marking?
Date: Tue, 4 Jul 2017 17:20:50 -0400 [thread overview]
Message-ID: <20170704172050.20dcc4ac@playground> (raw)
In-Reply-To: <2a775b43-8c1d-6b48-cecf-9796b82ec753@plouf.fr.eu.org>
On Tue, 4 Jul 2017 22:53:11 +0200
Pascal Hambourg <pascal@plouf.fr.eu.org> wrote:
> Le 04/07/2017 à 03:14, Robert White a écrit :
> >
> > I've honestly go no clue why you cant use --in-interface in a
> > POSTROUTING chain.
>
> Because the POSTROUTING chains also see packets that are generated
> locally and have no input interface.
Logically, (for example) locally generated packets (that have no input interface) and packets from eth1 should equally fail to match "--in-interface eth2". In other words, a packet that has no source interface should never match any '--in-interface X' option because it clearly did not, and could not have, come in from interface X.
Of course, the implementation may present different conditions and limitations.
next prev parent reply other threads:[~2017-07-04 21:20 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 [this message]
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
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=20170704172050.20dcc4ac@playground \
--to=neal.p.murphy@alum.wpi.edu \
--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 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.