Re: [EXTERNAL] Re: Re: [csit-dev] [vpp-dev] A 404 error occurred in the process of sudo apt-get update. How to solve it?

2018-05-02 Thread Chris Luke 
We’re not able to give detailed basic linux support here. Are you following a 
guide that had you execute a step to install the packages? That will tell you 
which files it modified to add the repository lines. Somewhere in 
/etc/apt/sources.list.d/

Chris.

From: 汤超 
Sent: Wednesday, May 2, 2018 20:34
To: Luke, Chris ; vpp-dev 
Cc: csit-dev 
Subject: [EXTERNAL] Re: Re: [csit-dev] [vpp-dev] A 404 error occurred in the 
process of sudo apt-get update. How to solve it?

Yes, I found this problem, but how should I modify it? Is the 
etc/apt/source.list file modified? How should I modify it?

My source file content：

#deb cdrom:[Ubuntu 16.04.4 LTS _Xenial Xerus_ - Release amd64 (20180228)]/ 
xenial main restricted

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial main restricted
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial universe
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial universe
deb http://cn.archive.ubuntu.com/ubuntu/ xenial-updates universe
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial multiverse
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial multiverse
deb http://cn.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial-backports main restricted 
universe multiverse
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial-backports main restricted 
universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu xenial partner
# deb-src http://archive.canonical.com/ubuntu xenial partner

deb http://security.ubuntu.com/ubuntu xenial-security main restricted
# deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted
deb http://security.ubuntu.com/ubuntu xenial-security universe
# deb-src http://security.ubuntu.com/ubuntu xenial-security universe
deb http://security.ubuntu.com/ubuntu xenial-security multiverse
# deb-src http://security.ubuntu.com/ubuntu xenial-security multiverse
deb http://download.virtualbox.org/virtualbox/debian xenial contrib
deb http://download.virtualbox.org/virtualbox/debian xenial contrib
deb http://download.virtualbox.org/virtualbox/debian xenial contrib
deb http://download.virtualbox.org/virtualbox/debian xenial contrib


nwnj...@fiberhome.com

From: Chris Luke
Date: 2018-05-02 19:06
To: 汤超; vpp-dev
CC: csit-dev
Subject: Re: [csit-dev] [vpp-dev] A 404 error occurred in the process of sudo 
apt-get update. How to solve it?
‘fd.io.ubuntu..main’ is not a valid URL – spot the double-dot. It’s missing the 
word ‘xenial’.

Chris.


From: vpp-dev@lists.fd.io 
> On Behalf Of ??
Sent: Tuesday, May 1, 2018 22:41
To: vpp-dev >
Cc: csit-dev >
Subject: [EXTERNAL] [vpp-dev] A 404 error occurred in the process of sudo 
apt-get update. How to solve it?

A 404 error occurred in the process of sudo apt-get update. How to solve it?
fiber@ubuntu:/etc/apt$ sudo apt-get update
Have you ever met？

Hit:1 http://archive.ubuntukylin.com:10006/ubuntukylin xenial InRelease
Hit:2

[vpp-dev] hardware-interfaces not seen inside VPP

2018-05-02 Thread Jit Mehta 
Hello,

I see that my physical nic highlighted below is seen by vpp but somehow I
do not see corresponding hardware interface TenGigabitEthernet9/0/0
in "show hardware-interfaces". How do I create this interface in VPP?

Thanks,
Jit



vpp# show pci

Address  Sock VID:PID Link Speed   Driver  Product Name
Vital Product Data

:01:00.0   0  8086:1521   5.0 GT/s x4  igb Cisco  I350-TX
1Gig LOM  PN: I350-TX


V0: 0x 31 2e 36 2e 33 2d 32 2e ...


MN: 1137


RV: 0x be

:01:00.1   0  8086:1521   5.0 GT/s x4  igb Cisco  I350-TX
1Gig LOM  PN: I350-TX


V0: 0x 31 2e 36 2e 33 2d 32 2e ...


MN: 1137


RV: 0x be

*:09:00.0   0  1137:0043   5.0 GT/s x16 uio_pci_generic*


:0a:00.0   0  1137:0043   5.0 GT/s x16 enic


:0e:00.0   0  8086:10fb   5.0 GT/s x8  ixgbe


:0e:00.1   0  8086:10fb   5.0 GT/s x8  ixgbe


