Re: [vpp-dev] VPP Performance data

2020-03-30 Thread Majumdar, Kausik 
Thanks Dave, Jerome. Will go through it.

I was specifically looking on VPP 20.01 as I was able to get FRR 3.0.3 working 
for IPv4 BGP, OSPF with VPP 20.01. Need to try out FRR BGP neighbors and routes 
scale with VPP DP, so trying to get VPP performance number for 20.01. But 
master/latest data would be good.

Regards,
Kausik

From: Dave Barach (dbarach) 
Sent: Monday, March 30, 2020 12:35 PM
To: Jerome Tollet (jtollet) ; Majumdar, Kausik 
; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] VPP Performance data

Message received from external source. Exercise caution when opening 
attachments, clicking links, or exchanging information.

If you care about master/latest, also check out 
https://docs.fd.io/csit/master/trending/<https://secure-web.cisco.com/12Y83d56KQbs4CrWWwH01anzw0y8Yk2uFxJNvWIpDHdjbzzLsDeZgdUTA4ELscz6YODQKL_088uBipatYw0vteZB8EPCj4BENIfZqB8eM-bPleQNAH4EDa-UAPJ0D7BdLHNFo8fnP5AC8RBbk2XzCia5vnzD7cNYNoZeq02BpwVxoXL6ZK_A25xDOPLvh9tH3reSA6n7nbLmzVqhncln2r3R5lSTXtroh05RcCydNgKUjEpeDeEES8XUolPWWWEBU345vUEja0tHdoDWw7vOesAty_yWXz5Ra96WbpgHCOxTB-uyh7nWKSr-EbLIQ-b0TM0wAcryVGW8O_n4WKE_vqA/https%3A%2F%2Fdocs.fd.io%2Fcsit%2Fmaster%2Ftrending%2F>

From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> 
mailto:vpp-dev@lists.fd.io>> On Behalf Of Jerome Tollet 
via Lists.Fd.Io
Sent: Monday, March 30, 2020 2:40 PM
To: Majumdar, Kausik 
mailto:kausik.majum...@commscope.com>>; 
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Cc: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] VPP Performance data

Hello,
You should have a look at 
https://docs.fd.io/csit/rls2001/report/<https://secure-web.cisco.com/1wwd4id_wYGh_3JojpB_aQfJIZTbADNVcty0AUUZDquDnmDK6dP808y2tLchPQD0cYXo9Dh7XClM3LNXKNrJIdSyhcDKp25lUCWCdJqzisf21Ejt3_AB8Ud_jKiUPgTm56REbNYKCXt7ZAfYpbVKiwXjlj1yDcV7nydnDdbwVFycv0-pnlkSjRvMjy-CUSrAM10FhDbbxRduouu2Bz32ccWWxcGisa7Nt-X6E0o_YhmQWnpNjSKD8W8gkmPCxb40W2rPLnef5ymBTqJa0XgnT9udnscJ6z9Yy77MntxTP9Vbfkuc-Q_ciCS8Y8aAzIX_KHv57nDuOwKdgSpe3Z1AZiA/https%3A%2F%2Fdocs.fd.io%2Fcsit%2Frls2001%2Freport%2F>
Jerome

De : mailto:vpp-dev@lists.fd.io>> au nom de "Majumdar, 
Kausik" mailto:kausik.majum...@commscope.com>>
Date : lundi 30 mars 2020 à 19:47
À : "vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>" 
mailto:vpp-dev@lists.fd.io>>
Objet : [vpp-dev] VPP Performance data


Hi,

Can someone please share the VPP performance measurement data in different 
packet sizes for plain vanilla IPv4, IPv6, and tunnel encap/decap for IPSec, 
VxLAN cases. Also do we have VPP packet forwarding data with at least one 
Service VNF in the same host or in a remote host, where traffic is service 
chained to run the services.

I am considering the below topologies to get some performance data -


1.  Tgen --> IPv4/IPv6 --> Host1 (VPP1) <Tunnel (IPSec or VxLAN)-> 
Host2 (VPP2) --> IPv4/IPv6 --> Tgen



2.  Tgen --> IPv4/IPv6 --> Host1 (VPP1) <Tunnel (IPSec or VxLAN)-> 
Host2 (VPP2) --> Host2 VNF (Service VM) --> Host2 (VPP2) --> IPv4/IPv6 --> Tgen



3.  Tgen --> IPv4/IPv6 --> Host1 (VPP1) <Tunnel (IPSec or VxLAN)-> 
Host2 (VPP2) --> Host3 VNF (Service VM) --> Host2 (VPP2) --> IPv4/IPv6 --> Tgen


I am assuming some analysis already performed in the above scenarios with the 
Number of CPUs, Cores, SR-IOV for VNF forwarding, or OVS in Kernel for bridging 
to VNF.  If we have some pointer of these data for VPP 20.01 release that would 
be great.

Thanks,
Kausik
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15946): https://lists.fd.io/g/vpp-dev/message/15946
Mute This Topic: https://lists.fd.io/mt/72658703/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Performance data

2020-03-30 Thread Majumdar, Kausik 

Hi,

Can someone please share the VPP performance measurement data in different 
packet sizes for plain vanilla IPv4, IPv6, and tunnel encap/decap for IPSec, 
VxLAN cases. Also do we have VPP packet forwarding data with at least one 
Service VNF in the same host or in a remote host, where traffic is service 
chained to run the services.

I am considering the below topologies to get some performance data -


  1.  Tgen --> IPv4/IPv6 --> Host1 (VPP1)  
Host2 (VPP2) --> IPv4/IPv6 --> Tgen



  1.  Tgen --> IPv4/IPv6 --> Host1 (VPP1)  
Host2 (VPP2) --> Host2 VNF (Service VM) --> Host2 (VPP2) --> IPv4/IPv6 --> Tgen



  1.  Tgen --> IPv4/IPv6 --> Host1 (VPP1)  
Host2 (VPP2) --> Host3 VNF (Service VM) --> Host2 (VPP2) --> IPv4/IPv6 --> Tgen


I am assuming some analysis already performed in the above scenarios with the 
Number of CPUs, Cores, SR-IOV for VNF forwarding, or OVS in Kernel for bridging 
to VNF.  If we have some pointer of these data for VPP 20.01 release that would 
be great.

Thanks,
Kausik
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15941): https://lists.fd.io/g/vpp-dev/message/15941
Mute This Topic: https://lists.fd.io/mt/72658703/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP with FRR Bring-up - tap interface enable causing crash

2020-03-09 Thread Majumdar, Kausik 

Hi All,

Wanted to update in this thread that I have debugged and found that VPP crash 
was due to undefined symbol for vlib_buffer_alloc_from_free_list(), which is 
called from router plugin during tap interface enable. I have made the 
following code changes in my WS to get this working.

Currently, with this change enabling tap interface works fine.


diff --git a/router/router/tap_inject_node.c b/router/router/tap_inject_node.c
index 8282c4c..8ce3cf9 100644
--- a/router/router/tap_inject_node.c
+++ b/router/router/tap_inject_node.c
@@ -202,9 +202,15 @@ tap_rx (vlib_main_t * vm, vlib_node_runtime_t * node, 
vlib_frame_t * f, int fd)
 {
   u32 len = vec_len (im->rx_buffers);

+#if 0
   len = vlib_buffer_alloc_from_free_list (vm,
 >rx_buffers[len], NUM_BUFFERS_TO_ALLOC,
 VLIB_BUFFER_DEFAULT_FREE_LIST_INDEX);
+#endif
+
+  len = vlib_buffer_alloc_on_numa (vm,
+>rx_buffers[len], NUM_BUFFERS_TO_ALLOC,
+vm->numa_node);

   _vec_len (im->rx_buffers) += len;

Thanks,
Kausik

From: Majumdar, Kausik 
Sent: Wednesday, March 4, 2020 3:56 PM
To: vpp-dev 
Cc: Majumdar, Kausik 
Subject: VPP with FRR Bring-up - tap interface enable causing crash


Hi All,

I am experiencing VPP crash when I am trying to bring the link up for the VPP 
tap interfaces in Linux. Is this a known issue ? I have tried it few items to 
bring the VPP tap interfaces link up and each time I see VPP crashing. Please 
let me know if there is any workaround.


vpp# show interface
  Name   IdxState  MTU (L3/IP4/IP6/MPLS) 
Counter  Count
TenGigabitEthernet7/0/0   1 down 9000/0/0/0
TenGigabitEthernet7/0/1   2 down 9000/0/0/0
local00 down  0/0/0/0
vpp#
vpp# set interface state TenGigabitEthernet7/0/0 up
vpp# set interface state TenGigabitEthernet7/0/1 up
vpp# set interface ip address TenGigabitEthernet7/0/0 10.0.10.2/24
vpp# set interface ip address TenGigabitEthernet7/0/1 10.0.20.2/24
vpp# show tap
tap tap-inject
vpp# show tap-inject
TenGigabitEthernet7/0/0 -> vpp0
TenGigabitEthernet7/0/1 -> vpp1
vpp#

# ip addr add 10.0.10.2/24 dev vpp0
# ip addr add 10.0.20.2/24 dev vpp1
# ip link set dev vpp0 up
# ip link set dev vpp1 up
Cannot find device "vpp1"
#


/var/log/syslog -

Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.7966] manager: 
(vpp0): new Tun device (/org/freedesktop/NetworkManager/Devices/30)
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8181] devices 
added (path: /sys/devices/virtual/net/vpp0, iface: vpp0)
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8181] device 
added (path: /sys/devices/virtual/net/vpp0, iface: vpp0): no ifupdown 
configuration found.
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8221] manager: 
(vpp1): new Tun device (/org/freedesktop/NetworkManager/Devices/31)
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8423] devices 
added (path: /sys/devices/virtual/net/vpp1, iface: vpp1)
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8423] device 
added (path: /sys/devices/virtual/net/vpp1, iface: vpp1): no ifupdown 
configuration found.


