Re: [vpp-dev] ping to ip6 uses link local as source..

[otroan]

> I’d suggest a modification to ip6_interface_first_address to indicate whether 
> a link-local is ok. Then you can choose to ignore the link-local when the 
> ping’s destination is global scope.

At some point we need to implement RFC6724.

Best regards,
Ole


signature.asc
Description: Message signed with OpenPGP
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Regarding vxlan_tool.py in SFC vNF

[Ni, Hongjun]

Please see inline comments.

From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, April 28, 2017 1:58 PM
To: Ni, Hongjun ; Yang, Yi Y ; 
vpp-dev@lists.fd.io; nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Hongjun,
Thanks for your time to recreate those commands.
I have some doubts :).
What about the nsp and nsi id's? They can be anything or need to get them from 
the openflow NSH flows in the compute node?
[Hongjun] Yes, can get NSP and NSI from packet's NSH header, when receiving a 
NSH packet.

What about the address '90e2.ba48.7a80'? Is this hardware address of 
TenGigabitEthernet5/0/0?
[Hongjun] Yes. It is MAC address of interface.

Regards,
Srikanth.

From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Friday, April 28, 2017 11:19 AM
To: Srikanth Lingala 
mailto:srikanth.ling...@nxp.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>; 
vpp-dev@lists.fd.io; 
nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Srikanth,

Please use VPP and NSH_SFC project for running SFF, not running vxlan_tool.py.

Below is the commands used to configure your setup for running SFF, just for 
reference.
vppctl set int state TenGigabitEthernet5/0/0 up
vppctl set int ip table TenGigabitEthernet5/0/0 7
vppctl set int ip address TenGigabitEthernet5/0/0 10.10.10.3/24
vppctl ip route add 192.168.2.25/32 via 10.10.10.3 TenGigabitEthernet5/0/0
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.2.25 90e2.ba48.7a80

vppctl create vxlan-gpe tunnel local 10.10.10.3 remote 192.168.2.25 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel0 1 1

vppctl create nsh map nsp 185 nsi 255 mapped-nsp 185 mapped-nsi 254 nsh_action 
swap encap-vxlan-gpe-intf 3

vppctl create nsh entry nsp 185 nsi 255 md-type 1 c1 1 c2 2 c3 3 c4 4 
next-ethernet
vppctl create nsh entry nsp 185 nsi 254 md-type 1 c1 11 c2 12 c3 13 c4 14 
next-ethernet


Yes, local 10.10.10.3 remote 192.168.2.25 is the local and peer tunnel endpoint 
IP.

Fib table is a VRF(Virtual Routing Forwarding) table. Default Fib table is 0.


From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, April 28, 2017 1:56 AM
To: Ni, Hongjun mailto:hongjun...@intel.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>; 
vpp-dev@lists.fd.io; 
nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

+ vpp-dev

Hi Hongjun,
Thanks for the info.
My requirement is that, I am spawning a SFC vNF which is VPP based. So, that 
vNF should be IP-less NSH aware.
My typical setup is as shown in the attached image. I have single Compute Node, 
with 2 vNFs in a Chain. One vNF is NSH aware (running vxlan_tool.py), and 
another vNF is VPP based VM, which is IP-less, as its interface is hooked to 
DPDK. As I am new to FD.io/ VPP, can you please relate the commands you sent to 
my setup? I may not need the entire commands...Isn't it?

Anyways, In the commands you sent, I have some doubts.

What are the IP's 192.168.50.71 and 192.168.50.76, those are tunnel endpoint 
IP's right?
What is fib-id 7?

Can you please filter out the particular commands to configure my setup?

Regards,
Srikanth.

From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, April 25, 2017 9:44 AM
To: Srikanth Lingala 
mailto:srikanth.ling...@nxp.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>
Cc: nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Srikanth,

If you install nsh_plugin, you may use NSH_SFC 17.01 release, which did not 
support NSH-aware SNAT.

For NSH_SFC 17.01 release, you can configure as blow to act as a SFF, which can 
forward NSH packets.

Below configuration script is for reference:

-NSH 
SFF
vppctl set int state TenGigabitEthernet5/0/0 up
vppctl set int ip table TenGigabitEthernet5/0/0 7
vppctl set int ip address TenGigabitEthernet5/0/0 192.168.50.76/24
vppctl ip route add 192.168.50.71/32 via 192.168.50.76 TenGigabitEthernet5/0/0
vppctl ip route add 192.168.50.72/32 via 192.168.50.76 TenGigabitEthernet5/0/0
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.50.71 90e2.ba48.7a80
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.50.72 0800.2761.0705

vppctl create vxlan-gpe tunnel local 192.168.50.76 remote 192.168.50.71 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel0 1 1
vppctl create vxlan-gpe tunnel local 192.168.50.76 remote 192.168.50.72 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel1 1 1

vppctl create nsh map nsp 185 nsi 255 mapped-nsp 185 mapped-nsi 254 nsh_action 
swap encap-vxlan-gpe-intf 3
vppctl create nsh map nsp 185 nsi 254 mapped-nsp 185 mapped-nsi 255 nsh_action 
swap encap-vxlan-gpe-intf 2

vppctl create n

Re: [vpp-dev] Regarding vxlan_tool.py in SFC vNF

[Srikanth Lingala]

