Hi Pim,
thanks for the explanation! So the optional netns parameter is just for tap creation and not netlink handling, correct? Theoretically, is it possible to dynamically register multiple new netlink handlers in different namespaces? For my use case Linux VRFs are not sufficient, unfortunately. As a workaround, I am thinking about just running multiple VPP instances, either each in their own namespace or all in one namespace with the netlink handler in a different namespace for each. Best regards Moritz
smime.p7s
Description: S/MIME cryptographic signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#26749): https://lists.fd.io/g/vpp-dev/message/26749 Mute This Topic: https://lists.fd.io/mt/117519114/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
