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: <ZzsCNUN1vl01uZcX@shredder>
Date: Mon, 18 Nov 2024 11:00:37 +0200
From: Ido Schimmel <idosch@...sch.org>
To: Ben Greear <greearb@...delatech.com>
Cc: netdev <netdev@...r.kernel.org>
Subject: Re: GRE tunnels bound to VRF

On Sun, Nov 17, 2024 at 10:40:18AM -0800, 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...

You can set eth{1,2} as the "physical device" of gre{0,1}

ip link add name gre0 up type gre [...] dev eth1
ip link add name gre1 up type gre [...] dev eth2

The "physical device" can be any interface in the VRF, not necessarily
eth{1,2}.