:81:00.0   1  14e4:d802   8.0 GT/s x8


:81:00.1   1  14e4:d802   8.0 GT/s x8


:81:00.2   1  14e4:d802   8.0 GT/s x8


:81:00.3   1  14e4:d802   8.0 GT/s x8


vpp# show hardware-interfaces

  NameIdx   Link  Hardware

local0 0down  local0

  local

Re: [csit-dev] [vpp-dev] A 404 error occurred in the process of sudo apt-get update. How to solve it?

2018-05-02 Thread 汤超 
Yes, I found this problem, but how should I modify it? Is the 
etc/apt/source.list file modified? How should I modify it?

My source file content：

#deb cdrom:[Ubuntu 16.04.4 LTS _Xenial Xerus_ - Release amd64 (20180228)]/ 
xenial main restricted

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial main restricted
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial universe
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial universe
deb http://cn.archive.ubuntu.com/ubuntu/ xenial-updates universe
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial multiverse
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial multiverse
deb http://cn.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://cn.archive.ubuntu.com/ubuntu/ xenial-backports main restricted 
universe multiverse
# deb-src http://cn.archive.ubuntu.com/ubuntu/ xenial-backports main restricted 
universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu xenial partner
# deb-src http://archive.canonical.com/ubuntu xenial partner

deb http://security.ubuntu.com/ubuntu xenial-security main restricted
# deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted
deb http://security.ubuntu.com/ubuntu xenial-security universe
# deb-src http://security.ubuntu.com/ubuntu xenial-security universe
deb http://security.ubuntu.com/ubuntu xenial-security multiverse
# deb-src http://security.ubuntu.com/ubuntu xenial-security multiverse
deb http://download.virtualbox.org/virtualbox/debian xenial contrib
deb http://download.virtualbox.org/virtualbox/debian xenial contrib
deb http://download.virtualbox.org/virtualbox/debian xenial contrib
deb http://download.virtualbox.org/virtualbox/debian xenial contrib



nwnj...@fiberhome.com
 
From: Chris Luke
Date: 2018-05-02 19:06
To: 汤超; vpp-dev
CC: csit-dev
Subject: Re: [csit-dev] [vpp-dev] A 404 error occurred in the process of sudo 
apt-get update. How to solve it?
‘fd.io.ubuntu..main’ is not a valid URL – spot the double-dot. It’s missing the 
word ‘xenial’.
 
Chris.
 
 
From: vpp-dev@lists.fd.io  On Behalf Of ??
Sent: Tuesday, May 1, 2018 22:41
To: vpp-dev 
Cc: csit-dev 
Subject: [EXTERNAL] [vpp-dev] A 404 error occurred in the process of sudo 
apt-get update. How to solve it?
 
A 404 error occurred in the process of sudo apt-get update. How to solve it?
fiber@ubuntu:/etc/apt$ sudo apt-get update 
Have you ever met？
 
Hit:1 http://archive.ubuntukylin.com:10006/ubuntukylin xenial InRelease
Hit:2 http://download.virtualbox.org/virtualbox/debian xenial InRelease 


Hit:3 http://cn.archive.ubuntu.com/ubuntu xenial InRelease  


Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]  
   
Hit:5 http://cn.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:6 http://cn.archive.ubuntu.com/ubuntu xenial-backports InRelease
   
Ign:7 https://nexus.fd.io/content/repositories/fd.io.ubuntu.xenial.main ./ 
InRelease
Ign:8 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ InRelease
Ign:10 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ Release
Ign:11

Re: [vpp-dev] segfault due to movaps unaligned access

2018-05-02 Thread Dave Barach 
Quick update. I added the obvious ASSERT, and immediately found a couple of 
non-compliant data structures. With two (trivial) fixes, vpp makes it to the 
debug CLI prompt. I'm going to start looking at "make test-debug", to see how 
many additional issues we may encounter.

D. 

-Original Message-
From: Dave Barach (dbarach) 
Sent: Tuesday, May 1, 2018 3:29 PM
To: Ray Kinsella ; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] segfault due to movaps unaligned access

Hey Ray,

That's a good idea, and none too hard to implement. It's on my list.

I'm a bit afraid of what I may find when I turn it on, but anyhow...

Thanks... D.

-Original Message-
From: vpp-dev@lists.fd.io  On Behalf Of Ray Kinsella
Sent: Tuesday, May 1, 2018 10:58 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] segfault due to movaps unaligned access

