[vpp-dev] Facing issue Ipv6 routing (Vpp 1908)

Hello Everyone, We are facing an issue with respect to ipv6 fib lookup (Vpp-1908). Sometimes a packet comes out of the wrong interface , looks like due to wrong fib lookup. I have found one change which is not part of our code https://gerrit.fd.io/r/c/vpp/+/27255 Can anybody please suggest , is

Re: [vpp-dev] svm ASAN check error

Do you need https://gerrit.fd.io/r/c/vpp/+/29937 ? try 'DPDK_CONFIG="" make run' for #2 above. This output is not right: sudo -E /home/dev/code/vpp/build-root/install-vpp_debug-native/vpp/bin/vpp " unix { interactive cli-listen /run/vpp/cli.sock gid 0 } *"dpdk { no-pci }"* " On Mon, Nov 16, 2

Re: [vpp-dev] svm ASAN check error

Hi ben: You can try the following steps: * make VPP_EXTRA_CMAKE_ARGS=-DVPP_ENABLE_SANITIZE_ADDR=ON build * make run * session enable > > DBGvpp# session enable > ==91579==AddressSanitizer CHECK failed: > ../../../../libsanitizer/asan/asan_mapping.h:377 "((AddrIsInMem(p))) != > (0)" (0x0, 0x0) >

[vpp-dev] why tunnel interfaces do not support device-input feature?

Hi all: why tunnel interfaces do not support device-input feature? why  esp packets  do not go through ipsec interface's "interface-output" node? I think it's no bad idea to keep some features consistency of all interface in spite of an little performance degradation? Best regards, Ye Don

[vpp-dev] vppctl fails from within the application (system cmd returns 256)

Hi, i am having a issue with VPP running on RH8.2 with version 20.05.1. There are 4 commands that I am trying to run from my application (using vppcli), fairly straight forward. the Trace.Writeline function is just a utility to print out the trace. what I see is the ret val is 256 indicating sy

[vpp-dev] #vpp #vppcom #vpp-dev #vnet

Hi All, I have a use case in which  a TCP connection will get terminate on VPP. So for that purpose i wanted to configure a TCP port which will bind to a interface. I wanted to verify the session manager vnet node as well as vpp graph nodes. For this exercise i am using hping3. Can anyone shed s

Re: [vpp-dev] Python API modules

> something has gone wrong here. Yeah, sorry for the confusion. I consult the maintainers file when double-checking who to add as reviewers. But when I think the maintainers file is outdated, I do not hesitate to add [0] or remove [1] anybody based on my (limited) perception. Usually I am too fo

Re: [vpp-dev] Python API modules

Hi Paul, > He/Vratko removed me as one of the maintainers of papi. > https://gerrit.fd.io/r/c/vpp/+/22672. I'm cool with not being a maintainer, > kinda funny that it was stuffed into another changeset. I have been called > out repeatedly for submitting unrelated changes ;) My apologies, so

Re: Handoff design issues [Re: RES: RES: [vpp-dev] Increasing NAT worker handoff frame queue size NAT_FQ_NELTS to avoid congestion drops?]

Just checked out the patch; you are compressing the frames on the receiving thread side. I didn't realize (i.e., look) that the code was copying the buffer indexes into a new frame anyway, as it is, I think this is a good fix! Thanks, Chris. > On Nov 16, 2020, at 4:20 AM, Klement Sekera -X (kse

Re: [vpp-dev] Increasing NAT worker handoff frame queue size NAT_FQ_NELTS to avoid congestion drops?

Hi Elias, thanks for getting back with some real numbers. I only tested with two workers and a very simple case and in my case, increasing queue size didn’t help one bit. But again, in my case there was 100% handoff rate (every single packet was going through handoff), which is most probably th

Re: [vpp-dev] Increasing NAT worker handoff frame queue size NAT_FQ_NELTS to avoid congestion drops?

Hi Klement, Thanks! I have now tested your patch (28980), it seems to work and it does give some improvement. However, according to my tests, increasing NAT_FQ_NELTS seems to have a bigger effect, it improves performance a lot. When using the original NAT_FQ_NELTS value of 64, your patch gives som

Re: [vpp-dev] IPSEC traffic fails when ESN is enabled

Hi Vijay, It is not a known issue AFAIK. Can you share more details? vpp# show ikev2 sa details vpp# show ipsec all Also, could you share a packet trace? vpp# clear trace vpp# trace add dpdk-input 10 [send traffic and see it being dropped] vpp# show trace Thanks ben > -Original Message

Re: Handoff design issues [Re: RES: RES: [vpp-dev] Increasing NAT worker handoff frame queue size NAT_FQ_NELTS to avoid congestion drops?]

That’s exactly what my patch improves. Coalescing small groups of packets waiting in the handoff queue into a full(er) frame allows the downstream node to do more “V” and achieve better performance. And that’s also what I’ve seen when testing the patch. Thanks, Klement ps. in case you missed t

Re: RES: RES: RES: [vpp-dev] Increasing NAT worker handoff frame queue size NAT_FQ_NELTS to avoid congestion drops?

If you can handle the traffic with a single thread then all multi-worker issues would go away. But the congestion drops are seen easily with as little as two workers due to infra limitations. Regards, Klement > On 13 Nov 2020, at 18:41, Marcos - Mgiga wrote: > > Thanks, you see reducing the n

Re: [vpp-dev] svm ASAN check error

Hi, > There is a svm ASAN check error. My vpp version is 21.01-rc0~394- > g798267aaa Can you try running with the following environment variable set: ASAN_OPTIONS=unmap_shadow_on_exit=1:disable_coredump=0:abort_on_error=1:detect_leaks=0:protect_shadow_gap=0 Also, we'd need you startup.conf. Be