Mar  4 13:41:07 root avahi-daemon[1097]: Joining mDNS multicast group on 
interface vpp0.IPv4 with address 10.0.10.2.
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6687] device 
(vpp0): state change: unmanaged -> unavailable (reason 'connection-assumed') 
[10 20 41]
Mar  4 13:41:07 root avahi-daemon[1097]: New relevant interface vpp0.IPv4 for 
mDNS.
Mar  4 13:41:07 root avahi-daemon[1097]: Registering new address record for 
10.0.10.2 on vpp0.IPv4.
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6701] keyfile: 
add connection in-memory (48ac355a-b5dd-4099-8ece-7b9137770887,"vpp0")
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6711] device 
(vpp0): state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6726] device 
(vpp0): Activation: starting connection 'vpp0' 
(48ac355a-b5dd-4099-8ece-7b9137770887)
Mar  4 13:41:07 root vpp[18936]: /usr/bin/vpp: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/vpp_plugins/router.so: undefined symbol: 
vlib_buffer_alloc_from_free_list
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6793] device 
(vpp0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6803] device 
(vpp0): state change: prepare -> config (reason 'none') [40 50 0]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6822] device 
(vpp0): state change: config -> ip-config (reason 'none') [50 70 0]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6925] device 
(vpp0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Mar  4 13:41:07 root

[vpp-dev] VPP v20.01 to get working with FRR BGP

2020-03-09 Thread Majumdar, Kausik 

Hi Folks,

I was able to get the VPP tap interface working and FRR/BGP session got 
established through the tap interface. This path seems working. Though I 
couldn't get the VPP netlink sync working with to get the external routes 
synced from Kernel routing table to the VPP FIB PD table.

I am guessing the external BGP route points to dev vpp interface this netlink 
sync won't work, is that correct assumption? How to make this working, is the 
default gw needs to be accessed through one of the VPP interface?


  *   172.22.1.0/24 via 10.176.192.1 dev eno1  proto zebra  metric 20


vpp# show in
inacl  init-function  interface
vpp# show interface
  Name   IdxState  MTU (L3/IP4/IP6/MPLS) 
Counter  Count
TenGigabitEthernet7/0/0   1  up  9000/0/0/0 drops   
 237
tx-error
 240
TenGigabitEthernet7/0/1   2  up  9000/0/0/0 drops   
 434
tx-error
 437
local00 down  0/0/0/0   drops   
   6
loop0 3  up  9000/0/0/0 tx packets  
 862
tx bytes
   76100
drops   
 103
ip4 
 334
ip6 
  94
vpp# show tap
tap tap-inject
vpp# show tap-inject
loop0 -> vpp2
TenGigabitEthernet7/0/0 -> vpp0
TenGigabitEthernet7/0/1 -> vpp1
vpp#


vpp0  Link encap:Ethernet  HWaddr 90:e2:ba:7c:cf:c8
  inet addr:10.176.196.100  Bcast:0.0.0.0  Mask:255.255.255.0
  inet6 addr: fe80::92e2:baff:fe7c:cfc8/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:237 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:25236 (25.2 KB)

vpp1  Link encap:Ethernet  HWaddr 90:e2:ba:7c:cf:c9
  inet addr:10.176.190.4  Bcast:0.0.0.0  Mask:255.255.255.0
  inet6 addr: fe80::92e2:baff:fe7c:cfc9/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:434 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:38332 (38.3 KB)

vpp2  Link encap:Ethernet  HWaddr de:ad:00:00:00:00
  inet addr:172.16.0.2  Bcast:0.0.0.0  Mask:255.255.255.255
  inet6 addr: fe80::dcad:ff:fe00:0/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:329 errors:0 dropped:1 overruns:0 frame:0
  TX packets:430 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:27169 (27.1 KB)  TX bytes:38008 (38.0 KB)

root@Sanjeev:~# ifconfig | grep vpp
vpp0  Link encap:Ethernet  HWaddr 90:e2:ba:7c:cf:c8
vpp1  Link encap:Ethernet  HWaddr 90:e2:ba:7c:cf:c9
vpp2  Link encap:Ethernet  HWaddr de:ad:00:00:00:00
root@Sanjeev:~#

root@Sanjeev:~# ip route
default via 10.176.192.1 dev eno1 onlink
10.176.190.0/24 dev ens1f0  proto kernel  scope link  src 10.176.190.3 linkdown
10.176.190.0/24 dev vpp1  proto kernel  scope link  src 10.176.190.4
10.176.192.0/20 dev eno1  proto kernel  scope link  src 10.176.196.83
10.176.196.0/24 dev ens1f1  proto kernel  scope link  src 10.176.196.102 
linkdown
10.176.196.0/24 dev vpp0  proto kernel  scope link  src 10.176.196.100
169.254.0.0/16 dev eno1  scope link  metric 1000
172.16.21.0/24 via 10.176.192.1 dev eno1
172.22.1.0/24 via 10.176.192.1 dev eno1  proto zebra  metric 20
192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
root@Sanjeev:~# ip route | grep vpp
10.176.190.0/24 dev vpp1  proto kernel  scope link  src 10.176.190.4
10.176.196.0/24 dev vpp0  proto kernel  scope link  src 10.176.196.100
root@Sanjeev:~# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt Iface
0.0.0.0 10.176.192.10.0.0.0 UG0 0  0 eno1
10.176.190.00.0.0.0 255.255.255.0   U 0 0  0 ens1f0
10.176.190.00.0.0.0 255.255.255.0   U 0 0  0 vpp1
10.176.192.00.0.0.0 255.255.240.0   U 0 0  0 eno1
10.176.196.00.0.0.0 255.255.255.0   U 0 0  0 ens1f1
10.176.196.00.0.0.0 255.255.255.0   U 0 0

[vpp-dev] VPP with FRR Bring-up - tap interface enable causing crash

2020-03-04 Thread Majumdar, Kausik 

Hi All,

I am experiencing VPP crash when I am trying to bring the link up for the VPP 
tap interfaces in Linux. Is this a known issue ? I have tried it few items to 
bring the VPP tap interfaces link up and each time I see VPP crashing. Please 
let me know if there is any workaround.


vpp# show interface
  Name   IdxState  MTU (L3/IP4/IP6/MPLS) 
Counter  Count
TenGigabitEthernet7/0/0   1 down 9000/0/0/0
TenGigabitEthernet7/0/1   2 down 9000/0/0/0
local00 down  0/0/0/0
vpp#
vpp# set interface state TenGigabitEthernet7/0/0 up
vpp# set interface state TenGigabitEthernet7/0/1 up
vpp# set interface ip address TenGigabitEthernet7/0/0 10.0.10.2/24
vpp# set interface ip address TenGigabitEthernet7/0/1 10.0.20.2/24
vpp# show tap
tap tap-inject
vpp# show tap-inject
TenGigabitEthernet7/0/0 -> vpp0
TenGigabitEthernet7/0/1 -> vpp1
vpp#

# ip addr add 10.0.10.2/24 dev vpp0
# ip addr add 10.0.20.2/24 dev vpp1
# ip link set dev vpp0 up
# ip link set dev vpp1 up
Cannot find device "vpp1"
#


/var/log/syslog -

Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.7966] manager: 
(vpp0): new Tun device (/org/freedesktop/NetworkManager/Devices/30)
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8181] devices 
added (path: /sys/devices/virtual/net/vpp0, iface: vpp0)
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8181] device 
added (path: /sys/devices/virtual/net/vpp0, iface: vpp0): no ifupdown 
configuration found.
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8221] manager: 
(vpp1): new Tun device (/org/freedesktop/NetworkManager/Devices/31)
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8423] devices 
added (path: /sys/devices/virtual/net/vpp1, iface: vpp1)
Mar  4 13:38:13 root NetworkManager[1175]:   [1583357893.8423] device 
added (path: /sys/devices/virtual/net/vpp1, iface: vpp1): no ifupdown 
configuration found.


