]> git.ipfire.org Git - thirdparty/bird.git/commit
Nest: Treat VRF interfaces as inside respective VRFs
authorOndrej Zajicek <santiago@crfreenet.org>
Wed, 23 Aug 2023 13:55:31 +0000 (15:55 +0200)
committerOndrej Zajicek <santiago@crfreenet.org>
Wed, 23 Aug 2023 14:08:40 +0000 (16:08 +0200)
commite3c0eca95642a846ab65261424a51dd99d954017
treee108f29222cd8b62a40f7b05360c05b9f34d3b9a
parent5121101136cb80151a9361c63dc4822afeb44eef
Nest: Treat VRF interfaces as inside respective VRFs

Despite not having defined 'master interface', VRF interfaces should be
treated as being inside respective VRFs. They behave as a loopback for
respective VRFs. Treating the VRF interface as inside the VRF allows
e.g. OSPF to pick up IP addresses defined on the VRF interface.

For this, we also need to tell apart VRF interfaces and regular interfaces.
Extend Netlink code to parse interface type and mark VRF interfaces with
IF_VRF flag.

Based on the patch from Erin Shepherd, thanks!
nest/iface.c
nest/iface.h
nest/neighbor.c
proto/babel/babel.c
proto/bgp/packets.c
proto/ospf/iface.c
proto/radv/radv.c
proto/rip/rip.c
sysdep/linux/netlink.c