[vpp-dev] Memif "no free tx slots" in 18.10

Retrying this.   Hi Vpp-Dev,   Need your help in understanding one the Memif related issue that we are facing in 18.10. This code has been working in 18.01. As soon as we moved to 18.10, we are started seeing this issue.   When our graph node tries to send a message over Memif interface, the sen

Re: [vpp-dev] vlib_register_all_static_nodes not picking up the graph node ( in 18.10 )

Hi Dave, The file with register_node for this graph node was not getting picked up as it was present in the "MULTIARCH_SOURCES" section in the CMakeLists.txt. This was working with 1801, but not in 18.10. After removing the section MULTIARCH_SOURCES, this got solved. Thanks & Regards, Satish -

Re: [vpp-dev] vpp-selinux-policy package

I'll take a look. Assigned the Jira to myself. Billy McFall On Mon, Apr 15, 2019 at 5:22 PM via Lists.Fd.Io wrote: > Hi, > > > > I recently installed VPP on a centos7 host and I had to set SELinux in > permissive mode to assign a vmxnet3 NIC to VPP or create veth interface. > > > > I opened bug

[vpp-dev] vpp-selinux-policy package

Hi, I recently installed VPP on a centos7 host and I had to set SELinux in permissive mode to assign a vmxnet3 NIC to VPP or create veth interface. I opened bug VPP-1640 to track this issue. Thanks for your support Laurent. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this gr

Re: [vpp-dev] A few MAP-T Clarifications

Hey, sorry to pester folks... Anyone have any insight here for us? Thanks, jdl On Wed, Apr 10, 2019 at 8:12 AM Jon Loeliger wrote: > Good Morning, > > We are working on some MAP-E and MAP-T testing, and we have > a few questions. Some of the existing VPP documentation about > MAP-E and MAP-T

[vpp-dev] pcap trace status in 19.04 reports local0 instead of specified interface

Hello all. I am using VPP 19.04 with DPDK 19.02. When I start a pcap trace on physical or tap interfaces, pcap trace status reports it as 'local0'. vpp# pcap rx trace on max 500 intfc tap0 file subif-rx.pcap pcap rx capture on... vpp# pcap rx trace status max is 500 for interface local0 to file

[vpp-dev] release commit rule

One sentence from miletone e-mails caught my attention: > Commit first to the release throttle, > then "git cherry-pick" into master I have tried searching for context. I have found this [0] wiki edit, with just > Here are a few common-sense suggestions: as an explanation. When I was working on O

Re: [vpp-dev] do not SNAT if forwarding enabled

Hi Ole, any finding on it ? are u able to reproduce it ? -Shahid. On Thu, Apr 11, 2019 at 1:32 PM Shahid Khan via Lists.Fd.Io wrote: > There is another physical port bridged to loop1 which is on > 192.168.15.0/24 network. > .the packets coming inside GRE tunnel are for 192.168.15.0/24 >