diff options
| author | Ondrej Zajicek <santiago@crfreenet.org> | 2023-08-23 15:55:31 +0200 |
|---|---|---|
| committer | Ondrej Zajicek <santiago@crfreenet.org> | 2023-08-23 16:08:40 +0200 |
| commit | e3c0eca95642a846ab65261424a51dd99d954017 (patch) | |
| tree | e108f29222cd8b62a40f7b05360c05b9f34d3b9a /proto/ospf/iface.c | |
| parent | 5121101136cb80151a9361c63dc4822afeb44eef (diff) | |
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!
Diffstat (limited to 'proto/ospf/iface.c')
| -rw-r--r-- | proto/ospf/iface.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/proto/ospf/iface.c b/proto/ospf/iface.c index 87e3d95e..dd922b00 100644 --- a/proto/ospf/iface.c +++ b/proto/ospf/iface.c @@ -1227,7 +1227,7 @@ ospf_reconfigure_ifaces2(struct ospf_proto *p) WALK_LIST(iface, iface_list) { - if (p->p.vrf_set && p->p.vrf != iface->master) + if (p->p.vrf_set && !if_in_vrf(iface, p->p.vrf)) continue; if (! (iface->flags & IF_UP)) @@ -1276,7 +1276,7 @@ ospf_reconfigure_ifaces3(struct ospf_proto *p) WALK_LIST(iface, iface_list) { - if (p->p.vrf_set && p->p.vrf != iface->master) + if (p->p.vrf_set && !if_in_vrf(iface, p->p.vrf)) continue; if (! (iface->flags & IF_UP)) |