Hi Hongjun,
Thanks for your time to recreate those commands.
I have some doubts :).
What about the nsp and nsi id's? They can be anything or need to get them from 
the openflow NSH flows in the compute node?
What about the address '90e2.ba48.7a80'? Is this hardware address of 
TenGigabitEthernet5/0/0?

Regards,
Srikanth.

From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Friday, April 28, 2017 11:19 AM
To: Srikanth Lingala ; Yang, Yi Y 
; vpp-dev@lists.fd.io; nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Srikanth,

Please use VPP and NSH_SFC project for running SFF, not running vxlan_tool.py.

Below is the commands used to configure your setup for running SFF, just for 
reference.
vppctl set int state TenGigabitEthernet5/0/0 up
vppctl set int ip table TenGigabitEthernet5/0/0 7
vppctl set int ip address TenGigabitEthernet5/0/0 10.10.10.3/24
vppctl ip route add 192.168.2.25/32 via 10.10.10.3 TenGigabitEthernet5/0/0
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.2.25 90e2.ba48.7a80

vppctl create vxlan-gpe tunnel local 10.10.10.3 remote 192.168.2.25 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel0 1 1

vppctl create nsh map nsp 185 nsi 255 mapped-nsp 185 mapped-nsi 254 nsh_action 
swap encap-vxlan-gpe-intf 3

vppctl create nsh entry nsp 185 nsi 255 md-type 1 c1 1 c2 2 c3 3 c4 4 
next-ethernet
vppctl create nsh entry nsp 185 nsi 254 md-type 1 c1 11 c2 12 c3 13 c4 14 
next-ethernet


Yes, local 10.10.10.3 remote 192.168.2.25 is the local and peer tunnel endpoint 
IP.

Fib table is a VRF(Virtual Routing Forwarding) table. Default Fib table is 0.


From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, April 28, 2017 1:56 AM
To: Ni, Hongjun mailto:hongjun...@intel.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>; 
vpp-dev@lists.fd.io; 
nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

+ vpp-dev

Hi Hongjun,
Thanks for the info.
My requirement is that, I am spawning a SFC vNF which is VPP based. So, that 
vNF should be IP-less NSH aware.
My typical setup is as shown in the attached image. I have single Compute Node, 
with 2 vNFs in a Chain. One vNF is NSH aware (running vxlan_tool.py), and 
another vNF is VPP based VM, which is IP-less, as its interface is hooked to 
DPDK. As I am new to FD.io/ VPP, can you please relate the commands you sent to 
my setup? I may not need the entire commands...Isn't it?

Anyways, In the commands you sent, I have some doubts.

What are the IP's 192.168.50.71 and 192.168.50.76, those are tunnel endpoint 
IP's right?
What is fib-id 7?

Can you please filter out the particular commands to configure my setup?

Regards,
Srikanth.

From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, April 25, 2017 9:44 AM
To: Srikanth Lingala 
mailto:srikanth.ling...@nxp.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>
Cc: nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Srikanth,

If you install nsh_plugin, you may use NSH_SFC 17.01 release, which did not 
support NSH-aware SNAT.

For NSH_SFC 17.01 release, you can configure as blow to act as a SFF, which can 
forward NSH packets.

Below configuration script is for reference:

-NSH 
SFF
vppctl set int state TenGigabitEthernet5/0/0 up
vppctl set int ip table TenGigabitEthernet5/0/0 7
vppctl set int ip address TenGigabitEthernet5/0/0 192.168.50.76/24
vppctl ip route add 192.168.50.71/32 via 192.168.50.76 TenGigabitEthernet5/0/0
vppctl ip route add 192.168.50.72/32 via 192.168.50.76 TenGigabitEthernet5/0/0
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.50.71 90e2.ba48.7a80
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.50.72 0800.2761.0705

vppctl create vxlan-gpe tunnel local 192.168.50.76 remote 192.168.50.71 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel0 1 1
vppctl create vxlan-gpe tunnel local 192.168.50.76 remote 192.168.50.72 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel1 1 1

vppctl create nsh map nsp 185 nsi 255 mapped-nsp 185 mapped-nsi 254 nsh_action 
swap encap-vxlan-gpe-intf 3
vppctl create nsh map nsp 185 nsi 254 mapped-nsp 185 mapped-nsi 255 nsh_action 
swap encap-vxlan-gpe-intf 2

vppctl create nsh entry nsp 185 nsi 255 md-type 1 c1 1 c2 2 c3 3 c4 4 
next-ethernet
vppctl create nsh entry nsp 185 nsi 254 md-type 1 c1 11 c2 12 c3 13 c4 14 
next-ethernet

Regards,
Hongjun

From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Tuesday, April 25, 2017 2:18 AM
To: Ni, Hongjun mailto:hongjun...@intel.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>
Cc: nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Hongjun,
I am able to install 'nsh_plug

Re: [vpp-dev] Regarding vxlan_tool.py in SFC vNF

[Ni, Hongjun]

Hi Srikanth,

Please use VPP and NSH_SFC project for running SFF, not running vxlan_tool.py.

