Hi Jan, > Is someone actively maintaining the router plugin?
I'm not a big fan of the router plugin. The starting point of the router plugin is "how can you take an unmodified routing protocol implementation and make it work with VPP". That leads to all kinds of complexities as the two methods they tried shows. If we change the premise does the solution space look better? I think we could change the routing protocol implementation to talk directly with VPP's API for interfaces / interface events, it programs the VPP FIB directly. Then it could send and receive packets somewhat similar to what we have for the punt Unix domain socket. We might need a better punt path mechanism, where a Linux application can register for a particular IP protocol (like 89 for OSPF) on a particular interface. But that should be easy to do. I did have a brief chat with David Lamparter of Quagga fame and he had thought about doing it in a similar way. What is your particular use case? Is it just a routing protocol you need? Best regards, Ole -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8886): https://lists.fd.io/g/vpp-dev/message/8886 View All Messages In Topic (2): https://lists.fd.io/g/vpp-dev/topic/16973079 Mute This Topic: https://lists.fd.io/mt/16973079/21656 New Topic: https://lists.fd.io/g/vpp-dev/post Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656 Group Home: https://lists.fd.io/g/vpp-dev Contact Group Owner: vpp-dev+ow...@lists.fd.io Terms of Service: https://lists.fd.io/static/tos Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub -=-=-=-=-=-=-=-=-=-=-=-
signature.asc
Description: Message signed with OpenPGP
