From: David Ahern <dsahern@gmail.com>
To: Stephen Suryaputra <ssuryaextr@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Matching unbound sockets for VRF
Date: Sun, 3 Apr 2022 10:24:36 -0600 [thread overview]
Message-ID: <2bbfde7b-7b67-68fd-f62b-f9cd9b89d2ad@gmail.com> (raw)
In-Reply-To: <YkBfQqz66FxYmGVV@ssuryadesk>
On 3/27/22 6:57 AM, Stephen Suryaputra wrote:
>
> The reproducer script is attached.
>
h0 has the mgmt vrf, the l3mdev settings yet is running the client in
*default* vrf. Add 'ip vrf exec mgmt' before the 'nc' and it works.
Are you saying that before Mike and Robert's changes you could get a
client to run in default VRF and work over mgmt VRF? If so it required
some ugly routing tricks (the last fib rule you installed) and is a bug
relative to the VRF design.
next prev parent reply other threads:[~2022-04-03 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 17:19 Matching unbound sockets for VRF Stephen Suryaputra
2022-03-25 14:13 ` David Ahern
2022-03-27 12:57 ` Stephen Suryaputra
2022-04-03 16:24 ` David Ahern [this message]
2022-04-04 12:41 ` Stephen Suryaputra
2022-04-05 14:32 ` David Ahern
2022-04-07 21:28 ` Ben Greear
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=2bbfde7b-7b67-68fd-f62b-f9cd9b89d2ad@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ssuryaextr@gmail.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 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 NNTP newsgroup(s).