Re: [vpp-dev] Unable to configure mixed NAT and non-NAT traffic

Hi all, Just to add to the query, I have observed that in interface configuration is optional for NAT to work. All traffic get NATed if out interface is set with output-feature. Thanks, Rajith On Thu, 13 Jan 2022 at 7:06 AM, alekcejk via lists.fd.io wrote: > Hi all, > > I am trying to get setu

Re: [vpp-dev] linux-cp TAP MTU show issue

Hi, Yes, I have tested the latest code that includes https://gerrit.fd.io/r/c/vpp/+/33709. Test: "lcp lcp-sync on" => everything work fine "lcp lcp-sync off" => issue appears Here is a video with an example https://youtu.be/wwyXyVilvOk Regards Petr pá 14. 1. 2022 v 16:59 odesílatel Pim van Pelt

Re: [vpp-dev] linux-cp TAP MTU show issue

Hoi Petr, We merged a relevant VPP -> Linux interface sync change in https://gerrit.fd.io/r/c/vpp/+/33709 just this week. The code that does this sync is in lcp_interface_sync.c:100 and lcp_interface.c:1004. Does your build include that code, and did you issue "lcp lcp-sync on" ? On Fri, Jan 14,

[vpp-dev] linux-cp TAP MTU show issue

Hello, I have found a cosmetic issue with a linux-cp TAP device (tested both plugins - original and patched linux-cp 31122 ). If you try to add multiple LCP TAP interfaces, sometimes there is bug in "vppctl show interface" output. MTU at the TAP is randomly shown incorrectly like: tap10

Re: [vpp-dev] VXLAN and RSS

> Him Pim, This was supposed to read "Hi Pim". Although I did to find a nice play on "Hoi". ;-) Ole > > I'm also doing a round now updating the Geneve implementation: > - add direct {IPv4, IPv6} encapsulation support > - validate protocol type (now all payload is blindly treated as Ethernet) >

Re: [vpp-dev] VXLAN and RSS

Him Pim, I'm also doing a round now updating the Geneve implementation: - add direct {IPv4, IPv6} encapsulation support - validate protocol type (now all payload is blindly treated as Ethernet) - drop packets with C bit set - make well known port configurable cheers, Ole > On 14 Jan 2022, at

Re: [vpp-dev] VXLAN and RSS

Hi Pim, The logic there (I think) is that the since the source port is the one you send with, it is also the one you receive on, so the source-port setting determines the key to match incoming traffic, i.e. it’s the peer’s dst-port. /neale From: Pim van Pelt Date: Friday, 14 January 2022 at 1

[vpp-dev] MPLS Tunnel Interface on Provider Router

Hi, I was doing a PoC to simulate label swap operation on Service Provider Router(non PE Routers) by creating a mpls tunnel interface and using that tunnel interface as a target in mpls route entry. Reference:https://wiki.fd.io/view/VPP/MPLS_FIB Please find below the set of configs that I trie

Re: [vpp-dev] VXLAN and RSS

Hoi, Neale, thank you for pointing that out! I verified the intent, and I can confirm that VXLAN uses random source ports [1], and so does GENEVE [2], so this is WAI. I mirrored traffic between the two VPP hosts, while running a T-Rex bench.py with vm=var2 to scramble the src/dst IP addresses of t

Re: [vpp-dev] VXLAN and RSS

Hi Pim, For VXLAN the intention is to use random source ports. The code you sight builds the ‘static’ portion of the imposed header. The source ports are overwritten with the hash of the encapped packet in encap.c:246 /neale From: vpp-dev@lists.fd.io on behalf of Pim van Pelt via lists.fd.i