Repository navigation
Replies: 2 comments
|
When you figure out how to do inter-VRF route leaking in FRR (and a bunch of other platforms) without going through BGP, please submit a PR (not promising I will merge it though, the current stuff works ;) As for checking for yet another feature flag, there aren't that many platforms that cannot do inter-VRF route leaking, so that belongs into quirks. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This Sunday, I was testing out topology
integration/vrf/33-vrf-common-ospfwhile implementing Cumulus NVUE OSPFv2 support in VRFsOn Cumulus (and FRR in general, similar on EOS), this yields the following:

The validation passes, but I'm seeing all sorts of BGP and IP-VPN related configs that would seem to require the bgp module - which isn't used in this topology. If not, it requires the
vrf.bgpfeature which isn't implemented for Cumulus NVUE - but there is no check/warningPerhaps
netlab/netsim/modules/vrf.py
Line 280 in a1e1076
vpn.bgpsupport?Thoughts?
All reactions