Hoi,
On 29.01.2026 14:17, Moritz Beck via lists.fd.io wrote:
Hi Pim,
thanks for the explanation! So the optional netns parameter is just
for tap creation and not netlink handling, correct?
In this CLI call:
lcp create lcp create
<sw_if_index>|<if-name> host-if <host-if-name> netns <namespace> [tun]
and its associated API call lcp_itf_pair_add_del(), the netns there
applies to where the TAP device gets created.
Theoretically, is it possible to dynamically register multiple new
netlink handlers in different namespaces? For my use case Linux VRFs
are not sufficient, unfortunately.
Linux CP only has one listener, as discussed. It is of course possible
to add multiple listeners, bind each to a VPP dataplane table for
ip4/ip6/mpls, and poll and govern the namespaces separately.
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.
Good luck!
groet,
Pim
--
Pim van Pelt<[email protected]>
PBVP1-RIPEhttps://ipng.ch/
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#26753): https://lists.fd.io/g/vpp-dev/message/26753
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]]
-=-=-=-=-=-=-=-=-=-=-=-