Is it worth to use an assert (or similar) to validate the assumption in the 
debug build at least. Well at least until the compiler bugs get's sorted?

Ray K

On 26/04/2018 17:08, Dave Barach wrote:
> Yes, it’s arguably a compiler bug.
> 
> But, it makes no sense to vec_validate_aligned(…), pool_get_aligned(…) 
> etc. objects whose size is not a multiple of the alignment request.
> Only the first element will be aligned to the specified boundary.
> 
> __attribute__((aligned(xxx))) is not the same thing as ensuring that 
> objects are _sized_ correctly.
> 
> D.
> 
> *From:*vpp-dev@lists.fd.io  *On Behalf Of *Radu 
> Nicolau
> *Sent:* Thursday, April 26, 2018 4:54 AM
> *To:* Florin Coras 
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] segfault due to movaps unaligned access
> 
> Hi Florin,
> 
> Thanks! The patch fixes the issue.
> 
> Any idea why is it happening?
> 
> Regards,
> 
> Radu
> 
> *From:*vpp-dev@lists.fd.io  
> [mailto:vpp-dev@lists.fd.io] *On Behalf Of *Florin Coras
> *Sent:* Tuesday, April 24, 2018 11:25 PM
> *To:* Nicolau, Radu  >
> *Cc:* vpp-dev@lists.fd.io 
> *Subject:* Re: [vpp-dev] segfault due to movaps unaligned access
> 
> Hi Radu,
> 
> Making the crypto_worker_main_t a full cache line in size (see patch
> [1]) seems to solve the issue. Could you confirm?
> 
> Florin
> 
> [1] https://gerrit.fd.io/r/#/c/12086/
> 
> On Apr 24, 2018, at 9:23 AM, Radu Nicolau  > wrote:
> 
> Hello all,
> 
> We’re seeing a weird issue, that is a segfault that looks to be
> caused by a movaps instruction that is trying to access an address
> that is not 16 byte aligned.
> 
> The call originates from a vec_validate_init_empty_aligned that has
> the argument aligned to 16 bytes.
> 
> I have seen something like this in the past, we couldn’t find a root
> cause and considered it a GCC bug (version 5 then), but now it pops
> up again on version 7, so probably it isn’t.
> 
> Any idea? A snapshot of the gdb screen below.
> 
> gcc (Ubuntu 7.2.0-8ubuntu3.2) 7.2.0
> 
> https://postimg.cc/image/9jy4p38at/
> 
> thanks and I will appreciate any help,
> 
> Radu
> 
> 




-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9151): https://lists.fd.io/g/vpp-dev/message/9151
View All Messages In Topic (14): https://lists.fd.io/g/vpp-dev/topic/18058213
Mute This Topic: https://lists.fd.io/mt/18058213/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] CentOS 7 build broken

2018-05-02 Thread Ed Kern 
Damn,

Thought I had enough retries to get around these corner cases but here again

3 rounds of centos failures failed faster then virl failure then success so it 
ended up with a +1 that shouldn’t have been the case.

Would not have been the case if the failure was also seen on ubuntu but this is 
still possible when the failure is NOT seen on ubuntu.

But thanks for the new patch…either that or revert the original bad patch is 
certainly the thing to do..

thanks,

Ed



On May 2, 2018, at 9:12 AM, Matthew Smith 
> wrote:


I see errors when trying to build from master on CentOS 7:

