[vpp-dev] Problem on VxLAN multicast mode

[Xuekun]

Hi, All

I'm configuring VPP as VxLAN multicast mode over multiple servers. To simplify 
the topology, I only used two servers: server1 as VPP; server2 using vxlan 
kernel mode.

Server1:
set interface state TenGigabitEthernet3d/0/1 up
set interface ip address TenGigabitEthernet3d/0/1 172.168.1.1/24
create bridge-domain 1000 learn 1 forward 1 uu-flood 1 flood 1 arp-term 0
create vxlan tunnel src 172.168.1.1 group 239.1.1.1 TenGigabitEthernet3d/0/1 
vni 100
set interface l2 bridge vxlan_tunnel0 1000  
loopback create 
set interface l2 bridge loop0 1000 bvi
set interface state loop0 up
set interface ip address loop0 192.168.1.1/24

Server2:
ifconfig enp11s0f1 172.168.1.2/24 up
ip link add vxlan0 type vxlan id 100 dstport 4789 group 239.1.1.1 dev enp11s0f1
ifconfig vxlan0 192.168.1.2/24 up

Now, server1 and server2 are connected with VxLAN VNI 100 through multicast 
group 239.1.1.1.  
However, 192.168.1.1 and 192.168.1.2 could NOT be pingable each other. 

Trace log: 
Packet 1

00:01:02:563831: dpdk-input
  TenGigabitEthernet3d/0/1 rx queue 0
  buffer 0x4b93: current data 14, length 78, free-list 0, clone-count 0, 
totlen-nifb 0, trace 0x0
 ext-hdr-valid
 l4-cksum-computed l4-cksum-correct l2-hdr-offset 0
  PKT MBUF: port 0, nb_segs 1, pkt_len 92
buf_len 2176, data_len 92, ol_flags 0x180, data_off 128, phys_addr 
0x4012e540
packet_type 0x291 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
rss 0x0 fdir.hi 0x0 fdir.lo 0x0
Packet Offload Flags
  PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid
  PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid
Packet Types
  RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
  RTE_PTYPE_L3_IPV4_EXT_UNKNOWN (0x0090) IPv4 packet with or without 
extension headers
  RTE_PTYPE_L4_UDP (0x0200) UDP packet
  IP4: 00:1e:67:34:31:6c -> 01:00:5e:01:01:01
  UDP: 172.168.1.2 -> 239.1.1.1
tos 0x00, ttl 1, length 78, checksum 0xe04b
fragment id 0x3ba7
  UDP: 54420 -> 4789
length 58, checksum 0x
00:01:02:563834: ip4-input-no-checksum
  UDP: 172.168.1.2 -> 239.1.1.1
tos 0x00, ttl 1, length 78, checksum 0xe04b
fragment id 0x3ba7
  UDP: 54420 -> 4789
length 58, checksum 0x
00:01:02:563839: ip4-mfib-forward-lookup
  fib 0 entry 6
00:01:02:563842: ip4-mfib-forward-rpf
  entry 6 itf 1 flags Accept,
00:01:02:563842: ip4-replicate
  replicate: 4 via [@1]: dpo-receive
00:01:02:563843: ip4-local
UDP: 172.168.1.2 -> 239.1.1.1
  tos 0x00, ttl 1, length 78, checksum 0xe04b
  fragment id 0x3ba7
UDP: 54420 -> 4789
  length 58, checksum 0x
00:01:02:563846: ip4-udp-lookup
  UDP: src-port 54420 dst-port 4789
00:01:02:563847: vxlan4-input
  VXLAN decap error - tunnel for vni 100 does not exist
00:01:02:563847: error-drop
  vxlan4-input: no such tunnel packets

Why it said "tunnel for vni 100 does not exist"? 
Any help is appreciated. 

Thx, Xuekun

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

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

Re: [E] [vpp-dev] VPPSB Netlink build failing

[Ni, Hongjun]

Hi Florin,

Netlink/router plugin is implemented as some graph nodes in the data plane,
It is better to use C FIB APIs to update FIB.

Thanks,
Hongjun

From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Florin Coras
Sent: Monday, November 5, 2018 11:06 AM
To: Ni, Hongjun 
Cc: Damjan Marion ; alp.ars...@xflowresearch.com; Kevin Yan 
; vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

Agreed with Damjan. Why not manage this as a separate project, just like 
Sweetcomb? Goal for Sandbox was to host plugins that could later convert into 
fully fledged projects.