Mar  4 13:41:07 root avahi-daemon[1097]: Joining mDNS multicast group on 
interface vpp0.IPv4 with address 10.0.10.2.
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6687] device 
(vpp0): state change: unmanaged -> unavailable (reason 'connection-assumed') 
[10 20 41]
Mar  4 13:41:07 root avahi-daemon[1097]: New relevant interface vpp0.IPv4 for 
mDNS.
Mar  4 13:41:07 root avahi-daemon[1097]: Registering new address record for 
10.0.10.2 on vpp0.IPv4.
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6701] keyfile: 
add connection in-memory (48ac355a-b5dd-4099-8ece-7b9137770887,"vpp0")
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6711] device 
(vpp0): state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6726] device 
(vpp0): Activation: starting connection 'vpp0' 
(48ac355a-b5dd-4099-8ece-7b9137770887)
Mar  4 13:41:07 root vpp[18936]: /usr/bin/vpp: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/vpp_plugins/router.so: undefined symbol: 
vlib_buffer_alloc_from_free_list
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6793] device 
(vpp0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6803] device 
(vpp0): state change: prepare -> config (reason 'none') [40 50 0]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6822] device 
(vpp0): state change: config -> ip-config (reason 'none') [50 70 0]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6925] device 
(vpp0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6932] devices 
removed (path: /sys/devices/virtual/net/vpp1, iface: vpp1)
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6937] device 
(vpp0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6941] device 
(vpp0): state change: secondaries -> activated (reason 'none') [90 100 0]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.6950] device 
(vpp0): Activation: successful, device activated.
Mar  4 13:41:07 root dbus[1099]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
Mar  4 13:41:07 root avahi-daemon[1097]: Interface vpp0.IPv4 no longer relevant 
for mDNS.
Mar  4 13:41:07 root avahi-daemon[1097]: Leaving mDNS multicast group on 
interface vpp0.IPv4 with address 10.0.10.2.
Mar  4 13:41:07 root systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Mar  4 13:41:07 root avahi-daemon[1097]: Withdrawing address record for 
10.0.10.2 on vpp0.
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.7374] device 
(vpp0): state change: activated -> unmanaged (reason 'unmanaged') [100 10 3]
Mar  4 13:41:07 root NetworkManager[1175]:   [1583358067.7401] devices 
removed (path:

Re: [vpp-dev] VPP build failure in master branch - plugins/quic

2020-03-03 Thread Majumdar, Kausik 

Thanks Nathan for pointing out quick work-around. I will give a try.

Thanks,
Kausik

From: Nathan Skrzypczak 
Sent: Tuesday, March 3, 2020 7:11 AM
To: Nathan Skrzypczak 
Cc: Majumdar, Kausik ; vpp-dev 

Subject: Re: [vpp-dev] VPP build failure in master branch - plugins/quic

Message received from external source. Exercise caution when opening 
attachments, clicking links, or exchanging information.

[1] should fix this behavior in the future, checking the lib presence and 
version before trying to compile the quicly plugin.
-Nathan

[1] 
https://gerrit.fd.io/r/c/vpp/+/24872<https://secure-web.cisco.com/1-JjQxsX15k50yEC5SuCih2Cra41rFu8-onqq021uDLS70ZFhfk_23H3K-w-Ls85hxxy-2jvIKJp_DUiPaih-SqOy8e5ghaN-6sptP2mlsjkFGACRmHaJNmW_TBkf3zzg4MEWDkISPUHg-uKpIV2Nwf_02cz4CCJkpsDAJ2YhpaHxnERHm67OGN9tpGGn1aWybYzMsDM8t7Npuy99X3KXx4ia8GFILRQaI1jI9oZI6Pf1WLBdOFW25foALMWURgcSJcFE7JQZIyta__7pgt6gxWk4HPeSorT1hSXL7OB7LR_zHxm0FzBhmdcb0BSkYrWJLGLERYLG-ZQtNiav9n_vnQ/https%3A%2F%2Fgerrit.fd.io%2Fr%2Fc%2Fvpp%2F%2B%2F24872>

Le mar. 3 mars 2020 à 10:16, Nathan Skrzypczak via 
Lists.Fd.Io<http://secure-web.cisco.com/1UJUB5wl0EcBMwHdpmC2bxJpO3ijNBfcszS62d_FSOHS3Hr7_082dlKplffBha85xzmAMr8ZlCj1Bk8qecytPNoaq05GuF-elBQNXhsGgfVEhO_HAwby7udnmACr7x2ntfC9450mXCZoFF0P_WxZEIlHf6XOf-IFAc0a852u2UhOr4IIrF4gJ0AgRllpO3wFkZFqfINj87RRpSW6fa-KnMLi5z9JvMbnH46ThOV1xLNcsj7UltFjGrGdPrQL-OBjoGd9Lo0Btfxs5DXKSpXj8sUoDZiHXJGXJTNHikst-78RPiNQ4wv9Txz6fsKHqGO3lPthJnRk6A4BfgGqtspr2eQ/http%3A%2F%2FLists.Fd.Io>
 mailto:gmail@lists.fd.io>> a 
écrit :
Hi Kausik,

This error comes from a discrepancy between the installed version of libquicly 
and the one required for the build.
For now we sadly do not have a version-checking mechanism, I'll try to write a 
patch to avoid those errors and keep you posted.

To fix the build issue you can :
* If `dpkg -l | grep vpp-ext-deps` gives you an entry, maybe try rebuild 
external deps `make install-ext-deps`
* If not, the older version of quicly might come with the e-build, try `make 
wipe-release && git clean -ffdx` and re-run `build.sh`
* If this keeps bothering you and you don't need quicly, you can just remove 
`./src/plugins/quic/CMakeLists.txt` and rebuild

Hope this helps

-Nathan


Le mar. 3 mars 2020 à 05:27, Majumdar, Kausik 
mailto:kausik.majum...@commscope.com>> a écrit :

Hi All,

I have pulled latest VPP codebase from the master and tried to run “build.sh” 
from the /vpp/build-root/vagrant folder. I see following build errors. Anyone 
seen this ? Is there any patch available ?

I didn’t see it when I built from v20.01 release.

[1671/1816] Building C object plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o
FAILED: plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o
/opt/rh/devtoolset-7/root/bin/cc -Dquic_plugin_EXPORTS 
-I/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src -I. -Iinclude 
-I/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins -Iplugins 
-I/opt/vpp/external/x86_64/include -Wno-address-of-packed-member -g -fPIC 
-Werror -Wall -march=corei7 -mtune=corei7-avx  -O2 -fstack-protector 
-DFORTIFY_SOURCE=2 -fno-common  -fPIC -MD -MT 
plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o -MF 
plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o.d -o 
plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o   -c 
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic.c
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic.c: In 
function 'quic_init_crypto_context':
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic.c:277:32:
 error: 'quicly_transport_parameters_t {aka struct 
st_quicly_transport_parameters_t}' has no member named 'max_idle_timeout'; did 
you mean 'idle_timeout'?
   quicly_ctx->transport_params.max_idle_timeout = qm->connection_timeout;
