From: "Øyvind Kaurstad" <oyvind@dynator.no>
To: netfilter@vger.kernel.org
Subject: Re: Full NAT forward and source routing - possible without packet marking?
Date: Mon, 3 Jul 2017 01:20:30 +0200 [thread overview]
Message-ID: <81cc9e0e-e82b-557a-8c2f-113ea8c6a1cd@dynator.no> (raw)
In-Reply-To: <a7ef1ff2-4bd7-1f56-c127-e8f30ea05952@plouf.fr.eu.org>
>> but it still seems to me I need to leverage the connection tracking
>> with packet marking to be able to ensure the reply packets that should
>> go back out a non-default route actually does that.
>
> I'm afraid so, unless you can add a second IP address to the target device.
The target device is usually a device that I have no control over, and
in many cases it can be a device that doesn't even have the capability
to have multiple IP addresses on the physical interface.
So I'll have to treat it as a one-address blackbox.
Still feeling quite happy now, because quite a few lessons has been
learned about the inner workings of routing (and
netfilter/nftables/iptables) in Linux, so I will be better equipped to
tackle future requirements for my device (and other Linux-based devices).
For others that read this later on, while there are lots of docs on
nftables/netfilter, I came across this one as particularly useful:
https://pelican.craoc.fr/
I can't attest that it is correct in all aspects, but I liked the
diagram he drew based on the tests he did.
next prev parent reply other threads:[~2017-07-02 23: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
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 [this message]
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=81cc9e0e-e82b-557a-8c2f-113ea8c6a1cd@dynator.no \
--to=oyvind@dynator.no \
--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.