Also, can’t netlink/router plugins use the binary APIs instead of, I would 
assume, raw C FIB APIs? That should simplify code maintenance.

Florin


On Nov 4, 2018, at 6:41 PM, Ni, Hongjun 
mailto:hongjun...@intel.com>> wrote:

Hi Damjan,

With some talks with customers, they want us to provide two options:
One option is what you mentioned here, routing daemon is integrated with VPP 
through binary APIs directly.
That is what we plan to do in Sweetcomb project.

Another option is to leverage legacy routing daemon without any change.
That is what vppsb netlink and router plugin have provided.
Since more than ten customers are using this feature,
and staying in vppsb makes it not sync with VPP code change in time.
So I suggest that we move it to VPP main repo.

Thanks,
Hongjun

From: Damjan Marion [mailto:dmar...@me.com]
Sent: Monday, November 5, 2018 1:32 AM
To: Ni, Hongjun mailto:hongjun...@intel.com>>
Cc: alp.ars...@xflowresearch.com; Kevin 
Yan mailto:kevin@mavenir.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing


Personally  i think it should stay in vppsb. I agree we miss integration with 
open source routing protocol implementation but it should be done natively 
trough binary APIs  and not with netlink hacks...

—
Damjan

On 4 Nov 2018, at 11:52, Ni, Hongjun 
mailto:hongjun...@intel.com>> wrote:
Hi Guys,

We are working on moving VPPSB Netlink to VPP main repo:
https://gerrit.fd.io/r/#/c/15062/ Port VPPSB's rtnetlink & router plugin to VPP 
main

This patch is under review and consolidating, but it could work well and you 
can use it.

Thanks,
Hongjun

From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of 
alp.ars...@xflowresearch.com
Sent: Friday, November 2, 2018 6:43 PM
To: 'Kevin Yan' mailto:kevin@mavenir.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

Using this command and running the application again, solved the issue,

# rm -rf /dev/shm/*

Thank you for the help.
From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of 
alp.ars...@xflowresearch.com
Sent: Friday, November 2, 2018 12:42 PM
To: 'Kevin Yan'; vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

No luck. Getting a seg fault. Will try to build again with stable/1810 instead 
of the master.

[root@vpp-build bin]# ./vpp -c startup.conf
vlib_plugin_early_init:361: plugin path 
/vpp/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins
load_one_plugin:189: Loaded plugin: abf_plugin.so (ACL based Forwarding)
load_one_plugin:189: Loaded plugin: acl_plugin.so (Access Control Lists)
load_one_plugin:189: Loaded plugin: avf_plugin.so (Intel Adaptive Virtual 
Function (AVF) Device Plugin)
load_one_plugin:191: Loaded plugin: cdp_plugin.so
load_one_plugin:189: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit 
(DPDK))
load_one_plugin:189: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
load_one_plugin:189: Loaded plugin: gbp_plugin.so (Group Based Policy)
load_one_plugin:189: Loaded plugin: gtpu_plugin.so (GTPv1-U)
load_one_plugin:189: Loaded plugin: igmp_plugin.so (IGMP messaging)
load_one_plugin:189: Loaded plugin: ila_plugin.so (Identifier-locator 
addressing for IPv6)
load_one_plugin:189: Loaded plugin: ioam_plugin.so (Inbound OAM)
load_one_plugin:117: Plugin disabled (default): ixge_plugin.so
load_one_plugin:189: Loaded plugin: l2e_plugin.so (L2 Emulation)
load_one_plugin:189: Loaded plugin: lacp_plugin.so (Link Aggregation Control 
Protocol)
load_one_plugin:189: Loaded plugin: lb_plugin.so (Load Balancer)
load_one_plugin:189: Loaded plugin: mactime_plugin.so (Time-based MAC 
source-address filter)
load_one_plugin:189: Loaded plugin: map_plugin.so (Mapping of address and port 
(MAP))
load_one_plugin:189: Loaded plugin: memif_plugin.so (Packet Memory Interface 
(experimental))
load_one_plugin:189: Loaded plugin: nat_plugin.so (Network Address Translation)
load_one_plugin:189: Loaded plugin: nsh_plugin.so (Network Service Header)
load_one_plugin:189: Loaded plugin: nsim_plugin.so (network delay simulator 
plugin)
load_one_plugin:189: Loaded plugin: perfmon_pl