Below is the commands used to configure your setup for running SFF, just for 
reference.
vppctl set int state TenGigabitEthernet5/0/0 up
vppctl set int ip table TenGigabitEthernet5/0/0 7
vppctl set int ip address TenGigabitEthernet5/0/0 10.10.10.3/24
vppctl ip route add 192.168.2.25/32 via 10.10.10.3 TenGigabitEthernet5/0/0
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.2.25 90e2.ba48.7a80

vppctl create vxlan-gpe tunnel local 10.10.10.3 remote 192.168.2.25 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel0 1 1

vppctl create nsh map nsp 185 nsi 255 mapped-nsp 185 mapped-nsi 254 nsh_action 
swap encap-vxlan-gpe-intf 3

vppctl create nsh entry nsp 185 nsi 255 md-type 1 c1 1 c2 2 c3 3 c4 4 
next-ethernet
vppctl create nsh entry nsp 185 nsi 254 md-type 1 c1 11 c2 12 c3 13 c4 14 
next-ethernet


Yes, local 10.10.10.3 remote 192.168.2.25 is the local and peer tunnel endpoint 
IP.

Fib table is a VRF(Virtual Routing Forwarding) table. Default Fib table is 0.


From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, April 28, 2017 1:56 AM
To: Ni, Hongjun ; Yang, Yi Y ; 
vpp-dev@lists.fd.io; nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

+ vpp-dev

Hi Hongjun,
Thanks for the info.
My requirement is that, I am spawning a SFC vNF which is VPP based. So, that 
vNF should be IP-less NSH aware.
My typical setup is as shown in the attached image. I have single Compute Node, 
with 2 vNFs in a Chain. One vNF is NSH aware (running vxlan_tool.py), and 
another vNF is VPP based VM, which is IP-less, as its interface is hooked to 
DPDK. As I am new to FD.io/ VPP, can you please relate the commands you sent to 
my setup? I may not need the entire commands...Isn't it?

Anyways, In the commands you sent, I have some doubts.

What are the IP's 192.168.50.71 and 192.168.50.76, those are tunnel endpoint 
IP's right?
What is fib-id 7?

Can you please filter out the particular commands to configure my setup?

Regards,
Srikanth.

From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, April 25, 2017 9:44 AM
To: Srikanth Lingala 
mailto:srikanth.ling...@nxp.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>
Cc: nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Srikanth,

If you install nsh_plugin, you may use NSH_SFC 17.01 release, which did not 
support NSH-aware SNAT.

For NSH_SFC 17.01 release, you can configure as blow to act as a SFF, which can 
forward NSH packets.

Below configuration script is for reference:

-NSH 
SFF
vppctl set int state TenGigabitEthernet5/0/0 up
vppctl set int ip table TenGigabitEthernet5/0/0 7
vppctl set int ip address TenGigabitEthernet5/0/0 192.168.50.76/24
vppctl ip route add 192.168.50.71/32 via 192.168.50.76 TenGigabitEthernet5/0/0
vppctl ip route add 192.168.50.72/32 via 192.168.50.76 TenGigabitEthernet5/0/0
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.50.71 90e2.ba48.7a80
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.50.72 0800.2761.0705

vppctl create vxlan-gpe tunnel local 192.168.50.76 remote 192.168.50.71 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel0 1 1
vppctl create vxlan-gpe tunnel local 192.168.50.76 remote 192.168.50.72 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel1 1 1

vppctl create nsh map nsp 185 nsi 255 mapped-nsp 185 mapped-nsi 254 nsh_action 
swap encap-vxlan-gpe-intf 3
vppctl create nsh map nsp 185 nsi 254 mapped-nsp 185 mapped-nsi 255 nsh_action 
swap encap-vxlan-gpe-intf 2

vppctl create nsh entry nsp 185 nsi 255 md-type 1 c1 1 c2 2 c3 3 c4 4 
next-ethernet
vppctl create nsh entry nsp 185 nsi 254 md-type 1 c1 11 c2 12 c3 13 c4 14 
next-ethernet

Regards,
Hongjun

From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Tuesday, April 25, 2017 2:18 AM
To: Ni, Hongjun mailto:hongjun...@intel.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>
Cc: nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Hongjun,
I am able to install 'nsh_plugin' in VPP vNF. Following are the list of plugins 
enabled in VPP vNF.

root@ls1046ardb:~# vppctl
_____   _  ___
__/ __/ _ \  (_)__| | / / _ \/ _ \
_/ _// // / / / _ \   | |/ / ___/ ___/
/_/ /(_)_/\___/   |___/_/  /_/

vpp# show plugins
Plugin path is: /usr/lib/vpp_plugins
Plugins loaded:
  1./usr/lib/vpp_plugins/nsh_plugin.so
  2./usr/lib/vpp_plugins/snat_plugin.so
  3./usr/lib/vpp_plugins/ila_plugin.so
  4./usr/lib/vpp_plugins/ioam_plugin.so
  5./usr/lib/vpp_plugins/libsixrd_plugin.so
  6./usr/lib/vpp_plugins/lb_plugin.so

To make the VPP vNF as 'NSH aware', do I need to configure anything in 'vppctl'?
To simply forwar

Re: [vpp-dev] No dpdk deb file after build in VPP 17.04

[John Lo (loj)]

With VPP 17.04 or later, vpp-dpdk-dkms deb is obsolete. DPDK support is now a 
plugin and included in  vpp-plugins deb.   -John

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of ??
Sent: Thursday, April 27, 2017 10:59 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] No dpdk deb file after build in VPP 17.04

