We have these objectives: 1) VRF-Route leaking via zebra 2) MPLS l3VPN's via zebra and linux kernel 3) VRF leaking across the default as well Future: L3VPN over any tunnel type We discussed the cli and decided to table that for the moment as that getting infrastructure and code working in zebra was more important. Lou was going to work on the BGP pieces -> Direct from VPN safi -> VRF unicast safi -> vrf contextpublish/learns VRF routes to zebra Donald was going to work on zapi/zebra: -> Ensure code resolved labels properly when you have recursive nexthops that also have labels. -> Add new zapi submessage type ( if needed ) to route install to tell it to prefer labels donald On Tue, Jan 23, 2018 at 12:09 PM, Philippe Guibert <philippe.guibert@6wind.com> wrote:
Hi Donald, Lou,
I could not attend the meeting. Are there any notes, or presentation that could explain what will be the strategy with BGP ?
On a separate work, I came to face the issue where I need to redirect flow to a specific VRF, based on route target input. I was wondering if that work was crossing or not.
Thanks,
Philippe
On Tue, Jan 16, 2018 at 4:08 PM, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
All -
During discussions this morning w/ Lou we discovered that we are both working towards a BGP solution for Route Leaking. We have enough differences between our approaches that we need to spend some time consolidating our approach. The current plan is to have the meeting at 3:30 EDT this Friday Jan 19. If you would like to attend please let me know and I will put you on the invite for it.
donald
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev