Re: [vpp-dev] [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Kawshik, Hc2vpp release is planned tomorrow so stay tuned ☺ You might also want to try artifacts from: https://nexus.fd.io/content/repositories/fd.io.stable.1801.ubuntu.xenial.main/io/fd/hc2vpp/honeycomb/ In case of issues, please contact hc2...@lists.fd.io. Regards, Marek From:

[vpp-dev] ping/interface bring up question

Hello, I have two vpp interfaces up on my VM, but cannot ping one vpp interface from the other. (I followed instructions in this doc https://wiki.fd.io/view/VPP/How_To_Connect_A_PCI_Interface_To_VPP) Do I need any additional

Re: [vpp-dev] recovering from a crash with the C shared memory API

Hi Florin, I rebuilt VPP with your patch applied. It looks like it works. I restarted VPP while one of my applications was connected to the API. Then I created some activity that would force the application to send a message the API. It logged a timeout on sending a message and then

Re: [vpp-dev] out of memory when adding > 64k routes

That worked!! Thanks Florin! -Matt > On Jan 29, 2018, at 3:34 PM, Florin Coras wrote: > > Hi Matt, > > I’ll let Neale provide more details but I think that what you’re looking for > is to start vpp with ip {heap-size } > > Cheers, > Florin > >> On Jan 29, 2018,

Re: [vpp-dev] out of memory when adding > 64k routes

Hi Matt, I’ll let Neale provide more details but I think that what you’re looking for is to start vpp with ip {heap-size } Cheers, Florin > On Jan 29, 2018, at 1:24 PM, Matthew Smith wrote: > > > Hi, > > I’ve been trying to insert a large set of routes into VPP’s FIB.

[vpp-dev] out of memory when adding > 64k routes

Hi, I’ve been trying to insert a large set of routes into VPP’s FIB. VPP keeps exiting after adding a very specific amount of them (64278). If I attach to the vpp process with gdb and start adding the routes, after a few seconds an ABRT is received. The backtrace (see below) shows that

Re: [vpp-dev] recovering from a crash with the C shared memory API

Ow, I’m guilty of having “manually restarted” vpp so I completely avoided the segment cleanup ... I can’t yet figure out why, but it seems that doing vl_client_api_unmap when vpp does not respond leads to breakage. Could you try the quick fix here [1] and see if it fixes your issue? Cheers,

Re: [vpp-dev] recovering from a crash with the C shared memory API

Hi Florin, If I repeat that test exactly as you ran it, I see the same results as you did. With a slight modification, the situation I described shows up: 1. systemctl start vpp 2. start vat, execute sw_interface_dump 3. leave vat running, in another terminal run systemctl restart vpp 4. in

Re: [vpp-dev] Routing in VPP - newbie

You need a route :) See: https://wiki.fd.io/view/VPP/Progressive_VPP_Tutorial#Exercise:_Routing (note: The Routing Exercise builds on previous exercises in the Tutorial... but seems to be pretty close to what you are trying to do :) ). Ed On Mon, Jan 29, 2018 at 12:19 PM Abdul Hadi

[vpp-dev] Routing in VPP - newbie

Hi, I have just started with VPP. Please ignore my ignorance. Will VPP route my traffic from one subnet to another by default? or do i have to create additional routes in order to reach a subnet. I have a simple topology of Three VMs. 10.0.1.21 -> 10.0.1.22 (VM running VPP) 10.0.3.22

Re: [vpp-dev] Supporting vpp releases besides N and N-1

On Fri, 2018-01-26 at 19:40 +, Ed Warnicke wrote: > I think you've hit on the right metric: retire those streams which are no > longer supported. +1 What do others think? Ed On Fri, Jan 26, 2018 at 3:53 PM Ed Kern (ejk) wrote: Id like to clean up jenkins ‘stream’ in the

Re: [vpp-dev] Arp doesn't work after classifier configuration

DBGvpp# sh ip fib 6.6.6.1/32 ipv4-VRF:0, fib_index:0, flow hash:[src dst sport dport proto ] locks:[src:(nil):2, src:default-route:1, ] 6.6.6.1/32 fib:0 index:10 locks:3 src:classify refs:1 src-flags:added,active, path-list:[14] locks:2 uPRF-list:8 len:0 itfs:[] path:[14] pl-index:14

Re: [vpp-dev] Arp doesn't work after classifier configuration

Hi Neale, Thanks. Below is the requested output. DBGvpp# show ip fib ipv4-VRF:0, fib_index:0, flow hash:[src dst sport dport proto ] locks:[src:(nil):2, src:default-route:1, ] 0.0.0.0/0 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:1 buckets:1 uRPF:0 to:[0:0]] [0] [@0]:

Re: [vpp-dev] Arp doesn't work after classifier configuration

Hi Brindiya, Could you please show me the output of: sh ip fib 6.6.6.1/32 Thanks, neale From: on behalf of bindiya Kurle Date: Monday, 29 January 2018 at 10:04 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev] Arp

Re: [vpp-dev] Howto implement L3 p2p tunnel interface without assigning IP to the interface?

Hi Andreas, There are binary API equivalent messages to the CLI commands I gave. For a non-interface based encap scheme you could reference as an example src/vnet/udp/udp_encap.[ch]. Not having an interface means there is no attachment point for features (like ACLs, NAT, etc) and you’ll need a

[vpp-dev] Arp doesn't work after classifier configuration

Hi, my vpp version : DBGvpp# show version vpp v18.04-rc0~81-g18e955e . I am observing whenever I do classifier configuration , arp resolution does not work my configuration: set interface state GigabitEthernet1/0/1 up set interface ip address GigabitEthernet1/0/1 6.6.6.1/24 classify table