/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c: In function 
vxlan_rewrite':
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c:224:3: 
error:missing braces around initializer [-Werror=missing-braces]
   } h = {0};
   ^
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c:224:3: 
error:(near initialization for 'h.h4') [-Werror=missing-braces]
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c: In function 
vnet_vxlan_add_del_tunnel':
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c:388:7: 
error:missing braces around initializer [-Werror=missing-braces]
   *t = (vxlan_tunnel_t){ 0 };
   ^
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c:388:7: 
error:(near initialization for '(anonymous).next_dpo') [-Werror=missing-braces]
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c: At top level:
cc1: error: unrecognized command line option "-Wno-address-of-packed-member" 
[-Werror]
cc1: all warnings being treated as errors
make[4]: *** [vnet/vxlan/vxlan.lo] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory 
`/root/src/tnsr-pkgs/work/vpp/build-root/build-vpp_debug-native/vpp'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory 
`/root/src/tnsr-pkgs/work/vpp/build-root/build-vpp_debug-native/vpp'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/root/src/tnsr-pkgs/work/vpp/build-root/build-vpp_debug-native/vpp'
make[1]: *** [vpp-build] Error 2
make[1]: Leaving directory `/root/src/tnsr-pkgs/work/vpp/build-root'
make: *** [build] Error 2


This appears to be broken by https://gerrit.fd.io/r/#/c/12288/. The history 
there shows that the centos7 verify jobs failed with the same errors, but 
somehow the change ended up as Verified+1.

I submitted a patch (https://gerrit.fd.io/r/#/c/12349/) that makes the build 
work again for me. I haven’t tested it extensively, just built with it on 
CentOS 7 and then made sure vpp would start up afterwards.

-Matt

[vpp-dev] CentOS 7 build broken

2018-05-02 Thread Matthew Smith 

I see errors when trying to build from master on CentOS 7:

/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c: In function 
vxlan_rewrite':
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c:224:3: 
error:missing braces around initializer [-Werror=missing-braces]
   } h = {0};
   ^
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c:224:3: 
error:(near initialization for 'h.h4') [-Werror=missing-braces]
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c: In function 
vnet_vxlan_add_del_tunnel':
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c:388:7: 
error:missing braces around initializer [-Werror=missing-braces]
   *t = (vxlan_tunnel_t){ 0 };
   ^
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c:388:7: 
error:(near initialization for '(anonymous).next_dpo') [-Werror=missing-braces]
/root/src/tnsr-pkgs/work/vpp/build-data/../src/vnet/vxlan/vxlan.c: At top level:
cc1: error: unrecognized command line option "-Wno-address-of-packed-member" 
[-Werror]
cc1: all warnings being treated as errors
make[4]: *** [vnet/vxlan/vxlan.lo] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory 
`/root/src/tnsr-pkgs/work/vpp/build-root/build-vpp_debug-native/vpp'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory 
`/root/src/tnsr-pkgs/work/vpp/build-root/build-vpp_debug-native/vpp'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/root/src/tnsr-pkgs/work/vpp/build-root/build-vpp_debug-native/vpp'
make[1]: *** [vpp-build] Error 2
make[1]: Leaving directory `/root/src/tnsr-pkgs/work/vpp/build-root'
make: *** [build] Error 2


This appears to be broken by https://gerrit.fd.io/r/#/c/12288/ 
. The history there shows that the centos7 
verify jobs failed with the same errors, but somehow the change ended up as 
Verified+1.

I submitted a patch (https://gerrit.fd.io/r/#/c/12349/ 
) that makes the build work again for me. I 
haven’t tested it extensively, just built with it on CentOS 7 and then made 
sure vpp would start up afterwards.

-Matt

Re: [vpp-dev] Figure out u16 mapping in NAT API output

2018-05-02 Thread Hamid Rasool 
Many thanks Matus for the patch.

I will add the changes and rebuild the code on my setup. Will let you know
the results.

Regards,
Hamid.

On Wed, May 2, 2018 at 1:02 PM, Matus Fabian -X (matfabia - PANTHEON
TECHNOLOGIES at Cisco)  wrote:

> https://gerrit.fd.io/r/#/c/12309/
>
>
>
> Matus
>
>
>
> *From:* Hamid Rasool <14mseesras...@seecs.edu.pk>
> *Sent:* Wednesday, May 2, 2018 7:24 AM
> *To:* Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) <
> matfa...@cisco.com>
>
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Figure out u16 mapping in NAT API output
>
>
>
> Dear Matus,
>
>
>
> Thanks for looking into it. So, is there any way I can apply any
> encoding/decoding formula on these values to obtain the correct mapping?
>
>
>
> Thanks,
>
> Hamid.
>
>
>
> On Wed, May 2, 2018 at 10:02 AM, Matus Fabian -X (matfabia - PANTHEON
> TECHNOLOGIES at Cisco)  wrote:
>
> There is bug, fields are decoded wrong way in 
> vl_api_nat44_user_session_details_t_handler
> (nat_test.c)
>
> Just note, nat44_user_session_dump works only with non-deterministic NAT.
>
>
>
> Matus
>
>
>
>
>
> *From:* vpp-dev@lists.fd.io  *On Behalf Of *Hamid
> via Lists.Fd.Io
> *Sent:* Wednesday, May 2, 2018 6:50 AM
> *To:* vpp-dev@lists.fd.io
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Figure out u16 mapping in NAT API output
>
>
>
> Cannot find a decoder for these fields so I think these incomprehensible
> value for port numbers and protocol number should be reported as a bug?
>
> 
>
>
>