Re: [vpp-dev] Where is the definition of IP_PROTOCOL_ICMP

[Ole Troan]

Hi there,

> Does someone know where is the definition of IP_PROTOCOL_ICMP? I searched 
> all the directories in VPP, but could not find it.

src/vnet/ip/protocols.def

Best regards,
Ole

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

View/Reply Online (#11093): https://lists.fd.io/g/vpp-dev/message/11093
Mute This Topic: https://lists.fd.io/mt/27855718/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] clearing stats

[David Cornejo]

On Sun, Nov 4, 2018 at 4:47 PM Ole Troan  wrote:
>
> David,
>
> > on a related note: do you intend that people will add to the
> > stat_directory_type_t with more complex specific types or keep it to
> > more primitive generic types?
>
> I was thinking of generic types, like if it is a counter, a counter vector, 
> or a gauge.
> And the user would have to know if it is a bytes counter, or a number of 
> buffers free counters etc.
>
> But I’m (very) open to better ways of presenting the data.
> Suggestions?
>
> Cheers,
> Ole
>
>
>
>
> > On Mon, Oct 22, 2018 at 10:20 AM Ole Troan  wrote:
> >>
> >> David,
> >>
> >>> in the new stats api, is there a way to clear counters or would that
> >>> be done using the existing messages? for example, clearing interface
> >>> stats with VL_API_SW_INTERFACE_CLEAR_STATS.
> >>
> >> There is nothing that clears all stats.
> >> The SW_INTERFACE_CLEAR_STATS will clear the interface stats.
> >>
> >> Guess we should at least add a clear for the node performance counters.
> >>
> >> Cheers,
> >> Ole
> >
> >
> >
> > --
> > Kailua, Hawaiʻi
> > US +1 (808) 728-3050
> > UK +44 (020) 3286 2808
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> >
> > View/Reply Online (#10966): https://lists.fd.io/g/vpp-dev/message/10966
> > Mute This Topic: https://lists.fd.io/mt/27525199/675193
> > Group Owner: vpp-dev+ow...@lists.fd.io
> > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [otr...@employees.org]
> > -=-=-=-=-=-=-=-=-=-=-=-
>

Ole,

I strongly concur with generic types - I'd like to see the combined
and simple counters removed once the old messages have been removed. I
think specific types would become a nightmare to maintain.

dave c



-- 
Kailua, Hawaiʻi
US +1 (808) 728-3050
UK +44 (020) 3286 2808
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[vpp-dev] Where is the definition of IP_PROTOCOL_ICMP

[saint_sun 孙 via Lists . Fd . Io]

Hello everyone,
    Does someone know where is the definition of IP_PROTOCOL_ICMP? I searched 
all the directories in VPP, but could not find it.

Appreciated for your help!

可用于iOS的myMail发送
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [E] [vpp-dev] VPPSB Netlink build failing

[Florin Coras]

Agreed with Damjan. Why not manage this as a separate project, just like 
Sweetcomb? Goal for Sandbox was to host plugins that could later convert into 
fully fledged projects. 

Also, can’t netlink/router plugins use the binary APIs instead of, I would 
assume, raw C FIB APIs? That should simplify code maintenance. 

Florin

> On Nov 4, 2018, at 6:41 PM, Ni, Hongjun  wrote:
> 
> Hi Damjan,
>  
> With some talks with customers, they want us to provide two options:
> One option is what you mentioned here, routing daemon is integrated with VPP 
> through binary APIs directly.
> That is what we plan to do in Sweetcomb project.
>  
> Another option is to leverage legacy routing daemon without any change.
> That is what vppsb netlink and router plugin have provided.
> Since more than ten customers are using this feature,
> and staying in vppsb makes it not sync with VPP code change in time.
> So I suggest that we move it to VPP main repo.
>  
> Thanks,
> Hongjun
>   <>
>  <>From: Damjan Marion [mailto:dmar...@me.com ] 
> Sent: Monday, November 5, 2018 1:32 AM
> To: Ni, Hongjun mailto:hongjun...@intel.com>>
> Cc: alp.ars...@xflowresearch.com ; Kevin 
> Yan mailto:kevin@mavenir.com>>; 
> vpp-dev@lists.fd.io 
> Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing
>  
>  
> Personally  i think it should stay in vppsb. I agree we miss integration with 
> open source routing protocol implementation but it should be done natively 
> trough binary APIs  and not with netlink hacks...
>  
> 
> — 
> Damjan
> 
> On 4 Nov 2018, at 11:52, Ni, Hongjun  > wrote:
> 
> Hi Guys,
>  
> We are working on moving VPPSB Netlink to VPP main repo:
> https://gerrit.fd.io/r/#/c/15062/  Port 
> VPPSB's rtnetlink & router plugin to VPP main
>  
> This patch is under review and consolidating, but it could work well and you 
> can use it.
>  
> Thanks,
> Hongjun
>  
> From: vpp-dev@lists.fd.io  
> [mailto:vpp-dev@lists.fd.io ] On Behalf Of 
> alp.ars...@xflowresearch.com 
> Sent: Friday, November 2, 2018 6:43 PM
> To: 'Kevin Yan' mailto:kevin@mavenir.com>>; 
> vpp-dev@lists.fd.io 
> Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing
>  
> Using this command and running the application again, solved the issue,
>  
> # rm -rf /dev/shm/*
>  
> Thank you for the help. 
> From: vpp-dev@lists.fd.io  
> [mailto:vpp-dev@lists.fd.io ] On Behalf Of 
> alp.ars...@xflowresearch.com 
> Sent: Friday, November 2, 2018 12:42 PM
> To: 'Kevin Yan'; vpp-dev@lists.fd.io 
> Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing
>  
> No luck. Getting a seg fault. Will try to build again with stable/1810 
> instead of the master.
>  
> [root@vpp-build bin]# ./vpp -c startup.conf
> vlib_plugin_early_init:361: plugin path 
> /vpp/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins
> load_one_plugin:189: Loaded plugin: abf_plugin.so (ACL based Forwarding)
> load_one_plugin:189: Loaded plugin: acl_plugin.so (Access Control Lists)
> load_one_plugin:189: Loaded plugin: avf_plugin.so (Intel Adaptive Virtual 
> Function (AVF) Device Plugin)
> load_one_plugin:191: Loaded plugin: cdp_plugin.so
> load_one_plugin:189: Loaded plugin: dpdk_plugin.so (Data Plane Development 
> Kit (DPDK))
> load_one_plugin:189: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
> load_one_plugin:189: Loaded plugin: gbp_plugin.so (Group Based Policy)
> load_one_plugin:189: Loaded plugin: gtpu_plugin.so (GTPv1-U)
> load_one_plugin:189: Loaded plugin: igmp_plugin.so (IGMP messaging)
> load_one_plugin:189: Loaded plugin: ila_plugin.so (Identifier-locator 
> addressing for IPv6)
> load_one_plugin:189: Loaded plugin: ioam_plugin.so (Inbound OAM)
> load_one_plugin:117: Plugin disabled (default): ixge_plugin.so
> load_one_plugin:189: Loaded plugin: l2e_plugin.so (L2 Emulation)
> load_one_plugin:189: Loaded plugin: lacp_plugin.so (Link Aggregation Control 
> Protocol)
> load_one_plugin:189: Loaded plugin: lb_plugin.so (Load Balancer)
> load_one_plugin:189: Loaded plugin: mactime_plugin.so (Time-based MAC 
> source-address filter)
> load_one_plugin:189: Loaded plugin: map_plugin.so (Mapping of address and 
> port (MAP))
> load_one_plugin:189: Loaded plugin: memif_plugin.so (Packet Memory Interface 
> (experimental))
> load_one_plugin:189: Loaded plugin: nat_plugin.so (Network Address 
> Translation)
> load_one_plugin:189: Loaded plugin: nsh_plugin.so (Network Service Header)
> load_one_plugin:189: Loaded plugin: nsim_plugin.so (network delay simulator 
> plugin)
> load_one_plugin:189: Loaded plugin: perfmon_plugin.so (Performance monitor 
> plugin)
> load_one_plugin:189: Loaded plugin: pppoe_plugin.

Re: [vpp-dev] clearing stats

[Ole Troan]

David,

> on a related note: do you intend that people will add to the
> stat_directory_type_t with more complex specific types or keep it to
> more primitive generic types?

I was thinking of generic types, like if it is a counter, a counter vector, or 
a gauge.
And the user would have to know if it is a bytes counter, or a number of 
buffers free counters etc.

But I’m (very) open to better ways of presenting the data.
Suggestions?

Cheers,
Ole




> On Mon, Oct 22, 2018 at 10:20 AM Ole Troan  wrote:
>> 
>> David,
>> 
>>> in the new stats api, is there a way to clear counters or would that
>>> be done using the existing messages? for example, clearing interface
>>> stats with VL_API_SW_INTERFACE_CLEAR_STATS.
>> 
>> There is nothing that clears all stats.
>> The SW_INTERFACE_CLEAR_STATS will clear the interface stats.
>> 
>> Guess we should at least add a clear for the node performance counters.
>> 
>> Cheers,
>> Ole
> 
> 
> 
> -- 
> Kailua, Hawaiʻi
> US +1 (808) 728-3050
> UK +44 (020) 3286 2808
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#10966): https://lists.fd.io/g/vpp-dev/message/10966
> Mute This Topic: https://lists.fd.io/mt/27525199/675193
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [otr...@employees.org]
> -=-=-=-=-=-=-=-=-=-=-=-

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

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

Re: [E] [vpp-dev] VPPSB Netlink build failing

[Ni, Hongjun]

Hi Damjan,

With some talks with customers, they want us to provide two options:
One option is what you mentioned here, routing daemon is integrated with VPP 
through binary APIs directly.
That is what we plan to do in Sweetcomb project.

Another option is to leverage legacy routing daemon without any change.
That is what vppsb netlink and router plugin have provided.
Since more than ten customers are using this feature,
and staying in vppsb makes it not sync with VPP code change in time.
So I suggest that we move it to VPP main repo.

Thanks,
Hongjun

From: Damjan Marion [mailto:dmar...@me.com]
Sent: Monday, November 5, 2018 1:32 AM
To: Ni, Hongjun 
Cc: alp.ars...@xflowresearch.com; Kevin Yan ; 
vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing


Personally  i think it should stay in vppsb. I agree we miss integration with 
open source routing protocol implementation but it should be done natively 
trough binary APIs  and not with netlink hacks...

—
Damjan

On 4 Nov 2018, at 11:52, Ni, Hongjun 
mailto:hongjun...@intel.com>> wrote:
Hi Guys,

We are working on moving VPPSB Netlink to VPP main repo:
https://gerrit.fd.io/r/#/c/15062/ Port VPPSB's rtnetlink & router plugin to VPP 
main

This patch is under review and consolidating, but it could work well and you 
can use it.

Thanks,
Hongjun

From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of 
alp.ars...@xflowresearch.com
Sent: Friday, November 2, 2018 6:43 PM
To: 'Kevin Yan' mailto:kevin@mavenir.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

Using this command and running the application again, solved the issue,

# rm -rf /dev/shm/*

Thank you for the help.
From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of 
alp.ars...@xflowresearch.com
Sent: Friday, November 2, 2018 12:42 PM
To: 'Kevin Yan'; vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

No luck. Getting a seg fault. Will try to build again with stable/1810 instead 
of the master.

[root@vpp-build bin]# ./vpp -c startup.conf
vlib_plugin_early_init:361: plugin path 
/vpp/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins
load_one_plugin:189: Loaded plugin: abf_plugin.so (ACL based Forwarding)
load_one_plugin:189: Loaded plugin: acl_plugin.so (Access Control Lists)
load_one_plugin:189: Loaded plugin: avf_plugin.so (Intel Adaptive Virtual 
Function (AVF) Device Plugin)
load_one_plugin:191: Loaded plugin: cdp_plugin.so
load_one_plugin:189: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit 
(DPDK))
load_one_plugin:189: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
load_one_plugin:189: Loaded plugin: gbp_plugin.so (Group Based Policy)
load_one_plugin:189: Loaded plugin: gtpu_plugin.so (GTPv1-U)
load_one_plugin:189: Loaded plugin: igmp_plugin.so (IGMP messaging)
load_one_plugin:189: Loaded plugin: ila_plugin.so (Identifier-locator 
addressing for IPv6)
load_one_plugin:189: Loaded plugin: ioam_plugin.so (Inbound OAM)
load_one_plugin:117: Plugin disabled (default): ixge_plugin.so
load_one_plugin:189: Loaded plugin: l2e_plugin.so (L2 Emulation)
load_one_plugin:189: Loaded plugin: lacp_plugin.so (Link Aggregation Control 
Protocol)
load_one_plugin:189: Loaded plugin: lb_plugin.so (Load Balancer)
load_one_plugin:189: Loaded plugin: mactime_plugin.so (Time-based MAC 
source-address filter)
load_one_plugin:189: Loaded plugin: map_plugin.so (Mapping of address and port 
(MAP))
load_one_plugin:189: Loaded plugin: memif_plugin.so (Packet Memory Interface 
(experimental))
load_one_plugin:189: Loaded plugin: nat_plugin.so (Network Address Translation)
load_one_plugin:189: Loaded plugin: nsh_plugin.so (Network Service Header)
load_one_plugin:189: Loaded plugin: nsim_plugin.so (network delay simulator 
plugin)
load_one_plugin:189: Loaded plugin: perfmon_plugin.so (Performance monitor 
plugin)
load_one_plugin:189: Loaded plugin: pppoe_plugin.so (PPPoE)
load_one_plugin:189: Loaded plugin: router.so (router)
load_one_plugin:189: Loaded plugin: srv6ad_plugin.so (Dynamic SRv6 proxy)
load_one_plugin:189: Loaded plugin: srv6am_plugin.so (Masquerading SRv6 proxy)
load_one_plugin:189: Loaded plugin: srv6as_plugin.so (Static SRv6 proxy)
load_one_plugin:189: Loaded plugin: stn_plugin.so (VPP Steals the NIC for 
Container integration)
load_one_plugin:189: Loaded plugin: svs_plugin.so (Source VRF Select)
load_one_plugin:189: Loaded plugin: tlsopenssl_plugin.so (openssl based TLS 
Engine)
load_one_plugin:117: Plugin disabled (default): unittest_plugin.so
load_one_plugin:189: Loaded plugin: vmxnet3_plugin.so (VMWare Vmxnet3 Device 
Plugin)
./vpp[15923]: svm_map_region:766: region /global_vm mutex held by dead pid 
15806, tag 2, force unlock
./vpp[15923]: svm_map_region:774: recovery: attempt to re-lock region
Se

Re: [E] [vpp-dev] VPPSB Netlink build failing

[Damjan Marion via Lists.Fd.Io]

Personally  i think it should stay in vppsb. I agree we miss integration with 
open source routing protocol implementation but it should be done natively 
trough binary APIs  and not with netlink hacks...


— 
Damjan

> On 4 Nov 2018, at 11:52, Ni, Hongjun  wrote:
> 
> Hi Guys,
>  
> We are working on moving VPPSB Netlink to VPP main repo:
> https://gerrit.fd.io/r/#/c/15062/ Port VPPSB's rtnetlink & router plugin to 
> VPP main
>  
> This patch is under review and consolidating, but it could work well and you 
> can use it.
>  
> Thanks,
> Hongjun
>  
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of 
> alp.ars...@xflowresearch.com
> Sent: Friday, November 2, 2018 6:43 PM
> To: 'Kevin Yan' ; vpp-dev@lists.fd.io
> Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing
>  
> Using this command and running the application again, solved the issue,
>  
> # rm -rf /dev/shm/*
>  
> Thank you for the help.
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of 
> alp.ars...@xflowresearch.com
> Sent: Friday, November 2, 2018 12:42 PM
> To: 'Kevin Yan'; vpp-dev@lists.fd.io
> Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing
>  
> No luck. Getting a seg fault. Will try to build again with stable/1810 
> instead of the master.
>  
> [root@vpp-build bin]# ./vpp -c startup.conf
> vlib_plugin_early_init:361: plugin path 
> /vpp/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins
> load_one_plugin:189: Loaded plugin: abf_plugin.so (ACL based Forwarding)
> load_one_plugin:189: Loaded plugin: acl_plugin.so (Access Control Lists)
> load_one_plugin:189: Loaded plugin: avf_plugin.so (Intel Adaptive Virtual 
> Function (AVF) Device Plugin)
> load_one_plugin:191: Loaded plugin: cdp_plugin.so
> load_one_plugin:189: Loaded plugin: dpdk_plugin.so (Data Plane Development 
> Kit (DPDK))
> load_one_plugin:189: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
> load_one_plugin:189: Loaded plugin: gbp_plugin.so (Group Based Policy)
> load_one_plugin:189: Loaded plugin: gtpu_plugin.so (GTPv1-U)
> load_one_plugin:189: Loaded plugin: igmp_plugin.so (IGMP messaging)
> load_one_plugin:189: Loaded plugin: ila_plugin.so (Identifier-locator 
> addressing for IPv6)
> load_one_plugin:189: Loaded plugin: ioam_plugin.so (Inbound OAM)
> load_one_plugin:117: Plugin disabled (default): ixge_plugin.so
> load_one_plugin:189: Loaded plugin: l2e_plugin.so (L2 Emulation)
> load_one_plugin:189: Loaded plugin: lacp_plugin.so (Link Aggregation Control 
> Protocol)
> load_one_plugin:189: Loaded plugin: lb_plugin.so (Load Balancer)
> load_one_plugin:189: Loaded plugin: mactime_plugin.so (Time-based MAC 
> source-address filter)
> load_one_plugin:189: Loaded plugin: map_plugin.so (Mapping of address and 
> port (MAP))
> load_one_plugin:189: Loaded plugin: memif_plugin.so (Packet Memory Interface 
> (experimental))
> load_one_plugin:189: Loaded plugin: nat_plugin.so (Network Address 
> Translation)
> load_one_plugin:189: Loaded plugin: nsh_plugin.so (Network Service Header)
> load_one_plugin:189: Loaded plugin: nsim_plugin.so (network delay simulator 
> plugin)
> load_one_plugin:189: Loaded plugin: perfmon_plugin.so (Performance monitor 
> plugin)
> load_one_plugin:189: Loaded plugin: pppoe_plugin.so (PPPoE)
> load_one_plugin:189: Loaded plugin: router.so (router)
> load_one_plugin:189: Loaded plugin: srv6ad_plugin.so (Dynamic SRv6 proxy)
> load_one_plugin:189: Loaded plugin: srv6am_plugin.so (Masquerading SRv6 proxy)
> load_one_plugin:189: Loaded plugin: srv6as_plugin.so (Static SRv6 proxy)
> load_one_plugin:189: Loaded plugin: stn_plugin.so (VPP Steals the NIC for 
> Container integration)
> load_one_plugin:189: Loaded plugin: svs_plugin.so (Source VRF Select)
> load_one_plugin:189: Loaded plugin: tlsopenssl_plugin.so (openssl based TLS 
> Engine)
> load_one_plugin:117: Plugin disabled (default): unittest_plugin.so
> load_one_plugin:189: Loaded plugin: vmxnet3_plugin.so (VMWare Vmxnet3 Device 
> Plugin)
> ./vpp[15923]: svm_map_region:766: region /global_vm mutex held by dead pid 
> 15806, tag 2, force unlock
> ./vpp[15923]: svm_map_region:774: recovery: attempt to re-lock region
> Segmentation fault
>  
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Kevin Yan
> Sent: Friday, November 2, 2018 12:28 PM
> To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
> Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing
>  
> I think rpm packages can be generated but I never tried that,  just use “make 
> run ” or “vpp -c /etc/vpp/startup.conf” to start vpp,  the additional thing 
> you should do is just copy router.so to the default plugin location.
>  
> From: alp.ars...@xflowresearch.com [mailto:alp.ars...@xflowresearch.com] 
> Sent: Friday, November 02, 2018 3:17 PM
> To: Kevin Yan ; vpp-dev@lists.fd.io
> Subject: RE: [E] [vpp-dev] VPPSB Netlink build failing
>  
> Yes, did that and its compiling. Thanks.
>  
> One question, after the build is completed, how do I install it to my system? 
> I ca

Re: [E] [vpp-dev] VPPSB Netlink build failing

[Ni, Hongjun]

Hi Guys,

We are working on moving VPPSB Netlink to VPP main repo:
https://gerrit.fd.io/r/#/c/15062/ Port VPPSB's rtnetlink & router plugin to VPP 
main

This patch is under review and consolidating, but it could work well and you 
can use it.

Thanks,
Hongjun

From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of 
alp.ars...@xflowresearch.com
Sent: Friday, November 2, 2018 6:43 PM
To: 'Kevin Yan' ; vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

Using this command and running the application again, solved the issue,

# rm -rf /dev/shm/*

Thank you for the help.
From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of 
alp.ars...@xflowresearch.com
Sent: Friday, November 2, 2018 12:42 PM
To: 'Kevin Yan'; vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

No luck. Getting a seg fault. Will try to build again with stable/1810 instead 
of the master.

[root@vpp-build bin]# ./vpp -c startup.conf
vlib_plugin_early_init:361: plugin path 
/vpp/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins
load_one_plugin:189: Loaded plugin: abf_plugin.so (ACL based Forwarding)
load_one_plugin:189: Loaded plugin: acl_plugin.so (Access Control Lists)
load_one_plugin:189: Loaded plugin: avf_plugin.so (Intel Adaptive Virtual 
Function (AVF) Device Plugin)
load_one_plugin:191: Loaded plugin: cdp_plugin.so
load_one_plugin:189: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit 
(DPDK))
load_one_plugin:189: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
load_one_plugin:189: Loaded plugin: gbp_plugin.so (Group Based Policy)
load_one_plugin:189: Loaded plugin: gtpu_plugin.so (GTPv1-U)
load_one_plugin:189: Loaded plugin: igmp_plugin.so (IGMP messaging)
load_one_plugin:189: Loaded plugin: ila_plugin.so (Identifier-locator 
addressing for IPv6)
load_one_plugin:189: Loaded plugin: ioam_plugin.so (Inbound OAM)
load_one_plugin:117: Plugin disabled (default): ixge_plugin.so
load_one_plugin:189: Loaded plugin: l2e_plugin.so (L2 Emulation)
load_one_plugin:189: Loaded plugin: lacp_plugin.so (Link Aggregation Control 
Protocol)
load_one_plugin:189: Loaded plugin: lb_plugin.so (Load Balancer)
load_one_plugin:189: Loaded plugin: mactime_plugin.so (Time-based MAC 
source-address filter)
load_one_plugin:189: Loaded plugin: map_plugin.so (Mapping of address and port 
(MAP))
load_one_plugin:189: Loaded plugin: memif_plugin.so (Packet Memory Interface 
(experimental))
load_one_plugin:189: Loaded plugin: nat_plugin.so (Network Address Translation)
load_one_plugin:189: Loaded plugin: nsh_plugin.so (Network Service Header)
load_one_plugin:189: Loaded plugin: nsim_plugin.so (network delay simulator 
plugin)
load_one_plugin:189: Loaded plugin: perfmon_plugin.so (Performance monitor 
plugin)
load_one_plugin:189: Loaded plugin: pppoe_plugin.so (PPPoE)
load_one_plugin:189: Loaded plugin: router.so (router)
load_one_plugin:189: Loaded plugin: srv6ad_plugin.so (Dynamic SRv6 proxy)
load_one_plugin:189: Loaded plugin: srv6am_plugin.so (Masquerading SRv6 proxy)
load_one_plugin:189: Loaded plugin: srv6as_plugin.so (Static SRv6 proxy)
load_one_plugin:189: Loaded plugin: stn_plugin.so (VPP Steals the NIC for 
Container integration)
load_one_plugin:189: Loaded plugin: svs_plugin.so (Source VRF Select)
load_one_plugin:189: Loaded plugin: tlsopenssl_plugin.so (openssl based TLS 
Engine)
load_one_plugin:117: Plugin disabled (default): unittest_plugin.so
load_one_plugin:189: Loaded plugin: vmxnet3_plugin.so (VMWare Vmxnet3 Device 
Plugin)
./vpp[15923]: svm_map_region:766: region /global_vm mutex held by dead pid 
15806, tag 2, force unlock
./vpp[15923]: svm_map_region:774: recovery: attempt to re-lock region
Segmentation fault

From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of Kevin Yan
Sent: Friday, November 2, 2018 12:28 PM
To: alp.ars...@xflowresearch.com; 
vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

I think rpm packages can be generated but I never tried that,  just use "make 
run " or "vpp -c /etc/vpp/startup.conf" to start vpp,  the additional thing you 
should do is just copy router.so to the default plugin location.

From: alp.ars...@xflowresearch.com 
[mailto:alp.ars...@xflowresearch.com]
Sent: Friday, November 02, 2018 3:17 PM
To: Kevin Yan mailto:kevin@mavenir.com>>; 
vpp-dev@lists.fd.io
Subject: RE: [E] [vpp-dev] VPPSB Netlink build failing

Yes, did that and its compiling. Thanks.

One question, after the build is completed, how do I install it to my system? I 
can see the install directory with all the binaries, but how do I get them to 
proper locations, like I would if I installed using the rpms.


From: vpp-dev@lists.fd.io 
[mailto:v