Neale, We have a use case where we would like to be able to determine a more-fine-grained reason for introducing routes into the FIBs. All the routes we introduce will come via some API call, but on behalf of different sources. Specifically, they will come from a user-supplied static route, different routing protocols (BGP, OSPF, etc).
What would you say to adding a few more enum entries into the fib_source_t type? We could then modify the fib_api_route_add_del() to allow the API to state which source should be used rather than just "API". Thoughts? jdl
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14534): https://lists.fd.io/g/vpp-dev/message/14534 Mute This Topic: https://lists.fd.io/mt/44489479/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
