netdev - Re: GRE tunnels bound to 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: <88c439e9-0771-4bfc-a4af-70b4be76ea1f@orange.com>
Date: Sun, 17 Nov 2024 23:41:35 +0100
From: Alexandre Ferrieux <alexandre.ferrieux@...il.com>
To: Ben Greear <greearb@...delatech.com>, netdev <netdev@...r.kernel.org>
Subject: Re: GRE tunnels bound to VRF

On 17/11/2024 19:40, Ben Greear wrote:
> Hello,
> 
> Is there any (sane) way to tell a GRE tunnel to use a VRF for its
> underlying traffic?
> 
> For instance, if I have eth1 in a VRF, and eth2 in another VRF, I'd like gre0 to be bound
> to the eth1 VRF and gre1 to the eth2 VRF, with ability to send traffic between the two
> gre interfaces and have that go out whatever the ethernet VRFs route to...

A netns is vastly more flexible than a VRF, with much cleaner operation. In your
case I'd just move each eth to a separate netns, and create its GRE there.