Hello
Before I changed to the formal release of VPP 17.04 , I used VPP 17.04 rc0. 
After build rc0 I can get vpp-dpdk-dkms deb install file,  VPP can take over 
specified interfaces and works fine.
But in VPP 17.04, I didn't find this deb file even the build is success. So my 
question is whether we should build and install DPDK manually before or after 
VPP installed? Now I used VPP 17.04
in this way.
By this way, I used Ubuntu 14.04 to host VPP.

Thanks!



___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] No dpdk deb file after build in VPP 17.04

[陈祥]

Hello
Before I changed to the formal release of VPP 17.04 , I used VPP 17.04 rc0. 
After build rc0 I can get vpp-dpdk-dkms deb install file,  VPP can take over 
specified interfaces and works fine.
But in VPP 17.04, I didn't find this deb file even the build is success. So my 
question is whether we should build and install DPDK manually before or after 
VPP installed? Now I used VPP 17.04
in this way. 
By this way, I used Ubuntu 14.04 to host VPP.


Thanks!___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] NSH_SFC 17.04 Released

[Ni, Hongjun]

Hey all,

The NSH_SFC 17.04 Release is up.

NSH_SFC artifacts can be found on nexus:
https://nexus.fd.io/content/repositories/fd.io.release/io/fd/nsh_sfc/nsh-sfc/17.04/

You can follow the below link to install binaries from packages:
https://wiki.fd.io/view/NSH_SFC/Installing_NSH_SFC_binaries_from_packages

Many thanks to all contributors, testers and LF infra engineers.


The following is the release notes:

## Features

- NSH MD-Type 2
  - Design document:
https://wiki.fd.io/view/File:NSH_MD-type_2_support_in_VPP_v2.pptx

- iOAM Trace over NSH
  - Unit test output:
https://wiki.fd.io/images/3/38/IOAM_Trace_Output.png
  - Thanks Vengada Prasad Govindan for developing this feature.

- NSH-aware SNAT
  - Unit test output:
https://wiki.fd.io/view/File:NSH_SNAT_Output.png
  - Depends on this patch to be merged to make it work:
https://gerrit.fd.io/r/#/c/6439/ Fix mac check issue for virtual tunnel 
interface with no mac address

- Integration Test
  - Thanks Qun Wan and Fangyin Hu for running the integration test of VPP 17.04 
and NSH_SFC 17.04-rc2.

- Integration with other LF projects
  - Thanks Yi Yang for integrating NSH-Proxy feature into ODL SFC project.

Thanks you all,
Hongjun

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [honeycomb-dev] Honeycomb 1.17.04 released

[Ni, Hongjun]

Congratulation to all guys involved !

From: hc2vpp-boun...@lists.fd.io [mailto:hc2vpp-boun...@lists.fd.io] On Behalf 
Of Jerome Tollet (jtollet)
Sent: Friday, April 28, 2017 3:12 AM
To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) 
; honeycomb-dev 
Cc: t...@lists.fd.io; hc2...@lists.fd.io; csit-...@lists.fd.io; 
vpp-dev@lists.fd.io; nsh_sfc-...@lists.fd.io
Subject: Re: [hc2vpp] [honeycomb-dev] Honeycomb 1.17.04 released

Congratulation!


De : 
mailto:honeycomb-dev-boun...@lists.fd.io>> 
au nom de "Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)" 
mailto:mgrad...@cisco.com>>
Date : jeudi 27 avril 2017 à 17:04
À : honeycomb-dev mailto:honeycomb-...@lists.fd.io>>
Cc : "t...@lists.fd.io" 
mailto:t...@lists.fd.io>>, 
"hc2...@lists.fd.io" 
mailto:hc2...@lists.fd.io>>, 
"csit-...@lists.fd.io" 
mailto:csit-...@lists.fd.io>>, 
"nsh_sfc-...@lists.fd.io" 
mailto:nsh_sfc-...@lists.fd.io>>, 
"vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Objet : [honeycomb-dev] Honeycomb 1.17.04 released

The honeycomb 1.17.04 release is up.

Honeycomb artifacts can be found on nexus:
https://nexus.fd.io/content/repositories/fd.io.release/io/fd/honeycomb/

More details can be found in release notes:
https://docs.fd.io/honeycomb/1.17.04/release-notes-aggregator/release_notes.html

Many thanks to all contributors, testers and LF infra engineers,

Marek
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Regarding vxlan_tool.py in SFC vNF

[Srikanth Lingala]

+ vpp-dev

Hi Hongjun,
Thanks for the info.
My requirement is that, I am spawning a SFC vNF which is VPP based. So, that 
vNF should be IP-less NSH aware.
My typical setup is as shown in the attached image. I have single Compute Node, 
with 2 vNFs in a Chain. One vNF is NSH aware (running vxlan_tool.py), and 
another vNF is VPP based VM, which is IP-less, as its interface is hooked to 
DPDK. As I am new to FD.io/ VPP, can you please relate the commands you sent to 
my setup? I may not need the entire commands...Isn't it?

Anyways, In the commands you sent, I have some doubts.

What are the IP's 192.168.50.71 and 192.168.50.76, those are tunnel endpoint 
IP's right?
What is fib-id 7?

