netdev - Re: Matching unbound sockets for VRF

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2bbfde7b-7b67-68fd-f62b-f9cd9b89d2ad@gmail.com>
Date:   Sun, 3 Apr 2022 10:24:36 -0600
From:   David Ahern <dsahern@...il.com>
To:     Stephen Suryaputra <ssuryaextr@...il.com>
Cc:     netdev@...r.kernel.org
Subject: Re: Matching unbound sockets for VRF

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.