[vpp-dev] Python API for specific VPP instance

2018-05-02 Thread Justin Iurman 
Hi guys,

How can I "connect" to a specific instance of VPP through the python API ?

Each instance (together, they form a topology) is run as follow:
  sudo vpp unix { log /tmp/vpp1.log cli-listen /run/vpp/cli-vpp1.sock } 
api-segment { prefix vpp1 } plugins { plugin dpdk_plugin.so { disable } }

In python, usually, we do:
  vpp = VPP(jsonfiles)
  r = vpp.connect("xxx")

Is it possible to connect to a "prefix" (eg "vpp1") to only interact with a 
specific instance ?
Let's say, for instance, something like this:
  r = vpp.connect("vpp1")

Thanks,

Justin

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9147): https://lists.fd.io/g/vpp-dev/message/9147
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/18138970
Mute This Topic: https://lists.fd.io/mt/18138970/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Dynamically attach to a PCI device

2018-05-02 Thread Ray Kinsella 

Sorry Avi,

Let me clarify what I meant.

To the best of my knowledge, it is not supported with FD.io VPP + DPDK 
Plugin at this time. You can achieve something similar with FD.io VPP 
and AF_PACKET but it won't be fast.


As you point out, DPDK does support hotput, so it is not a DPDK 
constraint but I am not yet sure on the difficulty of implementing it.


Ray K

On 02/05/2018 08:30, Avi Cohen (A) wrote:

Ray
I know that with ovs-dpdk you can add/remove  a dpdk interface (physical or 
vhost-user) on runtime
Best Regards
Avi


-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ray Kinsella
Sent: Tuesday, 01 May, 2018 5:41 PM
To: Avi Cohen (A); vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Dynamically attach to a PCI device

Hi Avi,

Good question - really depends on how you want to do it.

To my knowledge it is not supported with DPDK. You can achieve similar
functionality using af_packet - but clearly it won't be anything like as fast.

Ray K

On 01/05/2018 08:11, Avi Cohen (A) wrote:

With Ovs-Dpdk this is supported
If this is not supported in VPP I can implement it Avi

-Original Message-
From: Avi Cohen (A)
Sent: Monday, 23 April, 2018 9:44 AM
To: 'vpp-dev@lists.fd.io'
Subject: RE: Dynamically attach to a PCI device

I'll clarify my question
For a PCI device e.g. :04:00:0  - is it possible to add this
device  to VPP on runtime with a specific cli command ?
Currently I  only can add these kind of devices  by specifying it in
the  while-list in startup.conf Best Regards Avi


-Original Message-
From: Avi Cohen (A)
Sent: Monday, 16 April, 2018 10:48 AM
To: vpp-dev@lists.fd.io
Subject: Dynamically attach to a PCI device

Hello All

Currently I attach the physical NICs PCI devices by setting the
white list in the startup.conf How can I attach it dynamically in runtime ?

Best Regards
Avi
















-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9146): https://lists.fd.io/g/vpp-dev/message/9146
View All Messages In Topic (6): https://lists.fd.io/g/vpp-dev/topic/17425326
Mute This Topic: https://lists.fd.io/mt/17425326/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] A 404 error occurred in the process of sudo apt-get update. How to solve it?

2018-05-02 Thread Chris Luke 
‘fd.io.ubuntu..main’ is not a valid URL – spot the double-dot. It’s missing the 
word ‘xenial’.

Chris.


From: vpp-dev@lists.fd.io  On Behalf Of ??
Sent: Tuesday, May 1, 2018 22:41
To: vpp-dev 
Cc: csit-dev 
Subject: [EXTERNAL] [vpp-dev] A 404 error occurred in the process of sudo 
apt-get update. How to solve it?

A 404 error occurred in the process of sudo apt-get update. How to solve it?
fiber@ubuntu:/etc/apt$ sudo apt-get update
Have you ever met？

