> On Jul 1, 2019, at 4:44 AM, Steuer Heribert <ste...@patronas.com> wrote:
> 
> Hello,
>  
> I am trying to understand what the current status of the router plugin in 
> vppsb is. It seems not to compile with any recent version of VPP.
> There is  not much value in a data plane implementation without a proper 
> control plane. Can you guys please enlighten me about the current status of 
> the plugin or whether it was replaced by any other implementation that 
> enables tools like Bird or FRR to inject routes into the VPP FIB?
>  
> Thanks lot for your help,
> Heri

Heri,

First, your question has been asked and answered several times on vpp-dev:

https://lists.fd.io/g/vpp-dev/topic/issue_in_installing_router/16635086?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,16635086

https://lists.fd.io/g/vpp-dev/topic/building_router_plugin/10641656?p=Created,,,20,1,0,0::,,,0,0,0,10641656

https://lists.fd.io/g/vppsb-dev/topic/questions_about_the_router/10642802?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,1,20,10642802

There is more of this type of thing in the archives.

Second, several vendors maintain private forks of the router plugin, so it’s 
obviously possible to make it compile, and run.

This said, the router plugin is the “short path” to control plane 
functionality, but there are reasons it’s in the sandbox, and it will likely 
never be part of VPP proper.

Basically: it’s architecturally ugly, and the more you try to fix it, the more 
difficult the problems become. As an example, you’ll eventually want to be able 
to mirror the interface state to bird or frr, as they see the tap interfaces. 
This rabbit hole of this type of issue goes very deep. 

For protocols that run over UDP, (and OSPF), VPP’s punt interface is one path 
forward.

You can’t punt TCP, so BGP would need to be retrofit on top of VPP’s host 
stack.  TCP-MD5 needs to be implemented in the host stack before a 
standards-compliant BGP could be accomplished.

Another path is to implement a protocol as a plugin. This is how we’ve 
implemented VRRP (protocol 112).

VPP is an open source project, so you’re free to implement via one of these or 
another method, as you choose. 

Jim

p.s. perhaps you only meant to engage in hyperbole, but I’ve found VPP quite 
useful without FRR or bird or any other dynamic routing protocol. They’re nice 
to have, but not required for many use cases. 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13449): https://lists.fd.io/g/vpp-dev/message/13449
Mute This Topic: https://lists.fd.io/mt/32309215/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to