^~~~
idle_timeout
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic.c: At 
top level:
cc1: error: unrecognized command line option '-Wno-address-of-packed-member' 
[-Werror]
cc1: all warnings being treated as errors
[1672/1816] Building C object 
plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o
FAILED: plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o
/opt/rh/devtoolset-7/root/bin/cc -Dquic_plugin_EXPORTS 
-I/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src -I. -Iinclude 
-I/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins -Iplugins 
-I/opt/vpp/external/x86_64/include -Wno-address-of-packed-member -g -fPIC 
-Werror -Wall -march=corei7 -mtune=corei7-avx  -O2 -fstack-protector 
-DFORTIFY_SOURCE=2 -fno-common  -fPIC -MD -MT 
plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o -MF 
plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o.d -o 
plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o   -c 
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic_crypto.c
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/pl

[vpp-dev] VPP build failure in master branch - plugins/quic

2020-03-02 Thread Majumdar, Kausik 

Hi All,

I have pulled latest VPP codebase from the master and tried to run "build.sh" 
from the /vpp/build-root/vagrant folder. I see following build errors. Anyone 
seen this ? Is there any patch available ?

I didn't see it when I built from v20.01 release.

[1671/1816] Building C object plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o
FAILED: plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o
/opt/rh/devtoolset-7/root/bin/cc -Dquic_plugin_EXPORTS 
-I/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src -I. -Iinclude 
-I/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins -Iplugins 
-I/opt/vpp/external/x86_64/include -Wno-address-of-packed-member -g -fPIC 
-Werror -Wall -march=corei7 -mtune=corei7-avx  -O2 -fstack-protector 
-DFORTIFY_SOURCE=2 -fno-common  -fPIC -MD -MT 
plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o -MF 
plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o.d -o 
plugins/quic/CMakeFiles/quic_plugin.dir/quic.c.o   -c 
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic.c
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic.c: In 
function 'quic_init_crypto_context':
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic.c:277:32:
 error: 'quicly_transport_parameters_t {aka struct 
st_quicly_transport_parameters_t}' has no member named 'max_idle_timeout'; did 
you mean 'idle_timeout'?
   quicly_ctx->transport_params.max_idle_timeout = qm->connection_timeout;
^~~~
idle_timeout
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic.c: At 
top level:
cc1: error: unrecognized command line option '-Wno-address-of-packed-member' 
[-Werror]
cc1: all warnings being treated as errors
[1672/1816] Building C object 
plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o
FAILED: plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o
/opt/rh/devtoolset-7/root/bin/cc -Dquic_plugin_EXPORTS 
-I/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src -I. -Iinclude 
-I/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins -Iplugins 
-I/opt/vpp/external/x86_64/include -Wno-address-of-packed-member -g -fPIC 
-Werror -Wall -march=corei7 -mtune=corei7-avx  -O2 -fstack-protector 
-DFORTIFY_SOURCE=2 -fno-common  -fPIC -MD -MT 
plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o -MF 
plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o.d -o 
plugins/quic/CMakeFiles/quic_plugin.dir/quic_crypto.c.o   -c 
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic_crypto.c
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic_crypto.c:
 In function 'quic_crypto_decrypt_packet':
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic_crypto.c:258:5:
 error: implicit declaration of function 
'quicly_get_next_expected_packet_number'; did you mean 
'quicly_determine_packet_number'? [-Werror=implicit-function-declaration]
 quicly_get_next_expected_packet_number (qctx->conn);
 ^~
 quicly_determine_packet_number
/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/src/plugins/quic/quic_crypto.c:
 At top level:
cc1: error: unrecognized command line option '-Wno-address-of-packed-member' 
[-Werror]
cc1: all warnings being treated as errors
[1674/1816] Building C object 
plugins/rdma/CMakeFiles/rdma_plugin_avx2.dir/input.c.o
ninja: build stopped: subcommand failed.
make[3]: *** [Makefile:693: vpp-build] Error 1
make[3]: Leaving directory 
'/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/build-root'
make[2]: *** [Makefile:929: install-packages] Error 1
make[2]: Leaving directory 
'/root/vpp_master/vpp/build-root/rpmbuild/vpp-20.05/build-root'
error: Bad exit status from /var/tmp/rpm-tmp.uvq9PV (%build)


RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.uvq9PV (%build)
make[1]: *** [RPM] Error 1
make[1]: Leaving directory `/root/vpp_master/vpp/extras/rpm'
make: *** [pkg-rpm] Error 2
[root@localhost vagrant]#

Thanks,
Kausik

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15669): https://lists.fd.io/g/vpp-dev/message/15669
Mute This Topic: https://lists.fd.io/mt/71693777/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP with FRR Bring-up - not able to enable tap-inject

2020-02-28 Thread Majumdar, Kausik 
[16270]: enable: unknown input 
`tap-inject
Feb 27 19:37:00 localhost.localdomain vnet[16270]: unknown input `vppctl create 
loopback interfa...
Feb 27 19:37:19 localhost.localdomain vnet[16270]: show: unknown input `
Feb 27 19:38:02 localhost.localdomain vnet[16270]: enable: unknown input 
`tap-inject
Feb 27 19:40:32 localhost.localdomain vnet[16270]: unknown input `exit
Feb 28 11:33:46 localhost.localdomain vnet[16270]: unknown input `a c
[root@localhost build-root]# vppctl
_____   _  ___
 __/ __/ _ \  (_)__| | / / _ \/ _ \
 _/ _// // / / / _ \   | |/ / ___/ ___/
 /_/ /(_)_/\___/   |___/_/  /_/

vpp# enable ?
  enable ip6 interface enable ip6 interface 
vpp#


[root@localhost build-root]# ls /usr/lib/vpp_plugins/
abf_plugin.so dhcp_plugin.so ikev2_plugin.so  
mactime_plugin.so  ping_plugin.sosrv6mobile_plugin.so
acl_plugin.so dns_plugin.so  ila_plugin.somap_plugin.so 
 pppoe_plugin.so   stn_plugin.so
avf_plugin.so dpdk_plugin.so ioam_plugin.so   
mdata_plugin.soquic_plugin.sosvs_plugin.so
builtinurl_plugin.so  flowprobe_plugin.soixge_plugin.so   
memif_plugin.sordma_plugin.sotlsmbedtls_plugin.so
cdp_plugin.so gbp_plugin.so  l2e_plugin.sonat_plugin.so 
 router.so tlsopenssl_plugin.so
crypto_ia32_plugin.so gtpu_plugin.so l3xc_plugin.so   nsh_plugin.so 
 sctp_plugin.sotlspicotls_plugin.so
crypto_ipsecmb_plugin.so  hs_apps_plugin.so  lacp_plugin.so   
nsim_plugin.so srv6ad_plugin.so  unittest_plugin.so
crypto_openssl_plugin.so  http_static_plugin.so  lb_plugin.so 
oddbuf_plugin.so   srv6am_plugin.so  vmxnet3_plugin.so
ct6_plugin.so igmp_plugin.so librtnl.so   
perfmon_plugin.so  srv6as_plugin.so
[root@localhost build-root]#


Thanks,
Kausik


From: Majumdar, Kausik 
Sent: Wednesday, February 26, 2020 5:05 PM
To: Balaji Venkatraman (balajiv) ; vpp-dev 

Cc: vppsb-...@lists.fd.io; Majumdar, Kausik 
Subject: RE: [vpp-dev] VPP with FRR Bring-up - Netlink and Router Plugin build 
failures


Hi Balaji,

Thanks for replying. Yes, I have that wiki and followed that, may be it is out 
dated. I have mentioned that in a different thread on yesterday (attached here).

I have tried to build from different release versions, initially with v18.10 as 
mentioned in the wiki. Currently, I am v20.01. These plugins doesn’t build 
properly.

Few issues –


  1.  I didn’t find ‘bootstrap.sh’ file under build-root dir as mentioned in 
the wiki.
  2.  $ cd build-root/
  3.  $ ./bootstrap.sh

2. The VPP vnet/ip dir doesn’t contain ip6_neighbor.h, but it is included in 
tap_inject_netlink.c

/root/vpp/src/vnet/ip
[root@localhost ip]# ls ip6*
ip6_error.hip6_forward.h ip6_hop_by_hop.h ip6_input.h  
ip6_ll_table.c  ip6_ll_types.h  ip6_punt_drop.c
ip6_format.c   ip6.h ip6_hop_by_hop_packet.h  ip6_link.c   
ip6_ll_table.h  ip6_packet.hip6_to_ip4.h
ip6_forward.c  ip6_hop_by_hop.c  ip6_input.c  ip6_link.h   
ip6_ll_types.c  ip6_pg.c

/root/vpp/build-data/../router/router/tap_inject_netlink.c:19:34: fatal error: 
vnet/ip/ip6_neighbor.h: No such file or directory
 #include 



  1.  The netlink build issue was discussed in the thread, but not sure what 
was the resolution of it.
https://lists.fd.io/g/vpp-dev/topic/vppsb_netlink_build_failing/27825040?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,27825040


Thanks,
Kausik

From: Balaji Venkatraman (balajiv) mailto:bala...@cisco.com>>
Sent: Wednesday, February 26, 2020 4:48 PM
To: Majumdar, Kausik 
mailto:kausik.majum...@commscope.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Cc: vppsb-...@lists.fd.io<mailto:vppsb-...@lists.fd.io>
Subject: Re: [vpp-dev] VPP with FRR Bring-up - Netlink and Router Plugin build 
failures

Message received from external source. Exercise caution when opening 
attachments, clicking links, or exchanging information.

[Sorry hit the ‘send’ by mistake..]

Did you try that solution?

Thanks!
--
Regards,
Balaji.


From: "Balaji Venkatraman (balajiv)" 
mailto:bala...@cisco.com>>
Date: Wednesday, February 26, 2020 at 4:46 PM
To: "Majumdar, Kausik" 
mailto:kausik.majum...@commscope.com>>, vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Cc: "vppsb-...@lists.fd.io<mailto:vppsb-...@lists.fd.io>" 
mailto:vppsb-...@lists.fd.io>>
Subject: Re: [vpp-dev] VPP with FRR Bring-up - Netlink and Router Plugin build 
failures

Hi Kausik,
I see a project that incorporated FRR with VPP.

x 
https://github.com/FRRouting/frr/wiki/Alternate-forwarding-planes:-VPP<https://secure-web.cisco.com/179klKjrSOUoQKvSSCS88PuAak9DHzPCSanc6aZ9q2dl_Iy9WW2xz_a54r2gXqYESVIenYoanK6etSd_WEd7f8mwgRzULDHmdqKToOJrgb

Re: [vpp-dev] VPP with FRR Bring-up - Netlink and Router Plugin build failures

2020-02-26 Thread Majumdar, Kausik 

Hi Balaji,

Thanks for replying. Yes, I have that wiki and followed that, may be it is out 
dated. I have mentioned that in a different thread on yesterday (attached here).

I have tried to build from different release versions, initially with v18.10 as 
mentioned in the wiki. Currently, I am v20.01. These plugins doesn’t build 
properly.

Few issues –


  1.  I didn’t find ‘bootstrap.sh’ file under build-root dir as mentioned in 
the wiki.

2.   $ cd build-root/

3.   $ ./bootstrap.sh

2. The VPP vnet/ip dir doesn’t contain ip6_neighbor.h, but it is included in 
tap_inject_netlink.c

/root/vpp/src/vnet/ip
[root@localhost ip]# ls ip6*
ip6_error.hip6_forward.h ip6_hop_by_hop.h ip6_input.h  
ip6_ll_table.c  ip6_ll_types.h  ip6_punt_drop.c
ip6_format.c   ip6.h ip6_hop_by_hop_packet.h  ip6_link.c   
ip6_ll_table.h  ip6_packet.hip6_to_ip4.h
ip6_forward.c  ip6_hop_by_hop.c  ip6_input.c  ip6_link.h   
ip6_ll_types.c  ip6_pg.c

/root/vpp/build-data/../router/router/tap_inject_netlink.c:19:34: fatal error: 
vnet/ip/ip6_neighbor.h: No such file or directory
 #include 



  1.  The netlink build issue was discussed in the thread, but not sure what 
was the resolution of it.
https://lists.fd.io/g/vpp-dev/topic/vppsb_netlink_build_failing/27825040?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,27825040


Thanks,
Kausik

From: Balaji Venkatraman (balajiv) 
Sent: Wednesday, February 26, 2020 4:48 PM
To: Majumdar, Kausik ; vpp-dev 

Cc: vppsb-...@lists.fd.io
Subject: Re: [vpp-dev] VPP with FRR Bring-up - Netlink and Router Plugin build 
failures

Message received from external source. Exercise caution when opening 
attachments, clicking links, or exchanging information.

[Sorry hit the ‘send’ by mistake..]

Did you try that solution?

Thanks!
--
Regards,
Balaji.


From: "Balaji Venkatraman (balajiv)" 
mailto:bala...@cisco.com>>
Date: Wednesday, February 26, 2020 at 4:46 PM
To: "Majumdar, Kausik" 
mailto:kausik.majum...@commscope.com>>, vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Cc: "vppsb-...@lists.fd.io<mailto:vppsb-...@lists.fd.io>" 
mailto:vppsb-...@lists.fd.io>>
Subject: Re: [vpp-dev] VPP with FRR Bring-up - Netlink and Router Plugin build 
failures

Hi Kausik,
I see a project that incorporated FRR with VPP.

x 
https://github.com/FRRouting/frr/wiki/Alternate-forwarding-planes:-VPP<https://secure-web.cisco.com/179klKjrSOUoQKvSSCS88PuAak9DHzPCSanc6aZ9q2dl_Iy9WW2xz_a54r2gXqYESVIenYoanK6etSd_WEd7f8mwgRzULDHmdqKToOJrgbbJziwr8cFPq2ZT2TrDLLnuPQHA7s264o3dgrnbw58u0Y6q9Bp3fl1TqOTVPgtoRvfk5gjPq5N0_oCyhD2WGZjvz-97hrPtpXKJMeKj0dHbbNGSHEpUam3EKnv5y2t5TzlV5mtCi9m9IcFBPxXws7UmYlTdC9mSLb_cy49ON4opImoPj8PVtaqGNCe4cWC9crOmIVuwd327tTfmyMS9enTn2Sug0bLIqjAVm59togUNZBA/https%3A%2F%2Fgithub.com%2FFRRouting%2Ffrr%2Fwiki%2FAlternate-forwarding-planes%3A-VPP>




--
Regards,
Balaji.


From: mailto:vpp-dev@lists.fd.io>> on behalf of "Majumdar, 
Kausik" mailto:kausik.majum...@commscope.com>>
Date: Wednesday, February 26, 2020 at 4:31 PM
To: vpp-dev mailto:vpp-dev@lists.fd.io>>
Cc: "vppsb-...@lists.fd.io<mailto:vppsb-...@lists.fd.io>" 
mailto:vppsb-...@lists.fd.io>>, "Majumdar, Kausik" 
mailto:kausik.majum...@commscope.com>>
Subject: [vpp-dev] VPP with FRR Bring-up - Netlink and Router Plugin build 
failures


Hi folks,

I wanted to start a new thread on the discussion related to VPP with FRR bring 
up and get this working together for VPP as a Data plane with FRR as a Control 
/Routing plane. Please chime in if you have already got VPP and FRR working 
together or can help on the current issues.

I am currently facing issues to build VPP plugins for netlink and router.


  1.  Netlink build error -

I looked into the previous discussion on netlink compilation issues, I didn’t 
find proper resolution for it. I made simple hack in the codebase and with that 
I was able to build netlink lib. I am sure folks have gone through this issue, 
so would like to know if any fix or patch is available.

[root@localhost build-root]# make V=0 PLATFORM=vpp TAG=vpp_debug 
netlink-install router-install

 Building netlink in /root/vpp/build-root/build-vpp_debug-native/netlink 

make[1]: Entering directory 
`/root/vpp/build-root/build-vpp_debug-native/netlink'
  CC   librtnl/netns.lo
  CC   librtnl/rtnl.lo
/root/vpp/build-data/../netlink/librtnl/rtnl.c: In function 'rtnl_socket_open':
/root/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: error: 
'RTNLGRP_MPLS_ROUTE' undeclared (first use in this function)
 grpmask(RTNLGRP_NOTIFY) | grpmask(RTNLGRP_MPLS_ROUTE),
   ^
/root/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: note: each undeclared 
identifier is reported only once for each function it appears in
make[1]: *** [librtnl/rtnl.lo] Error 1
make[1]: *** Waiting for unfinished jobs
/root/vpp/build-data/../netlink/librtnl

[vpp-dev] VPP with FRR Bring-up - Netlink and Router Plugin build failures

2020-02-26 Thread Majumdar, Kausik 

Hi folks,

