Re: [vpp-dev] View IPv6 default route

DBGvpp# sh ip6 fib ::/0 ipv6-VRF:0, fib_index:0, flow hash:[src dst sport dport proto flowlabel ] epoch:0 flags:none locks:[default-route:1, ] ::/0 fib:0 index:5 locks:2 default-route refs:1 entry-flags:drop, src-flags:added,contributing,active, path-list:[7] locks:2 flags:drop,

Re: [vpp-dev] having problem pinging gtpu_tunnel0 interface, says Failed: no source address for egress interface

Hi Venu, vagrant@ ~/vpp (master) $ grep -A1 -B1 gtpu MAINTAINERS Plugin - GTPU I:gtpu M:Hongjun Ni <> F:src/plugins/gtpu/ But the problem of ping on GTPU interfaces is not specific to GTPU, it’s a problem on all P2P interfaces. It’s something I need to fix. /neale

[vpp-dev] View IPv6 default route

Hi, How can we get IPv6 default routes using vpp cli? Thanks and Regards, Chinmaya Agarwal. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19753): https://lists.fd.io/g/vpp-dev/message/19753 Mute This Topic: https://lists.fd.io/mt/84176732/21656

Re: [EXTERNAL] Re: [vpp-dev] Multi-threading locks and synchronization

Really depends on what you need it to do, which I may have missed. Why do you need any synchronization at all? Chris From: vpp-dev@lists.fd.io on behalf of satish amara Date: Monday, July 12, 2021 at 23:59 To: vpp-dev@lists.fd.io Subject: Re: [EXTERNAL] Re: [vpp-dev] Multi-threading locks

Re: [vpp-dev] having problem pinging gtpu_tunnel0 interface, says Failed: no source address for egress interface

Hi Neale, Sorry for the late reply, the below patch worked for me. Can you let me know who is the gtpu mainrainer ? Thanks, Regards, Venu On Thu, 8 Jul 2021 at 19:15, Neale Ranns wrote: > > > Try this one: > > https://gerrit.fd.io/r/c/vpp/+/32801 > > > > /neale > > > > *From:

Re: [vpp-dev] VPP on different Linux Platforms

> On 13.07.2021., at 19:40, satish amara wrote: > > Hi, > Currently, the VPP code can be compiled only on RedHat, CentOS, and Ubuntu. > Can I compile the VPP code on other OS Linux flavors, I see it's hardcoded in > the makefile. I am trying to understand by changing the Makefile VPP code

[vpp-dev] Need help on IPSEC tunnel

Greetings of the day... I am facing a problem in ip-node lookup. Here is the sequence. 1) decrypting the esp packet at *esp4-decrypt-tun.* 2) packet is reaching to* ip4-input-no-checksum *which is nothing but the *ip4-lookup .* 3)From *ip4-input-no-checksum *ideally it should reach to *

[vpp-dev] VPP on different Linux Platforms

Hi, Currently, the VPP code can be compiled only on RedHat, CentOS, and Ubuntu. Can I compile the VPP code on other OS Linux flavors, I see it's hardcoded in the makefile. I am trying to understand by changing the Makefile VPP code can be compiled on other Linux platforms or is there any

Re: [EXTERNAL] Re: [vpp-dev] Multi-threading locks and synchronization

Sync is needed. It's a question about the design of packet flow in  VPP. Locks can be avoided if the packets in a flow are processed by the same thread. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19757):

Re: [EXTERNAL] [vpp-dev] Multi-threading locks and synchronization

> On 13.07.2021., at 18:41, satish amara wrote: > > Sync is needed. It's a question about the design of packet flow in VPP. > Locks can be avoided if the packets in a flow are processed by the same > thread. You can use the handoff to make sure all packets belonging to specific flow or

[vpp-dev] vapi message length error with variable length string type

Hi guys, Currently vapi message length is determined by sizeof(vapi_msg_) when alloced by vapi_msg_alloc. But if the vapi message has a variable length string type *string xxx[]* , the message real length can be changed, this will make vapi message length check error. For example,