Can you please filter out the particular commands to configure my setup?

Regards,
Srikanth.

From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, April 25, 2017 9:44 AM
To: Srikanth Lingala ; Yang, Yi Y 

Cc: nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Srikanth,

If you install nsh_plugin, you may use NSH_SFC 17.01 release, which did not 
support NSH-aware SNAT.

For NSH_SFC 17.01 release, you can configure as blow to act as a SFF, which can 
forward NSH packets.

Below configuration script is for reference:

-NSH 
SFF
vppctl set int state TenGigabitEthernet5/0/0 up
vppctl set int ip table TenGigabitEthernet5/0/0 7
vppctl set int ip address TenGigabitEthernet5/0/0 192.168.50.76/24
vppctl ip route add 192.168.50.71/32 via 192.168.50.76 TenGigabitEthernet5/0/0
vppctl ip route add 192.168.50.72/32 via 192.168.50.76 TenGigabitEthernet5/0/0
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.50.71 90e2.ba48.7a80
vppctl set ip arp fib-id 7 TenGigabitEthernet5/0/0 192.168.50.72 0800.2761.0705

vppctl create vxlan-gpe tunnel local 192.168.50.76 remote 192.168.50.71 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel0 1 1
vppctl create vxlan-gpe tunnel local 192.168.50.76 remote 192.168.50.72 vni 9 
next-nsh encap-vrf-id 7 decap-vrf-id 7
vppctl set int l2 bridge vxlan_gpe_tunnel1 1 1

vppctl create nsh map nsp 185 nsi 255 mapped-nsp 185 mapped-nsi 254 nsh_action 
swap encap-vxlan-gpe-intf 3
vppctl create nsh map nsp 185 nsi 254 mapped-nsp 185 mapped-nsi 255 nsh_action 
swap encap-vxlan-gpe-intf 2

vppctl create nsh entry nsp 185 nsi 255 md-type 1 c1 1 c2 2 c3 3 c4 4 
next-ethernet
vppctl create nsh entry nsp 185 nsi 254 md-type 1 c1 11 c2 12 c3 13 c4 14 
next-ethernet

Regards,
Hongjun

From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Tuesday, April 25, 2017 2:18 AM
To: Ni, Hongjun mailto:hongjun...@intel.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>
Cc: nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Hongjun,
I am able to install 'nsh_plugin' in VPP vNF. Following are the list of plugins 
enabled in VPP vNF.

root@ls1046ardb:~# vppctl
_____   _  ___
__/ __/ _ \  (_)__| | / / _ \/ _ \
_/ _// // / / / _ \   | |/ / ___/ ___/
/_/ /(_)_/\___/   |___/_/  /_/

vpp# show plugins
Plugin path is: /usr/lib/vpp_plugins
Plugins loaded:
  1./usr/lib/vpp_plugins/nsh_plugin.so
  2./usr/lib/vpp_plugins/snat_plugin.so
  3./usr/lib/vpp_plugins/ila_plugin.so
  4./usr/lib/vpp_plugins/ioam_plugin.so
  5./usr/lib/vpp_plugins/libsixrd_plugin.so
  6./usr/lib/vpp_plugins/lb_plugin.so

To make the VPP vNF as 'NSH aware', do I need to configure anything in 'vppctl'?
To simply forward NSH packets, do I need any configuration?

Thanks for your help.

Regards,
Srikanth.

From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Monday, April 24, 2017 7:59 AM
To: Srikanth Lingala 
mailto:srikanth.ling...@nxp.com>>; Yang, Yi Y 
mailto:yi.y.y...@intel.com>>
Cc: nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

Hi Srikanth,

We have implemented a NSH-aware SNAT VNF in NSH_SFC project.
Please see the link for details: 
https://wiki.fd.io/view/File:NSH_SNAT_Output.png

You can merge your FW and NSH_SFC project to create your own NSH-aware FW VNF.

Regards,
Hongjun

From: nsh_sfc-dev-boun...@lists.fd.io 
[mailto:nsh_sfc-dev-boun...@lists.fd.io] On Behalf Of Srikanth Lingala
Sent: Friday, April 21, 2017 3:17 PM
To: Yang, Yi Y mailto:yi.y.y...@intel.com>>
Cc: nsh_sfc-...@lists.fd.io
Subject: Re: [nsh_sfc-dev] Regarding vxlan_tool.py in SFC vNF

So, in the VPP SF, we need to install nsh_sfc VPP plugin. In that case, we need 
to run vxlan_tool.py in the VPP SF.
Please correct me, If I am wrong.

Regards,
Srikanth.

From: Yang, Yi Y [mailto:yi.y.y...@intel.com]
Sent: Friday, April 21, 2017 12:42 PM
To: Srikanth Lingala mailto:srikanth.ling...@nxp.com>>
Cc: nsh_sfc-...@lists.fd.io
Subject: RE: Regarding vxlan_tool.py in SFC vNF

No, nsh_sfc is a

Re: [vpp-dev] A Curious DHCP Hostname Terminator Choice

[Burt Silverman]

If I were coding, in addition to Jon's change, I probably would change "u8"
to "char" for the type of hostname elements in the dhcp_client_config and
dhcp_compl_event in dhcp.api, because way back when I liked to think of u8
as a hint that the array is a vector style string, i.e., not terminated
with a null. I don't know how carefully we maintained the convention years
ago, and I haven't looked at much code recently. I didn't write "unsigned
char" above because strings are usually "char".