Hit:1 http://archive.ubuntukylin.com:10006/ubuntukylin xenial InRelease
Hit:2 http://download.virtualbox.org/virtualbox/debian xenial InRelease
Hit:3 http://cn.archive.ubuntu.com/ubuntu xenial InRelease
Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
Hit:5 http://cn.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:6 http://cn.archive.ubuntu.com/ubuntu xenial-backports InRelease
Ign:7 https://nexus.fd.io/content/repositories/fd.io.ubuntu.xenial.main ./ 
InRelease
Ign:8 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ InRelease
Ign:10 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ Release
Ign:11 https://nexus.fd.io/content/repositories/fd.io.ubuntu.xenial.main ./ 
Release.gpg
Ign:12 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ Packages
Ign:13 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en_US
Ign:14 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en
Ign:12 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ Packages
Ign:13 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en_US
Ign:14 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en
Ign:12 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ Packages
Ign:13 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en_US
Ign:14 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en
Ign:12 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ Packages
Ign:13 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en_US
Ign:14 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en
Ign:12 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ Packages
Ign:13 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en_US
Ign:14 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en
Err:12 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ Packages
  404  Not Found
Ign:13 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en_US
Ign:14 https://nexus.fd.io/content/repositories/fd.io.ubuntu..main ./ 
Translation-en
Fetched 107 kB in 10s (9,909 B/s)
Reading package lists... Done
W: Target Packages (contrib/binary-amd64/Packages) is configured multiple times 
in /etc/apt/sources.list:52 and /etc/apt/sources.list:53
W: Target Packages (contrib/binary-i386/Packages) is configured multiple times 
in /etc/apt/sources.list:52 and /etc/apt/sources.list:53
W: Target Packages (contrib/binary-all/Packages) is configured multiple times 
in /etc/apt/sources.list:52 and /etc/apt/sources.list:53
W: Target Translations (contrib/i18n/Translation-en_US) is configured multiple 
times in /etc/apt/sources.list:52 and /etc/apt/sources.list:53
W: Target Translations (contrib/i18n/Translation-en) is configured multiple 
times in /etc/apt/sources.list:52 and /etc/apt/sources.list:53
W: Target DEP-11 (contrib/dep11/Components-amd64.yml) is configured multiple 
times in /etc/apt/sources.list:52 and /etc/apt/sources.list:53
W: Target DEP-11-icons (contrib/dep11/icons-64x64.tar) is configured multiple 
times in /etc/apt/sources.list:52 and /etc/apt/sources.list:53
W: Target Packages (contrib/binary-amd64/Packages) is configured multiple times 
in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (contrib/binary-i386/Packages) is configured multiple times 
in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (contrib/binary-all/Packages) is configured multiple times 
in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Translations (contrib/i18n/Translation-en_US) is configured multiple 
times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Translations (contrib/i18n/Translation-en) is configured multiple 
times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target DEP-11 (contrib/dep11/Components-amd64.yml) is configured multiple 
times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target DEP-11-icons (contrib/dep11/icons-64x64.tar) is configured multiple 
times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (contrib/binary-amd64/Packages) is configured multiple times 
in /etc/apt/sources.list:52 and /etc/apt/sources.list:55
W: Target Packages

Re: [vpp-dev] problem in SRV6

2018-05-02 Thread Pablo 
Hi Jane,

Could you share more details on your config/topology?
All VPP releases after 17.07 are good to use SRv6.

Thanks,
Pablo.

SRv6 documentation:
https://docs.fd.io/vpp/18.07/srv6_doc.html
https://wiki.fd.io/view/VPP/Segment_Routing_for_IPv6

From:  on behalf of Jane Chang 
Date: Friday, 27 April 2018 at 21:22
To: "vpp-dev@lists.fd.io" 
Subject: Re: [vpp-dev] problem in SRV6

Hello,

I have similar SRv6 setup as Xyxue described in earlier email.
However I see ipv6 ping pkts got drop on ingress port of VPP1.
So I never get chance to see how SRv6 play out in VPP1.
Would you pls let know which version of VPP is good for using SRv6?
Thanks,
Jane chang

Re: [vpp-dev] Figure out u16 mapping in NAT API output

2018-05-02 Thread Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES@Cisco) 
https://gerrit.fd.io/r/#/c/12309/

Matus

From: Hamid Rasool <14mseesras...@seecs.edu.pk>
Sent: Wednesday, May 2, 2018 7:24 AM
To: Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) 

Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Figure out u16 mapping in NAT API output

Dear Matus,

Thanks for looking into it. So, is there any way I can apply any 
encoding/decoding formula on these values to obtain the correct mapping?

Thanks,
Hamid.

