You basically have two options: 1. Teach your routing protocol daemon to directly talk to VPP for configuring the FIB. 2. Do not modify the routing daemon and let VPP map routes written in the kernel.
For 1, you will need the router plugin, but for packet punting only. For 2., you will need both netlink+router plugins. The netlink plugin (which actually more like a library), shouldn't require so much changes though. - Pierre Le 26 mars 2017 à 16:31, Łukasz Chrustek <ski...@tlen.pl<mailto:ski...@tlen.pl>> a écrit : Hello, thank all of You for clarification of status router plugin. I'm trying to use vpp+dpdk as bare metal linux ruter with bgp and ospf routing protocols, goal is to make very fast router with dynamic routing protocols. Can You advice is there any other way to exchange dynamic routing information between os and vpp ? Regards Lukasz The mailman did not let my last message go through because it was too big so I am removing the previous threads to keep this message under 100KB limit. Hello, Dave and Pierre are correct, the router plugin is no longer being maintained. There was not much interest in the community for this project at the time and I have since moved on to other things. I’d be happy to help a new maintainer with any questions they may have. If you really want to just test it out, I suggest attempting to checkout a commit of VPP close to the last commit on the router plugin. Somewhere closely following VPP commit 0bfe5d8c792abcdb, “A Protocol Independent Hierarchical FIB (VPP-352)” will work (you might have to git bisect to get something that compiles right away). If necessary, I can submit a patch to remove the router plugin from the VPP sandbox with a note on the wiki page mentioning the finalization of the project. I recall there being an 8-month time limit for these the sandbox projects. -Jeff
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
