Re: [vpp-dev] VPP v22.02 not coming up

Hi, I have compiled VPP v22.02 on Centos 8.4. I was able to compile it. But when I installed it and modified /etc/vpp/startup.conf, vpp service is not able to come up. I added below sections in /etc/vpp/startup.conf:- dpdk { socket-mem 1024 dev :00:08.0 dev :00:09.0 dev :00:0a.0 dev

Re: [vpp-dev] Query on VPP in Aure

Hi John, I have had some problems on Azure with my build lately similar to the MTU errors you mentioned. The build that has problems is based on the commit b0f0f8c8d ("memif: fix memif_process_desc indexing") from the upstream master branch (so..master branch from 1 or 2 months ago using DPDK 21.1

[vpp-dev] What's New in Calico v3.23

People is this list will certainly be interested in this announcement https://www.tigera.io/blog/whats-new-in-calico-v3-23/ Regards, Jerome -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21446): https://lists.fd.io/g/vpp-dev/message/21446 Mute This

Re: [vpp-dev] VPP v22.02 not coming up

Hoi, Linux CP's "interface-auto-create" flag is no longer valid. Currently you can use the following CLI options (see src/plugins/linux-cp/lcp_cli.c): .short_help = "lcp create | host-if " .short_help = "lcp lcp-sync [on|enable|off|disable]", .short_help = "lcp lcp-auto-subint [on|enable|of

[vpp-dev] VPP v22.02 not coming up

Hi, I have compiled VPP v22.02 on Centos 8.4. I was able to compile it. But when I installed it and modified /etc/vpp/startup.conf, vpp service is not able to come up. I added below sections in /etc/vpp/startup.conf:- dpdk { socket-mem 1024 dev :00:08.0 dev :00:09.0 dev :00:0a.0 dev

Re: [vpp-dev] zero memcpy interface (alternative to memif) to pass packets from VPP to another trusted DPDK application

Thank you Damjan. Really appreciate it. I got the idea. Let me look into the snort plugin code and experiment and get back to you should I have any questions. - PK Das On Tue, May 24, 2022 at 8:51 AM Damjan Marion wrote: > > On 24.05.2022., at 14:28, PRANAB DAS wrote: > > Hi Damjan, > > The s

Re: [vpp-dev] zero memcpy interface (alternative to memif) to pass packets from VPP to another trusted DPDK application

> On 24.05.2022., at 14:28, PRANAB DAS wrote: > > Hi Damjan, > > The snort plugin could be simple. But I am not familiar with VPP > memory/buffer management as such and I am finding it not so easy to navigate. > And looking at the physmem.c/h code, it appears the VPP uses heap memory > (mmap

Re: [vpp-dev] zero memcpy interface (alternative to memif) to pass packets from VPP to another trusted DPDK application

Hi Damjan, The snort plugin could be simple. But I am not familiar with VPP memory/buffer management as such and I am finding it not so easy to navigate. And looking at the physmem.c/h code, it appears the VPP uses heap memory (mmap) and has its own heap/buffer management system. Could you clarify

Re: [vpp-dev] zero memcpy interface (alternative to memif) to pass packets from VPP to another trusted DPDK application

VPP is not DPDK application, VPP features doesnt maintain DPDK metadata, in many cases we use native drivers so DPDK is not even loaded so you cannot use rte_ring unless you want to write complete translation layer which will likely be significantly slower that using native way which snort plug

[vpp-dev] VPP call topic - csit.fd.io perf dashboard preview

Hi Damjan, For the VPP call today, if possible, could we get 10-15min for CSIT team to do a demo of the new csit.fd.io perf dashboard? Cheers, Maciek -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21439): https://lists.fd.io/g/vpp-dev/message/2143

Re: [vpp-dev] zero memcpy interface (alternative to memif) to pass packets from VPP to another trusted DPDK application

Thank you very much for your response Benoit! I am wondering if there is another option e.g. rte-ring of DPDK or if that option is not feasible in VPP? Could you comment? We are looking for a service-chaining application similar to snort but would like to have a much simpler zero-copy interface. T

Re: [vpp-dev] Question about vpp neighbour Mac entry

That's not how a layer 3 network works: the dest mac is the mac address of the L3 nexthop. If you want to use the dest mac of the switch as nexthop, it should act as a router (with an IP address you can use as nexthop). Best Ben > -Original Message- > From: vpp-dev@lists.fd.io On Behal

Re: [vpp-dev] zero memcpy interface (alternative to memif) to pass packets from VPP to another trusted DPDK application

It all depends on what you want to do. Usually, we try to avoid sharing buffers read/write between multiple process, it makes debugging much harder - especially buffer leaks or use-after-free... Here is an example to share VPP buffers read-only with snort so that snort can inspect traffic and gi

Re: [vpp-dev] Help needed in bringing up memif with shm_open.

I think you should run step-by-step with gdb to see exactly what is failing. As it works on a recent system but not on an old one, I suspect an issue with an unsupported feature (eg. special flag in syscall or similar)... Best ben > -Original Message- > From: vpp-dev@lists.fd.io On Beh

Re: [vpp-dev] handling L2 and L3 traffic in gtpu plugin

Hi Vijay, You can adopt something similar to what was implemented for vxlan. Like specifying the next-node for the tunnel when creating. On Tue, 24 May 2022 at 07:52, wrote: > Hi, > > I wants to understand, how can i handle L2 and L3 traffic in gtpu plugin > during encap and decap. > Do anyone