Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure

2020-01-31 Thread Benoit Ganne (bganne) via Lists.Fd.Io
Hi Chris, Here are some updates: we were able to make VPP get packets in Azure with the DPDK driver. Note that the native rdma driver does not support Azure yet (it supports only mlx5 for now and does not support vmbus pairing). You need to recompile the DPDK embedded in VPP DPDK plugin with the

[vpp-dev] Issue coming while fib lookup in vpp 18.01 between /8 and default route

2020-01-31 Thread chetan bhasin
Hello Everyone, I know that vpp 18.01 is not supported further, but can anybody please provide a direction towards the below issue: We have two routes - 1) defaut gateway via 2.2.2.2 2) 10.0.0.0/8 via 3.3.3.3 Trying to ping 10.20.x.x via VPP but it is going via 1) default gateway but it should g

[vpp-dev] SRv6 header processing

2020-01-31 Thread Mohamed feroz Abdul majeeth
Hello folks, As per the draft (https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-06 ) LE value should be greater than or equal to SL. what will happen if LE is less than SL? I tested below combination in fd.io VPP version stable/1908 ( commit id :a6a98b5) LE =0 & SL = 2 - SRv6 hea

Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure

2020-01-31 Thread Chris King
Ben, I'm glad you got it to work - thanks for the info! Interestingly, I had already modified those 4 lines in dpdk.mk from 'n' to 'y' and I still get the "EAL: Driver cannot attach the device" errors when starting VPP. I noticed in your config file above that it says DPDK_VERSION ?= 19.08. My

Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure

2020-01-31 Thread Chris King
[Edited Message Follows] [Reason: Renaming 10dtap.link to 10-dtap.link] Ben, I'm glad you got it to work - thanks for the info! Interestingly, I had already modified those 4 lines in dpdk.mk from 'n' to 'y' and I still get the "EAL: Driver cannot attach the device" errors when starting VPP. I

Re: [vpp-dev] Wanted to use socket transport as VAT API ( not svm i.e shared memory default)

2020-01-31 Thread sastry . sista
Hi Ole, So VAT APIs has only shared memory has transport? Socket fd APIs like producer_event_fd etc are there but, I am not sure if they are any use. Please confirm if there is any other way to use VAT API? ALso vppctl commands between vpp_main and vppctl is using Unix socket? With Regards Sas

Re: [EXTERNAL] Re: [vpp-dev] Wanted to use socket transport as VAT API ( not svm i.e shared memory default)

2020-01-31 Thread Chris Luke
Vppctl uses a unix socket, yes, but it’s exactly the same as the TCP socket version of the CLI – it runs the TELNET protocol and does terminal-like IO with unstructured intended-for-humans content. There’s nothing special about it. Chris. From: vpp-dev@lists.fd.io On Behalf Of sastry.si...@gm

[vpp-dev] Coverity run FAILED as of 2020-01-31 14:00:15 UTC

2020-01-31 Thread Noreply Jenkins
Coverity run failed today. Current number of outstanding issues are 1 Newly detected: 0 Eliminated: 4 More details can be found at https://scan.coverity.com/projects/fd-io-vpp/view_defects -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15301): ht

Re: [EXTERNAL] Re: [vpp-dev] Wanted to use socket transport as VAT API ( not svm i.e shared memory default)

2020-01-31 Thread sastry . sista
Hi Chris, Thank you for the reply. When vppctl has all the logic to take VAT kind of commands and get output back except some dynamic events etc. We wanted to develop VAT kind of application but would like to use socket lib as transport. VAT is primarily is using shared memeory and VAPI lib also

Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure

2020-01-31 Thread Benoit Ganne (bganne) via Lists.Fd.Io
> Interestingly, I had already modified those 4 lines in dpdk.mk from 'n' to > 'y' and I still get the "EAL: Driver cannot attach the device" errors when > starting VPP. Do you have LD_LIBRARY_PATH exported so that the DPDK can find the librte_pmd_mlx[45]_glue.so.* library? Eg. from the the vpp b

Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure

2020-01-31 Thread Chris King
Ben, I tried what you suggested but it didn't work for me (yet) :-(.  In order to get the *glue* libraries to build I had to go into vpp/build/external/packages and run 'make dpdk-install'. Then I set LD_LIBRARY_PATH (was previously unset) and I issued the following commands: echo $LD_LIBRARY_

Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure

2020-01-31 Thread Chris King
[Edited Message Follows] [Reason: Fix minor typo] Ben, I tried what you suggested but it didn't work for me (yet) :-(.  In order to get the *glue* libraries to build I had to go into vpp/build/external/packages and run 'make dpdk-install'. Then I set LD_LIBRARY_PATH (was previously unset) and

Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure

2020-01-31 Thread Benoit Ganne (bganne) via Lists.Fd.Io
But you run VPP from systemd unit files, are you sure LD_LIBRARY_PATH is still set? Can you try: ~# sudo LD_LIBRARY_PATH=/home/chris/workspace/vpp/build/external/_build/dpdk-19.05/x86_64-native-linuxapp-gcc/lib /home/chris/workspace/vpp/build-root/install-vpp-native/vpp/bin/vpp "unix { interact