I wanted to start a new thread on the discussion related to VPP with FRR bring 
up and get this working together for VPP as a Data plane with FRR as a Control 
/Routing plane. Please chime in if you have already got VPP and FRR working 
together or can help on the current issues.

I am currently facing issues to build VPP plugins for netlink and router.


  1.  Netlink build error -

I looked into the previous discussion on netlink compilation issues, I didn't 
find proper resolution for it. I made simple hack in the codebase and with that 
I was able to build netlink lib. I am sure folks have gone through this issue, 
so would like to know if any fix or patch is available.

[root@localhost build-root]# make V=0 PLATFORM=vpp TAG=vpp_debug 
netlink-install router-install

 Building netlink in /root/vpp/build-root/build-vpp_debug-native/netlink 

make[1]: Entering directory 
`/root/vpp/build-root/build-vpp_debug-native/netlink'
  CC   librtnl/netns.lo
  CC   librtnl/rtnl.lo
/root/vpp/build-data/../netlink/librtnl/rtnl.c: In function 'rtnl_socket_open':
/root/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: error: 
'RTNLGRP_MPLS_ROUTE' undeclared (first use in this function)
 grpmask(RTNLGRP_NOTIFY) | grpmask(RTNLGRP_MPLS_ROUTE),
   ^
/root/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: note: each undeclared 
identifier is reported only once for each function it appears in
make[1]: *** [librtnl/rtnl.lo] Error 1
make[1]: *** Waiting for unfinished jobs
/root/vpp/build-data/../netlink/librtnl/netns.c:69:5: error: 'RTA_VIA' 
undeclared here (not in a function)
   _(RTA_VIA, via, 1)\
 ^
/root/vpp/build-data/../netlink/librtnl/netns.c:82:13: note: in definition of 
macro '_'
 .type = t, .unique = u, \
 ^
/root/vpp/build-data/../netlink/librtnl/netns.c:86:3: note: in expansion of 
macro 'ns_foreach_rta'
   ns_foreach_rta
   ^
make[1]: *** [librtnl/netns.lo] Error 1
make[1]: Leaving directory `/root/vpp/build-root/build-vpp_debug-native/netlink'
make: *** [netlink-build] Error 2

I have applied the following diff change in my local codebase and netlink 
compiled fine.

diff --git a/netlink/librtnl/netns.c b/netlink/librtnl/netns.c
index 1b40227..8ecf02b 100644
--- a/netlink/librtnl/netns.c
+++ b/netlink/librtnl/netns.c
@@ -66,7 +66,6 @@ u8 *format_ns_link (u8 *s, va_list *args)
 #define ns_foreach_rta  \
   _(RTA_DST, dst, 1)\
   _(RTA_SRC, src, 1)\
-  _(RTA_VIA, via, 1)\
   _(RTA_GATEWAY, gateway, 1)\
   _(RTA_IIF, iif, 1)\
   _(RTA_OIF, oif, 1)\
diff --git a/netlink/librtnl/rtnl.c b/netlink/librtnl/rtnl.c
index a849dc6..9879e14 100644
--- a/netlink/librtnl/rtnl.c
+++ b/netlink/librtnl/rtnl.c
@@ -266,7 +266,7 @@ static int rtnl_socket_open(rtnl_ns_t *ns)
 .nl_groups = grpmask(RTNLGRP_LINK)| grpmask(RTNLGRP_IPV6_IFADDR) |
 grpmask(RTNLGRP_IPV4_IFADDR) | grpmask(RTNLGRP_IPV4_ROUTE) |
 grpmask(RTNLGRP_IPV6_ROUTE) | grpmask(RTNLGRP_NEIGH) |