Burt

On Thu, Apr 27, 2017 at 2:19 PM, Luke, Chris  wrote:

> > Jon Loeliger said:
> >> On Thu, Apr 27, 2017 at 12:19 PM, Luke, Chris  chris_l...@comcast.com> wrote:
> >> [...] What I am not sure of is NUL in DHCP hostname strings – I
> remember reading somewhere
> >> it’s optional, so I suspect that means the TLV length is used to
> determine the string length;
> >> meaning it might be possible to have a hostname that is 64 printable
> characters long. Maybe.
> >
> > According to my RFC digging, 1 to 63 characters.
> >
> > NUL is not a valid hostname character.
>
> What it actually says is:
>
>sname64  Optional server host name, null terminated string.
>
> So yes, you're semantically correct. I forgot in the original DHCP this
> was a static field and not a TLV. In DHCPv6 however it doesn't exist.
>
> Chris.
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] CSIT rls1704 report published

[Maciek Konstantynowicz (mkonstan)]

The CSIT rls1704 report is published on FD.io docs site: 
https://docs.fd.io/csit/rls1704/report/

Many Thanks to All Contributors and Committers that worked on csit
rls1704 and made it happen !

And of course Many Thanks to VPP contributors and committers that gave
us a solid piece of VPP rls1704 to test and report on :)

Linked report includes results of i) VPP performance and functional
tests, ii) Testpmd performance tests, iii) Honeycomb functional tests,
and iv) reference to VPP unit tests.

Points of note in the report:

- Added tests including Centos7, crypto-HW, cgnat


https://docs.fd.io/csit/rls1704/report/vpp_performance_tests/csit_release_notes.html#changes-in-csit-release

https://docs.fd.io/csit/rls1704/report/vpp_functional_tests/csit_release_notes.html#changes-in-csit-release

https://docs.fd.io/csit/rls1704/report/testpmd_performance_tests/csit_release_notes.html#changes-in-csit-release

- Measured VPP performance improvements


https://docs.fd.io/csit/rls1704/report/vpp_performance_tests/csit_release_notes.html#performance-improvements

- Performance graphs - throughput and latency for VPP and DPDK-Testpmd


https://docs.fd.io/csit/rls1704/report/vpp_performance_tests/packet_throughput_graphs/index.html

https://docs.fd.io/csit/rls1704/report/vpp_performance_tests/packet_latency_graphs/index.html

https://docs.fd.io/csit/rls1704/report/testpmd_performance_tests/packet_throughput_graphs/index.html

https://docs.fd.io/csit/rls1704/report/testpmd_performance_tests/packet_latency_graphs/index.html

- VPP configs used per test case


https://docs.fd.io/csit/rls1704/report/test_configuration/vpp_performance_configuration/index.html

https://docs.fd.io/csit/rls1704/report/test_configuration/vpp_functional_configuration/index.html

- VPP operational data - "show runtime” outputs at NDR rate with CPU core
  clock cycles spent per worker node per packet


https://docs.fd.io/csit/rls1704/report/test_operational_data/vpp_performance_operational_data/index.html

And for those addicted to numbers and stats - here total numbers of VPP tests 
per type in CSIT rls1704:

- 360 of performance non-drop-rate discovery tests.
- 319 of performance partial-drop-rate discovery tests.
- 258 of system functional VIRL tests for VPP.
- executed on-demand, per patch, nightly and semi-weekly depending on 
category and requirements.

Please send your feedback and comments by email to csit-...@lists.fd.io.

-Maciek (CSIT PTL)
On behalf of FD.io CSIT project.

P.S. All test data in the report incl. graphs and tables are auto-
generated by CSIT scripts. CSIT project team did their best to ensure
the scripts are bug free and content is pleasant to human reading eye,
but as content generated by test executors is dynamic some errors are
very likely. If you see any formatting issues or data inconsistencies,
please report them by email to csit-...@lists.fd.io, so that errors can
be corrected.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [honeycomb-dev] Honeycomb 1.17.04 released

[Jerome Tollet (jtollet)]

Congratulation!


De :  au nom de "Marek Gradzki -X (mgradzki 
- PANTHEON TECHNOLOGIES at Cisco)" 
Date : jeudi 27 avril 2017 à 17:04
À : honeycomb-dev 
Cc : "t...@lists.fd.io" , "hc2...@lists.fd.io" 
, "csit-...@lists.fd.io" , 
"nsh_sfc-...@lists.fd.io" , "vpp-dev@lists.fd.io" 

Objet : [honeycomb-dev] Honeycomb 1.17.04 released

The honeycomb 1.17.04 release is up.

Honeycomb artifacts can be found on nexus:
https://nexus.fd.io/content/repositories/fd.io.release/io/fd/honeycomb/

More details can be found in release notes:
https://docs.fd.io/honeycomb/1.17.04/release-notes-aggregator/release_notes.html

Many thanks to all contributors, testers and LF infra engineers,

Marek
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] A Curious DHCP Hostname Terminator Choice

[Luke, Chris]

