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:09:00 +0200 [thread overview]
Message-ID: <66f644e4-81fd-140d-c242-989baec01d8a@dynator.no> (raw)
In-Reply-To: <5e96bc48-550c-4ec1-e0c4-5a929a456012@pobox.com>
>> My device is not meant to be a system (or full blown) router per se. It
>> is a specialized custom device that for some cases needs to be able to
>> act as a router. It does not act as a DNS server, and in most cases
>> there will be other routers in the system (at least on the eth0 network,
>> and my device is usually set up as a DHCP client on eth0).
>
> That's as "router-ish" as routers get. Don't think of it as "not a
> full-blown router". It may be expected to only have a light packet load
> but that doesn't make it anything less than a router.
I get what you're saying, and I don't really disagree, it's just that on
this device there's still quite a few things missing (on purpose) that a
"full blown" router has. Hence I said what I did.
> First I am going to juggle your addresses a little to get your device
> (and all of eth1), that is the inner protected network ("PRO") out of
<detailed explanation snipped for brevity>
Thanks for writing down all of that. It is useful, even though I
actually had most of it down working already. As also mentioned in the
subject, the real point of this thread was to find out if packet marking
is actually the best/easiest way to solve my problem, and both you and
others have confirmed that now.
I'm also using nftables (as mentioned in the OP), so the rules you used
in iptables are different than mine. The principles are the same though
(and netfilter is of course still the underlying framework), so your
answer is still useful as a guide to where and when.
I've struggled with this for quite some time, and it is a relief to
finally have a better grip on it.
> Again, apologies. Being told I missed "something" wasn't as helpful as
> being told what thing I missed. /D'oh
No apologies needed. You've been very helpful, to misunderstand is only
human. :-)
prev parent reply other threads:[~2017-07-02 23:09 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
2017-07-02 21:10 ` Robert White
2017-07-02 23:09 ` Øyvind Kaurstad [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=66f644e4-81fd-140d-c242-989baec01d8a@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.