-grpmask(RTNLGRP_NOTIFY) | grpmask(RTNLGRP_MPLS_ROUTE),
+grpmask(RTNLGRP_NOTIFY),
   };

   if (bind(ns->rtnl_socket, (struct sockaddr*) , sizeof(addr))) {


[root@localhost vpp]# ls 
/root/vpp/build-root/install-vpp_debug-native/netlink/lib64
librtnl.a   librtnl.solibrtnl.so.0.0.0   testrtnl_plugin.la  
testrtnl_plugin.so.0
librtnl.la  librtnl.so.0  testrtnl_plugin.a  testrtnl_plugin.so  
testrtnl_plugin.so.0.0.0



  1.  router build error -

Is there any fix available for the tap_inject_netlink.c failure?

[root@localhost build-root]# make V=0 PLATFORM=vpp TAG=vpp_debug 
netlink-install router-install
 Arch for platform 'vpp' is native 

 Building router in /root/vpp/build-root/build-vpp_debug-native/router 
make[1]: Entering directory `/root/vpp/build-root/build-vpp_debug-native/router'
  CC   router/tap_inject_netlink.lo
  CC   router/tap_inject_node.lo
/root/vpp/build-data/../router/router/tap_inject_netlink.c:19:34: fatal error: 
vnet/ip/ip6_neighbor.h: No such file or directory
 #include 
  ^
compilation terminated.
/root/vpp/build-data/../router/router/tap_inject_node.c: In function 'tap_rx':
/root/vpp/build-data/../router/router/tap_inject_node.c:182:29: error: 
'VLIB_BUFFER_DATA_SIZE' undeclared (first use in this function)
 #define MTU_BUFFERS ((MTU + VLIB_BUFFER_DATA_SIZE - 1) / VLIB_BUFFER_DATA_SIZE)
 ^
/root/vpp/build-data/../router/router/tap_inject_node.c:190:20: note: in 
expansion of macro 'MTU_BUFFERS'
   struct iovec iov[MTU_BUFFERS];
^
/root/vpp/build-data/../router/router/tap_inject_node.c:182:29: note: each 
undeclared identifier is reported only once for each function it appears in
 #define MTU_BUFFERS ((MTU +

Re: [vpp-dev] VPP Plugins build errors from IPSec module

2020-02-26 Thread Majumdar, Kausik 

Hi Chuan,

Thanks for your interest. So far I have found it is not straight forward way to 
build and bring up VPP with the plugins and that is required for FRR to work 
with VPP.

Let me start a new thread to resolve the current issues with netlink and router 
plugins compilation errors, I see the same issue is being discussed in the 
past. Hopefully we can get a resolution on this.

Yes, I can volunteer to put together the steps in an email or wiki if once I am 
able to bring-up VPP with FRR.

Thanks,
Kausik

From: Chuan Han 
Sent: Wednesday, February 26, 2020 7:43 AM
To: Ray Kinsella 
Cc: Majumdar, Kausik ; vpp-dev 
; vppsb-...@lists.fd.io
Subject: Re: [vpp-dev] VPP Plugins build errors from IPSec module

Message received from external source. Exercise caution when opening 
attachments, clicking links, or exchanging information.

I am also interested in frr integration with vpp. Could you please share 
detailed steps once you figure it out?

On Tue, Feb 25, 2020, 11:34 PM Ray Kinsella 
mailto:m...@ashroe.eu>> wrote:


I am not sure how accurate / current the information from the wiki is.

However looks like you are missing the Intel Multi-buffer Crypto Library.
Try a `make install-ext-deps`, then wipe and rebuild.

Ray K

On 25/02/2020 22:34, Majumdar, Kausik wrote:
> Hi folks,
>
>
>
> I am trying to build VPP netlink and router plugins based on vpp branch 
> v20.01 to integrate and run with routing control plane FRR. I am following 
> the guidelines based on 
> https://github.com/FRRouting/frr/wiki/Alternate-forwarding-planes:-VPP<https://secure-web.cisco.com/1ifNrQ2u1inEzXoO8GhOR89qpSUGwoqj2kArmFFKVtHMx_B27I_KVv642S4_AMbdQNN0E2VQMFCosTeFjObP78_rFGYR99WSJECyjDxPX5ISjlSUldqADm0VR2bPyq6EpMiCQzTEgwrlTVm8-YagNsFcxM-inO3yDWVnppveQ7pwpkinoqz-mZSPlThW7ymoGFsGHkbvSjVsM5OVK-zVhSwyhsvyLmsJ5dOQJ7iCNzgDXw_Tvr3Domj_CMxrJMIwAsQx5-W4DSlXIDn8R7RpWntgiWGDCUn7qDCqi43ImMld7k_oMjSzbOuguhanWOg_nReFqES3qSzbcroUy_bry6Q/https%3A%2F%2Fgithub.com%2FFRRouting%2Ffrr%2Fwiki%2FAlternate-forwarding-planes%3A-VPP>
>
>
>
> I am finding issues while trying to compile the IPSec plugin code, it is 
> exiting with the below error. I have tried with latest VPP master branch, the 
> result is pretty much same. Is there any resolution to this issue or am I 
> missing something? If I try to use VPP v18.10 branch then I hit other netlink 
> issue which I think discussed in this thread in the past. Hence moved to 
> latest VPP code base, tried to link VPPSB and build the netlink-install and 
> router-install plugins, hitting IPSec build failures. Any recommendation 
> would be helpful.
>
>
>
> I am running Centos 7.4 machine.
>
>
>
> [root@localhost build-root]# git branch
>
> * (detached from v20.01)
>
>   master
>
>
>
> [root@localhost build-root]# *make V=0 PLATFORM=vpp TAG=vpp_debug 
> netlink-install router-install*
>
>  Arch for platform 'vpp' is native 
>
>  Finding source for external 
>
>  Makefile fragment found in 
> /root/vpp/build-data/packages/external.mk<http://secure-web.cisco.com/1ZBGQG2r-isaK7c0yVgYVguPqUxgVipOrkANz-1c5obHxgV-V_BLqgzPK4249_v8Wei4QOAD2qvBn_BwFKaUVQalyPd_ao26Gt8-_YwC__sszjgOBKiEgbVrBohAnIpmdxWlJVjqN9ju6vuwZWt6uaZVEua-X2uP1BNjOjn-g9S-qvnX3t_haqQ5nzwbOBNgOkIAFOlg1xF8nN3qW9oJo0fyNEuAOfdKVh_US6sr--NQvt1b4fRFODbDUuPLr1f9MqGOxnEGjsMLbILKaRCuaEuhuiBPCYPmXnZbGbPYuqxdX8QhD_qS4onIPn5AObgoo/http%3A%2F%2Fexternal.mk>
>  
>
>  Source found in /root/vpp/build 
>
>  Arch for platform 'vpp' is native 
>
>  Finding source for vpp 
>
>  Makefile fragment found in 
> /root/vpp/build-data/packages/vpp.mk<http://secure-web.cisco.com/1xgmLdDktNGh69JtisCB0H8-3PUOJ-8-k1Gus9zobi3lc9nclJ1rsBMP756a76umf95xLk3R1RnQ1Bl07FRDjkEcsRK0Utv9Dgz8Yy4cSvLhd-IAiiyhjWjrbzQwvu3UDajwi9ZGixFikCKqzn09H6gPDJZWXNIbXa68zUtTIMZrjpyik-soDUYq5UqFnGy3M-y4m6cxg9F3DWhZKvfNSN890wiP-bwJh06R23cCtrw3hc-bfHC0ZlOzlvjAbDNQuH__AAUCb4k-DiWobzubsdzyuBIZLMtUnSRhRl1KXmEhBnxNJIRtGVAK03WmF-TUX/http%3A%2F%2Fvpp.mk>
>  
>
>  Source found in /root/vpp/src 
>
>  Arch for platform 'vpp' is native 
>
>  Finding source for netlink 
>
>  Makefile fragment found in 
> /root/vpp/build-data/packages/netlink.mk<http://secure-web.cisco.com/1EwGAWTBCjPeTiC9J0Duk6vk-LMqhR8jIavKSuoAkEPtTSY4e45M_lTF0cOMdjuPo6hteO8YtdcgwzxHDEvsfmPkVFY1EhEHMBHs2vNXn-8KX5d10auGsDDjbBjKWinJTsMZkYggBnDe7jjtNYjyDRbkRfYutwFU6RorKQ7_gr57L051wYP6HMVrL6dW5qzlqdp1U74VVu-_51VqN7uAuV9L9-dOsncYUfopc0NGfxAFSXV_bG6g_pASmLpTI76bnDCPWHbWeIe4aPrwCllXiz7bSWmRZ75CvvFgkBFEq1moX-hWH_SOOshnDE8ME/http%3A%2F%2Fnetlink.mk>
>  
>
>  Source found in /root/vpp/netlink 
>
>  Configuring external: nothing to do 
>
>  Building external: nothing to do 
>
>  Installing external:

Re: [vpp-dev] VPP Plugins build errors from IPSec module

2020-02-25 Thread Majumdar, Kausik 
 
 Source found in /root/vpp/netlink 
 Configuring external: nothing to do 
 Building external: nothing to do 
 Installing external: nothing to do 
 Configuring vpp: nothing to do 
 Building vpp in /root/vpp/build-root/build-vpp_debug-native/vpp 
ninja: no work to do.
 Installing vpp: nothing to do 
 Configuring netlink: nothing to do 
 Building netlink in /root/vpp/build-root/build-vpp_debug-native/netlink 

make[1]: Entering directory 
`/root/vpp/build-root/build-vpp_debug-native/netlink'
  CC   librtnl/rtnl.lo
  CC   librtnl/netns.lo
/root/vpp/build-data/../netlink/librtnl/netns.c:69:5: error: 'RTA_VIA' 
undeclared here (not in a function)
   _(RTA_VIA, via, 1)\
 ^
/root/vpp/build-data/../netlink/librtnl/netns.c:82:13: note: in definition of 
macro '_'
 .type = t, .unique = u, \
 ^
/root/vpp/build-data/../netlink/librtnl/netns.c:86:3: note: in expansion of 
macro 'ns_foreach_rta'
   ns_foreach_rta
   ^
/root/vpp/build-data/../netlink/librtnl/rtnl.c: In function 'rtnl_socket_open':
/root/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: error: 
'RTNLGRP_MPLS_ROUTE' undeclared (first use in this function)
 grpmask(RTNLGRP_NOTIFY) | grpmask(RTNLGRP_MPLS_ROUTE),
   ^
/root/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: note: each undeclared 
identifier is reported only once for each function it appears in
make[1]: *** [librtnl/rtnl.lo] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: *** [librtnl/netns.lo] Error 1
make[1]: Leaving directory `/root/vpp/build-root/build-vpp_debug-native/netlink'
make: *** [netlink-build] Error 2
[root@localhost build-root]# 
unction 'rtnl_socket_open':
/root/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: error: 
'RTNLGRP_MPLS_ROUTE' undeclared (first use in this function)
 grpmask(RTNLGRP_NOTIFY) | grpmask(RTNLGRP_MPLS_ROUTE),
   ^
/root/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: note: each undeclared 
identifier is reported only once for each function it appears in
make[1]: *** [librtnl/rtnl.lo] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: *** [librtnl/netns.lo] Error 1
make[1]: Leaving directory `/root/vpp/build-root/build-vpp_debug-native/netlink'
make: *** [netlink-build] Error 2
[root@localhost build-root]#

-Original Message-
From: Neale Ranns (nranns)  
Sent: Tuesday, February 25, 2020 10:32 PM
To: Majumdar, Kausik ; vpp-dev@lists.fd.io
Cc: vppsb-...@lists.fd.io
Subject: Re: [vpp-dev] VPP Plugins build errors from IPSec module

Message received from external source. Exercise caution when opening 
attachments, clicking links, or exchanging information.

 

Hi Kausik,

Did you run:
  make install-ext-dep

/neale

From:  on behalf of "Majumdar, Kausik" 

Date: Tuesday 25 February 2020 at 23:35
To: "vpp-dev@lists.fd.io" 
Cc: "vppsb-...@lists.fd.io" , "Majumdar, Kausik" 

Subject: [vpp-dev] VPP Plugins build errors from IPSec module

Hi folks,
 
I am trying to build VPP netlink and router plugins based on vpp branch v20.01 
to integrate and run with routing control plane FRR. I am following the 
guidelines based on 
https://secure-web.cisco.com/1NEdokSbQqopKRLdvL5uyb7-Fga29wluiY0hC6MVPft3y5NxoQRIpsqSeJs5Wj_rRNGrjfdCGAcrZvCTwlF1LDg5zrWe6zIrbudgg0KqNY6MFYjZ6bZaGemmECxB0ptw8v_U5Ey8JaXrq72fEgmJISgAxmrU3PpWEnsXst-MdOtCU6lppszxmSh7lOG4gLgTcIDCdY1dUs9UCYmOoXqW_2Hrx-hu5TcH8Ex0UFt5tP5W3sZQrsqkPi7JqkxIUSqgvanDmYIcJMtkdOIIvpiG7Av4x0RhuxmIByx8jScHPKMsGsXTlFAgEMRJNKMgfUhMqEiK_45N-rZciiM9xh-VasQ/https%3A%2F%2Fgithub.com%2FFRRouting%2Ffrr%2Fwiki%2FAlternate-forwarding-planes%3A-VPP
 
 
I am finding issues while trying to compile the IPSec plugin code, it is 
exiting with the below error. I have tried with latest VPP master branch, the 
result is pretty much same. Is there any resolution to this issue or am I 
missing something? If I try to use VPP v18.10 branch then I hit other netlink 
issue which I think discussed in this thread in the past. Hence moved to latest 
VPP code base, tried to link VPPSB and build the netlink-install and 
router-install plugins, hitting IPSec build failures. Any recommendation would 
be helpful.
 
I am running Centos 7.4 machine. 
 
[root@localhost build-root]# git branch
* (detached from v20.01)
  master
 
[root@localhost build-root]# make V=0 PLATFORM=vpp TAG=vpp_debug 
netlink-install router-install  Arch for platform 'vpp' is native   
Finding source for external   Makefile fragment found in 
/root/vpp/build-data/packages/external.mk   Source found in 
/root/vpp/build   Arch for platform 'vpp' is native   Finding 
source for vpp   Makefile fragment found in 
/root/vpp/build-data/packages/vpp.mk   Source found in /root/vpp/src 
  Arch for platform 'vpp' is native   Finding source

[vpp-dev] VPP Plugins build errors from IPSec module

2020-02-25 Thread Majumdar, Kausik 
Hi folks,

I am trying to build VPP netlink and router plugins based on vpp branch v20.01 
to integrate and run with routing control plane FRR. I am following the 
guidelines based on 
https://github.com/FRRouting/frr/wiki/Alternate-forwarding-planes:-VPP

I am finding issues while trying to compile the IPSec plugin code, it is 
exiting with the below error. I have tried with latest VPP master branch, the 
result is pretty much same. Is there any resolution to this issue or am I 
missing something? If I try to use VPP v18.10 branch then I hit other netlink 
issue which I think discussed in this thread in the past. Hence moved to latest 
VPP code base, tried to link VPPSB and build the netlink-install and 
router-install plugins, hitting IPSec build failures. Any recommendation would 
be helpful.

I am running Centos 7.4 machine.

[root@localhost build-root]# git branch
* (detached from v20.01)
  master

[root@localhost build-root]# make V=0 PLATFORM=vpp TAG=vpp_debug 
netlink-install router-install
 Arch for platform 'vpp' is native 
 Finding source for external 
 Makefile fragment found in /root/vpp/build-data/packages/external.mk 
 Source found in /root/vpp/build 
 Arch for platform 'vpp' is native 
 Finding source for vpp 
 Makefile fragment found in /root/vpp/build-data/packages/vpp.mk 
 Source found in /root/vpp/src 
 Arch for platform 'vpp' is native 
 Finding source for netlink 
 Makefile fragment found in /root/vpp/build-data/packages/netlink.mk 
 Source found in /root/vpp/netlink 
 Configuring external: nothing to do 
 Building external: nothing to do 
 Installing external: nothing to do 
 Configuring vpp: nothing to do 
 Building vpp in /root/vpp/build-root/build-vpp_debug-native/vpp 
[1/660] Building C object 
plugins/crypto_ipsecmb/CMakeFiles/crypto_ipsecmb_plugin.dir/ipsecmb.c.o
FAILED: plugins/crypto_ipsecmb/CMakeFiles/crypto_ipsecmb_plugin.dir/ipsecmb.c.o
/opt/rh/devtoolset-7/root/bin/cc -Dcrypto_ipsecmb_plugin_EXPORTS 
-I/root/vpp/src -I. -Iinclude -I/root/vpp/src/plugins -Iplugins 
-I/opt/vpp/external/x86_64/include -Wno-address-of-packed-member -g -fPIC 
-Werror -Wall -march=corei7 -mtune=corei7-avx  -O0 -DCLIB_DEBUG 
-fstack-protector -DFORTIFY_SOURCE=2 -fno-common  -fPIC   -march=silvermont 
-maes -MD -MT 
plugins/crypto_ipsecmb/CMakeFiles/crypto_ipsecmb_plugin.dir/ipsecmb.c.o -MF 
plugins/crypto_ipsecmb/CMakeFiles/crypto_ipsecmb_plugin.dir/ipsecmb.c.o.d -o 
plugins/crypto_ipsecmb/CMakeFiles/crypto_ipsecmb_plugin.dir/ipsecmb.c.o   -c 
/root/vpp/src/plugins/crypto_ipsecmb/ipsecmb.c
/root/vpp/src/plugins/crypto_ipsecmb/ipsecmb.c:20:10: fatal error: 
intel-ipsec-mb.h: No such file or directory
 #include 
  ^~
compilation terminated.
[4/660] Building C object 
plugins/ct6/CMakeFiles/ct6_test_plugin.dir/ct6_test.c.o
ninja: build stopped: subcommand failed.
make: *** [vpp-build] Error 1
[root@localhost build-root]#

Thanks,
Kausik
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15532): https://lists.fd.io/g/vpp-dev/message/15532
Mute This Topic: https://lists.fd.io/mt/71543494/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Confirm your kausik.majum...@commscope.com email address