On Wed, May 2, 2018 at 10:02 AM, Matus Fabian -X (matfabia - PANTHEON 
TECHNOLOGIES at Cisco) > wrote:
There is bug, fields are decoded wrong way in 
vl_api_nat44_user_session_details_t_handler (nat_test.c)
Just note, nat44_user_session_dump works only with non-deterministic NAT.

Matus


From: vpp-dev@lists.fd.io 
> On Behalf Of Hamid via 
Lists.Fd.Io
Sent: Wednesday, May 2, 2018 6:50 AM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Figure out u16 mapping in NAT API output

Cannot find a decoder for these fields so I think these incomprehensible value 
for port numbers and protocol number should be reported as a bug?

Re: [vpp-dev] Dynamically attach to a PCI device

2018-05-02 Thread Avi Cohen (A) 
Ray
I know that with ovs-dpdk you can add/remove  a dpdk interface (physical or 
vhost-user) on runtime
Best Regards
Avi

> -Original Message-
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ray 
> Kinsella
> Sent: Tuesday, 01 May, 2018 5:41 PM
> To: Avi Cohen (A); vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Dynamically attach to a PCI device
> 
> Hi Avi,
> 
> Good question - really depends on how you want to do it.
> 
> To my knowledge it is not supported with DPDK. You can achieve similar
> functionality using af_packet - but clearly it won't be anything like as fast.
> 
> Ray K
> 
> On 01/05/2018 08:11, Avi Cohen (A) wrote:
> > With Ovs-Dpdk this is supported
> > If this is not supported in VPP I can implement it Avi
> >> -Original Message-
> >> From: Avi Cohen (A)
> >> Sent: Monday, 23 April, 2018 9:44 AM
> >> To: 'vpp-dev@lists.fd.io'
> >> Subject: RE: Dynamically attach to a PCI device
> >>
> >> I'll clarify my question
> >> For a PCI device e.g. :04:00:0  - is it possible to add this
> >> device  to VPP on runtime with a specific cli command ?
> >> Currently I  only can add these kind of devices  by specifying it in
> >> the  while-list in startup.conf Best Regards Avi
> >>
> >>> -Original Message-
> >>> From: Avi Cohen (A)
> >>> Sent: Monday, 16 April, 2018 10:48 AM
> >>> To: vpp-dev@lists.fd.io
> >>> Subject: Dynamically attach to a PCI device
> >>>
> >>> Hello All
> >>>
> >>> Currently I attach the physical NICs PCI devices by setting the
> >>> white list in the startup.conf How can I attach it dynamically in runtime 
> >>> ?
> >>>
> >>> Best Regards
> >>> Avi
> >
> >
> >
> >
> >
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9142): https://lists.fd.io/g/vpp-dev/message/9142
View All Messages In Topic (5): https://lists.fd.io/g/vpp-dev/topic/17425326
Mute This Topic: https://lists.fd.io/mt/17425326/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Trying to build vpp on amd64 platform via qemu static library qemu-aarch64-static in Docker container

2018-05-02 Thread Stanislav Chlebec 
Hello Brian
1.
I was able to natively compile VPP.
2.
Cross-platform compilation:
I will try that patch from Ole on my cross platform instance and/or check if 
mentioned patch from Ole is included in my build later and I will report the 
result.

Thanks
Stanislav

-Original Message-
From: Brian Brooks [mailto:brian.bro...@arm.com] 
Sent: Thursday, April 26, 2018 4:11 AM
To: Ole Troan 
Cc: Stanislav Chlebec ; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] Trying to build vpp on amd64 platform via qemu static 
library qemu-aarch64-static in Docker container

Thanks, Ole.

Stanislav, does this help? Are you able to natively compile on arm64 instead of 
cross?

Brian

-Original Message-
From: Ole Troan 
Sent: Wednesday, April 25, 2018 11:56 AM
To: Brian Brooks 
Cc: Stanislav Chlebec ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Trying to build vpp on amd64 platform via qemu static 
library qemu-aarch64-static in Docker container

Brian,

> This appears to be related to cross compiling VPP.
> vppapigen is built for the cross target, but then run on the host as part of 
> the build.
>
> Can someone who is familiar with the build system confirm? If so, is it worth 
> fixing a cross build such that vppapigen is compiled for host target and run 
> on host target when cross compiling for the cross target?


vppapigen has been replaced with a PLY based compiler. Which does not need to 
be built.
Would you be able to try with that?

