On Fri, May 28, 2021 at 1:59 AM Mike Beattie <m...@ethernal.org> wrote:
> > # vppctl lcp default netns dataplane > > As the netlink listener doesn't appear to be re-created in that netns > dynamically. > I can confirm that changing the default netns after startup of VPP does not work, and your diagnosis is correct; the listener is created at start time, and is not reconfigured after changing the default. For me, adding the default netns in the startup.conf is sufficient, and perhaps we ought to simply remove the API call, because changing it several times will mean there needs to be a pool of listeners, one per netns used, and routing will become difficult unless VRFs are used per namespace -- sounds, to me at least, more problematic to keep the API call and ability to switch/plumb into differing namespaces, than simply to remove the feature :) But then, maybe there was a design consideration/reason to add TAPs into multiple namespaces, Neale or Matt may know more. groet, Pim -- Pim van Pelt <p...@ipng.nl> PBVP1-RIPE - http://www.ipng.nl/
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19501): https://lists.fd.io/g/vpp-dev/message/19501 Mute This Topic: https://lists.fd.io/mt/83138237/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