2020-02-24 Thread Majumdar, Kausik 

Hi,

I have subscribed to VPP dev mailing alias. Confirming my email address.

Thanks,
Kausik

From: FD.io 
Sent: Monday, February 24, 2020 10:19 AM
To: Majumdar, Kausik 
Subject: [vpp-dev] Confirm your kausik.majum...@commscope.com email address

Message received from external source. Exercise caution when opening 
attachments, clicking links, or exchanging information.


Hello,

Thank you for your interest in the 
https://lists.fd.io/g/vpp-dev<https://secure-web.cisco.com/1fNym-hmHGbOxtJRidnR_VU3lHPrLWkbVFWnNPuF-MKmJ41aCsXjMxMkcDwkBdVdhKAj1svb_ArO7XXFJuJ5uKMdyzBHJ4-WNnj41ic0a0Y5GD2WWMb224DopFUYdBELR3qS6p11zofKOc8vfTMCqb-P2Iuhahp6llYKnIVgdTbuQ6on-aUhNAL-rE1sOJn6BxgHj3OY-3E_5ee9JK5-kY_gCiwoX0Qusf1sCB1GB1D1lI2ylJaBZt-xly7pCaU4zTMn-Je3gPRzz_I_WF_S7UZ5j4wJy7KOLYHb72faXO2WqWUJADZUiTUkXa7_B_PR0Nr7CmSK4U2eF3i6kTl3Q2hAfMCv4uGnLfoo6JbdgQA0/https%3A%2F%2Flists.fd.io%2Fg%2Fvpp-dev>
 group at FD.io. If you did not request or do not want to join 
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>, please ignore this message.

If you only want to send and receive messages from 
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>, reply to this email to confirm 
your email address and activate your membership.

  *   Messages will be sent to you at 
kausik.majum...@commscope.com<mailto:kausik.majum...@commscope.com>
  *   Send messages to vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>

If you want to use the resources and read messages on the website, please click 
on the link below to confirm your email address, set up a password, and choose 
other subscription settings:

Confirm 
account<https://secure-web.cisco.com/1OgVEU_CnRNznFueRVUSEmkdjfr-6OM6GARTnZt8s1BUGSKYa7996ixdLNdlnTay8gE4ClRZXbjWRqWGcTs1nsQZxevjtgQ4Ft0KbBEqobg9jvFrRBhASD7s7dRB9NySzckc6o2Q7jVEJUjW-010WCCf6ofOtl0rw8dY2ir51ZtS1M6UXzGQ3GcNIksHyM0UNIFeYXZWiFURDC_SverappI3lC4qwvOheMwWyyKUKPpNjENWZbHoJrlIlYgC6l4u-VdKYRhm2xFnC3B3ZBW__urVlMV7FzfX4ICNUSeuq023SjdIC2Z_H5cXCWVnWRjDOyiGVwY0dEiZ089QaJS0ajRatrY080FlsQlExD--dukw/https%3A%2F%2Flists.fd.io%2Fconfirm%3Femail%3Dkausik.majumdar%2540commscope.com%26cookie%3D5237939063106927779>

Cheers,
The FD.io Team
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15510): https://lists.fd.io/g/vpp-dev/message/15510
Mute This Topic: https://lists.fd.io/mt/71517278/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-