> Jon Loeliger said:
>> On Thu, Apr 27, 2017 at 12:19 PM, Luke, Chris 
>>  wrote:
>> [...] What I am not sure of is NUL in DHCP hostname strings – I remember 
>> reading somewhere 
>> it’s optional, so I suspect that means the TLV length is used to determine 
>> the string length; 
>> meaning it might be possible to have a hostname that is 64 printable 
>> characters long. Maybe.
>
> According to my RFC digging, 1 to 63 characters.
>
> NUL is not a valid hostname character.

What it actually says is:

   sname64  Optional server host name, null terminated string.

So yes, you're semantically correct. I forgot in the original DHCP this was a 
static field and not a TLV. In DHCPv6 however it doesn't exist.

Chris.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] A Curious DHCP Hostname Terminator Choice

[Jon Loeliger]

On Thu, Apr 27, 2017 at 12:19 PM, Luke, Chris 
wrote:

> It looks, to me, like someone fixed a problem in the wrong place.
>
>
>
> I would certainly entertain the patch, especially if it included logic to
> make sure mp->hostname doesn’t overrun. Not likely since the DHCP option is
> limited to the same size but it’s still good practice. What I am not sure
> of is NUL in DHCP hostname strings – I remember reading somewhere it’s
> optional, so I suspect that means the TLV length is used to determine the
> string length; meaning it might be possible to have a hostname that is 64
> printable characters long. Maybe.
>

According to my RFC digging, 1 to 63 characters.

NUL is not a valid hostname character.

HTH,
jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] A Curious DHCP Hostname Terminator Choice

[Luke, Chris]

It looks, to me, like someone fixed a problem in the wrong place.

I would certainly entertain the patch, especially if it included logic to make 
sure mp->hostname doesn’t overrun. Not likely since the DHCP option is limited 
to the same size but it’s still good practice. What I am not sure of is NUL in 
DHCP hostname strings – I remember reading somewhere it’s optional, so I 
suspect that means the TLV length is used to determine the string length; 
meaning it might be possible to have a hostname that is 64 printable characters 
long. Maybe.

Chris.

From: Jon Loeliger [mailto:j...@netgate.com]
Sent: Thursday, April 27, 2017 11:28
To: Luke, Chris 
Cc: vpp-dev 
Subject: Re: [vpp-dev] A Curious DHCP Hostname Terminator Choice

On Wed, Apr 26, 2017 at 3:37 PM, Luke, Chris 
mailto:chris_l...@comcast.com>> wrote:
Definitely looks spurious to me.

Chris.

Spurious or wrong?

Will folks entertain a patch converting that newline to a 0?

jdl

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Jon Loeliger
Sent: Wednesday, April 26, 2017 4:24 PM
To: vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: [vpp-dev] A Curious DHCP Hostname Terminator Choice

Hi Guys,

Way over in src/vnet/dhcp/dhcp_api.c, we find the function


  clib_memcpy (&mp->hostname, hostname, vec_len (hostname));
  mp->hostname[vec_len (hostname) + 1] = '\n';
  clib_memcpy (&mp->host_address[0], host_address, 16);
  clib_memcpy (&mp->router_address[0], router_address, 16);

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] A Curious DHCP Hostname Terminator Choice

[Jon Loeliger]

On Wed, Apr 26, 2017 at 3:37 PM, Luke, Chris  wrote:

> Definitely looks spurious to me.
>
>
>
> Chris.
>

Spurious or wrong?

Will folks entertain a patch converting that newline to a 0?

jdl


> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Jon Loeliger
> *Sent:* Wednesday, April 26, 2017 4:24 PM
> *To:* vpp-dev 
> *Subject:* [vpp-dev] A Curious DHCP Hostname Terminator Choice
>
>
>
> Hi Guys,
>
>
>
> Way over in src/vnet/dhcp/dhcp_api.c, we find the function
>
>
>
>
>   clib_memcpy (&mp->hostname, hostname, vec_len (hostname));
>
>   mp->hostname[vec_len (hostname) + 1] = '\n';
>
>   clib_memcpy (&mp->host_address[0], host_address, 16);
>
>   clib_memcpy (&mp->router_address[0], router_address, 16);
>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Honeycomb 1.17.04 released

[Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)]

The honeycomb 1.17.04 release is up.

Honeycomb artifacts can be found on nexus:
https://nexus.fd.io/content/repositories/fd.io.release/io/fd/honeycomb/

More details can be found in release notes:
https://docs.fd.io/honeycomb/1.17.04/release-notes-aggregator/release_notes.html

Many thanks to all contributors, testers and LF infra engineers,

Marek
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] ping to ip6 uses link local as source..

[Neale Ranns (nranns)]

Hi nagp,

I’d suggest a modification to ip6_interface_first_address to indicate whether a 
link-local is ok. Then you can choose to ignore the link-local when the ping’s 
destination is global scope.

Regards,
neale

From:  on behalf of Nagaprabhanjan Bellaru 

Date: Thursday, 27 April 2017 at 14:40
To: vpp-dev 
Subject: [vpp-dev] ping to ip6 uses link local as source..

Even though the destination IP6 is multi hop away, ping seems to choose link 
local as its source address - any idea what can be done to override this 
behavior?
Thanks,
-nagp
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] ping to ip6 uses link local as source..

[Nagaprabhanjan Bellaru]

