Oh, I didn't notice that line. Yeah, that would absolutely not work. Btw, the cleanup for this case should work in master [0].
In any case, you can use the af_xdp plugin to enable a non-dpdk interface in vpp. [0] - https://gerrit.fd.io/r/c/vpp/+/43036 On Mon, 25 Aug 2025 at 04:52, Andre Nathan via lists.fd.io <andre= digirati.com...@lists.fd.io> wrote: > Hello > > On 8/5/25 9:41 AM, Andre Nathan via lists.fd.io wrote: > > The uplink2 interface is not compatible with DPDK so > > it's managed by Linux, but it's moved to the VPP namespace so that > > forwarding works > > After some more experimenting, I think this was the root cause of the > problem. When I setup this router, I thought I could make a non-DPDK > interface work together with VPP just by moving it to the same namespace > used by LCP. Now thinking about it, it doesn't really make much sense, > because what would VPP do with the netlink messages related to an > interface it doesn't know about? > > Anyway, I've disabled the BGP session with uplink2 and restarted VPP, > and after that I can't reproduce the synchronization issues I had with > kernel routes vs VPP/LCP ones. > > Cheers, > Andre > > > > > -- Best regards Stanislav Zaikin
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#26290): https://lists.fd.io/g/vpp-dev/message/26290 Mute This Topic: https://lists.fd.io/mt/114547460/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