https://gerrit.fd.io/r/#/c/8781/

Best regards,
Ole

> From: vpp-dev@lists.fd.io  On Behalf Of Brian 
> Brooks
> Sent: Friday, April 20, 2018 5:18 PM
> To: Stanislav Chlebec ;
> vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Trying to build vpp on amd64 platform via qemu 
> static library qemu-aarch64-static in Docker container
>
> Can you copy/paste the compiler or linker error?
>
> From: vpp-dev@lists.fd.io  On Behalf Of Stanislav 
> Chlebec
> Sent: Friday, April 20, 2018 6:05 AM
> To: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Trying to build vpp on amd64 platform via qemu 
> static library qemu-aarch64-static in Docker container
>
> Hello Brian
> I have not yet tried to build it in the arm64 VM.
> What I found out more that build fails in the file src/vppinfra/time.h 
> ...
> 
> #elif defined (__aarch64__)
> always_inline u64
> clib_cpu_time_now (void)
> {
>   u64 tsc;
>
>   /* Works on Cavium ThunderX. Other platforms: YMMV */
>   asm volatile ("mrs %0, cntvct_el0":"=r" (tsc));
>
>   return tsc;
> }
> ...
>
> Stanislav
>
>
> From: Brian Brooks [mailto:brian.bro...@arm.com]
> Sent: Monday, April 16, 2018 7:51 PM
> To: Stanislav Chlebec ;
> vpp-dev@lists.fd.io
> Subject: RE: Trying to build vpp on amd64 platform via qemu static 
> library qemu-aarch64-static in Docker container
>
> Hi Stanislav,
>
> Does the build work if you git clone and make build-release inside the arm64 
> VM (no docker)?
>
> Brian
>
> From: vpp-dev@lists.fd.io  On Behalf Of Stanislav 
> Chlebec
> Sent: Monday, April 16, 2018 2:27 AM
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] Trying to build vpp on amd64 platform via qemu 
> static library qemu-aarch64-static in Docker container
>
> Hello all
> I am trying to prepare arm64 docker image (based on arm64v8/ubuntu:latest) in 
> which will be vpp compiled and installed.
> I  do it on amd64 platform using qemu static library for qemu-aarch64-static 
> for emulation of arm64 instructions.
>
> (
> I found how to do it here:
> https://blog.hypriot.com/post/setup-simple-ci-pipeline-for-arm-images/
> http://www.hotblackrobotics.com/en/blog/2018/01/22/docker-images-arm/
> )
>
> Everything goes more the less  well but it fails in this Dockerfile step:
> {
> RUN /bin/bash -c "\
> git clone https://github.com/vpp-dev/vpp.git \
> && cd vpp \
> && git checkout ${VPP_COMMIT} \
> && UNATTENDED=y make vpp_configure_args_vpp='--disable-japi 
> --disable-vom' install-dep bootstrap dpdk-install-dev build build-release;"
> }
>
> It seems that build of vpp is complete without errors but the next processes 
> (installing od dpdk ?) will end with error 21326 Illegal instruction:
> {
> ….
> Build complete [arm64-armv8a-linuxapp-gcc] == 
> Installing /opt/vpp-agent/dev/vpp/dpdk/deb/debian/tmp/usr/
> ….
> ….
> ==
>   version vpp 18.01
>   prefix  
> /opt/vpp-agent/dev/vpp/build-root/install-vpp_debug-native/vpp
>   libdir  
> /opt/vpp-agent/dev/vpp/build-root/install-vpp_debug-native/vpp/lib64
>   includedir  ${prefix}/include
>   CFLAGS   -g -O0 -DCLIB_DEBUG -DFORTIFY_SOURCE=2 
> -fstack-protector-all -fPIC -Werror
>   CPPFLAGS

Re: [vpp-dev] how to apply a dpdk makefile patch?

2018-05-02 Thread Zhiyong Yang 
BTW,

Because I want to test the following DPDK patch in VPP.
http://www.dpdk.org/dev/patchwork/patch/39154/

thanks
Zhiyong

From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Zhiyong Yang
Sent: Wednesday, May 2, 2018 1:36 PM
To: dmarion.li...@gmail.com
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] how to apply a dpdk makefile patch?

Hi, folks,
I try to apply a dpdk makefile patch to add an option to dpdk 
shared lib, how can I enable it in VPP ?

Thanks
Zhiyong