Even though the destination IP6 is multi hop away, ping seems to choose
link local as its source address - any idea what can be done to override
this behavior?

Thanks,
-nagp
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vpp_papi: No such message type or failed CRC checksum

[otroan]

Weitao,

> I installed vpp 17.04 release in a new clean ubuntu 16.04 server, except 
> that, I did nothing.
> 
> When I first connect vpp using python api,  the terminal show those DEBUG 
> messages.
> 
> Is this phenomenon right?

No. Turns out that the CRC table wasn't setup correctly for messages in those 
plugins / modules.
Shwetha promised to push a patch for these.
Thanks for finding!

Best regards,
Ole

> 
> 2017-04-25 16:47 GMT+08:00 :
> Hi,
> 
> This means that you give the Python API a JSON definition for an API message 
> not available on the running VPP instance.
> That might be caused by a plugin not loaded, version mismatch...
> 
> Best regards,
> Ole
> 
> > When I try to connect vpp using python api, it shows the debug messages.
> >
> > My codes:
> >
> > from vpp_papi import VPP
> > vpp = VPP()
> > vpp.connect('test')
> >
> >
> > And the terminal shows:
> >
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > udp_ping_add_del_reply_a08dec44
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_transit_disable_reply_405af39d
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_transit_disable_ee3cf5f9
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_vni_disable_reply_2e8d61fa
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > udp_ping_add_del_req_a7280e39
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_vni_enable_reply_6a273d6e
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_export_enable_disable_20586df7
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > udp_ping_export_reply_7f8a6c87
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_disable_reply_711375e4
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_enable_6bf84bd6
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_vni_disable_27392af3
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_transit_enable_reply_4dc0cf51
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_vni_enable_489195ec
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_disable_1a373a3b
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_enable_reply_ca79fc00
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > ioam_cache_ip6_enable_disable_reply_67f2a36b
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > ioam_cache_ip6_enable_disable_de631cb6
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_transit_enable_2c399a17
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > udp_ping_export_req_e43a0203
> > DEBUG:vpp_papi:No such message type or failed CRC checksum: 
> > vxlan_gpe_ioam_export_enable_disable_reply_2baa825a
> > ___
> > vpp-dev mailing list
> > vpp-dev@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/vpp-dev
> 
> 



signature.asc
Description: Message signed with OpenPGP
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] ubuntu 16.04.1 EAL: Error reading from file descriptor 11: Input/output error

[yug...@telincn.com]

Thanks, 
I have fixed it.

Regards,
Ewan


yug...@telincn.com
 
From: yug...@telincn.com
Date: 2017-04-27 14:50
To: vpp-dev
Subject: [vpp-dev] ubuntu 16.04.1 EAL: Error reading from file descriptor 11: 
Input/output error
Hey, guys.
Why there are so many errors.

(gdb) r -c /etc/vpp/startup.conf 
Starting program: /usr/bin/vpp -c /etc/vpp/startup.conf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
vlib_plugin_early_init:360: plugin path /usr/lib/vpp_plugins
load_one_plugin:188: Loaded plugin: acl_plugin.so (Access Control Lists)
load_one_plugin:188: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit 
(DPDK))
load_one_plugin:188: Loaded plugin: flowperpkt_plugin.so (Flow per Packet)
load_one_plugin:188: Loaded plugin: ila_plugin.so (Identifier-locator 
addressing for IPv6)
load_one_plugin:188: Loaded plugin: ioam_plugin.so (Inbound OAM)
load_one_plugin:114: Plugin disabled (default): ixge_plugin.so
load_one_plugin:188: Loaded plugin: lb_plugin.so (Load Balancer)
load_one_plugin:188: Loaded plugin: libsixrd_plugin.so (IPv6 Rapid Deployment 
on IPv4 Infrastructure (RFC5969))
load_one_plugin:188: Loaded plugin: memif_plugin.so (Packet Memory Interface 
(experimetal))
load_one_plugin:188: Loaded plugin: snat_plugin.so (Network Address Translation)
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_export_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/flowperpkt_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/snat_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_trace_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_pot_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/vxlan_gpe_ioam_export_test_plugin.so
0: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/lb_test_plugin.so
0: vlib_pci_bind_to_uio: Skipping PCI device :02:01.0 as host interface 
ens33 is up
EAL: Detected 2 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
[New Thread 0x7fff920ec700 (LWP 39209)]
EAL: PCI device :02:01.0 on NUMA socket -1
EAL:   Device is blacklisted, not initializing
EAL: PCI device :02:06.0 on NUMA socket -1
EAL:   probe driver: 8086:100f net_e1000_em
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error
EAL: Error reading from file descriptor 11: Input/output error



yug...@telincn.com
 
From: yug...@telincn.com
Date: 2017-04-27 14:30
To: Burt Silverman
Subject: Re: Re: [vpp-dev] build on ubuntu 14.04.1 failed
Hey,
Why so many errors  any guide?
I started vpp in gdb and got these.

EAL: Error reading from file descriptor 11: Input/output error
/usr/bin/vpp[39114]: EAL: Error reading from file descriptor 11: Input/output 
error
EAL: Error reading from file descriptor 11: Input/output error
/usr/bin/vpp[39114]: EAL: Error reading from file descriptor 11: Input/output 
error
EAL: Error reading from file descriptor 11: In