From: Rob Ert <ertr3960@gmail.com>
To: Joshua Moore <j@jcm.me>
Cc: netfilter@vger.kernel.org
Subject: Re: Netfilter, IPVLAN, L3S and NAT64
Date: Thu, 21 Dec 2023 13:48:27 -0600 [thread overview]
Message-ID: <CANn7yVbt3nqerwU-_OjKFpD56RkqdgG5aUj_5FVoR1SOi3MrBw@mail.gmail.com> (raw)
In-Reply-To: <A74105B3-C9FF-4BD3-8269-4431BBAACDEE@jcm.me>
On Thu, Dec 21, 2023 at 1:31 PM Joshua Moore <j@jcm.me> wrote:
>
> Would have to see a diagram with traffic flows illustrated to understand your use case more.
>
My setup is as described in Fig1. of the following three page document,
with my WireGuard wg0-tun-device in the default-ns:
"This can be worked-around by assigning one of the
virtual devices to the host and eliminating the
configuration on the master interface, as shown in Fig1."
https://people.netfilter.org/pablo/netdev0.1/papers/IPVLAN-The-beginning.pdf
prev parent reply other threads:[~2023-12-21 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 18:38 Netfilter, IPVLAN, L3S and NAT64 Rob Ert
2023-12-21 18:42 ` Joshua Moore
[not found] ` <CANn7yVZkCm5KbRxDhJ78TCvBwj7P2adEuqWE+0EQxHAen_YFbA@mail.gmail.com>
2023-12-21 19:12 ` Fwd: " Rob Ert
2023-12-21 19:31 ` Joshua Moore
2023-12-21 19:48 ` Rob Ert [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=CANn7yVbt3nqerwU-_OjKFpD56RkqdgG5aUj_5FVoR1SOi3MrBw@mail.gmail.com \
--to=ertr3960@gmail.com \
--cc=j@jcm.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).