date:20181102

Re: [vpp-dev] Regarding vlib_buffer_alloc

2018-11-02 Thread Prashant Upadhyaya

Thanks Dave, the link is very useful !

On Sat, Nov 3, 2018 at 2:20 AM Dave Barach (dbarach)  wrote:
>
> See also 
> https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/developers/vnet.html#creating-packets-from-scratch
>
> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of Prashant 
> Upadhyaya
> Sent: Friday, November 2, 2018 12:54 PM
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] Regarding vlib_buffer_alloc
>
> Hi,
>
> When I allocate a buffer using the vlib_buffer_alloc, are the fields in the 
> vlib_buffer_t guaranteed to be properly initialized (eg. with all zero 
> values) or is there any obligation on the caller to initialize these because 
> the values may be unpredictable ?
>
> Regards
> -Prashant
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11081): https://lists.fd.io/g/vpp-dev/message/11081
Mute This Topic: https://lists.fd.io/mt/27829857/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] Regarding vlib_buffer_alloc

2018-11-02 Thread Dave Barach via Lists.Fd.Io

See also 
https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/developers/vnet.html#creating-packets-from-scratch
 

-Original Message-
From: vpp-dev@lists.fd.io  On Behalf Of Prashant Upadhyaya
Sent: Friday, November 2, 2018 12:54 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Regarding vlib_buffer_alloc

Hi,

When I allocate a buffer using the vlib_buffer_alloc, are the fields in the 
vlib_buffer_t guaranteed to be properly initialized (eg. with all zero values) 
or is there any obligation on the caller to initialize these because the values 
may be unpredictable ?

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

View/Reply Online (#11080): https://lists.fd.io/g/vpp-dev/message/11080
Mute This Topic: https://lists.fd.io/mt/27829857/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] auto-abandon

2018-11-02 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io

> difficult to find

I decided to test that, on a change
that is actually abandoned (because 9336 is not, yet).

This [0] simple search link finds two changes,
one [1] of them is abandoned.

Vratko.

[0] https://gerrit.fd.io/r/#/q/%22igmp+proxy%22
[1] https://gerrit.fd.io/r/12561

From: vpp-dev@lists.fd.io  On Behalf Of Jim Thompson
Sent: Wednesday, 2018-October-31 19:00
To: Damjan Marion 
Cc: vpp-dev 
Subject: Re: [vpp-dev] auto-abandon


It would seem to make it difficult to find a half-implemented feature.  “Has 
anyone tried this before?”

Case in-point: L3SPAN (#9336), which seems abandoned, but is of interest.

Jim


On Oct 26, 2018, at 3:01 PM, Damjan Marion via Lists.Fd.Io 
mailto:dmarion=me@lists.fd.io>> wrote:


Folks,

Gerrit have this nice feature and our list of open changes is growing:

https://gerrit-review.googlesource.com/Documentation/user-change-cleanup.html

Should we enable that? IMO everything without activity in last 3 months should 
be abandoned.

Thoughts?

--
Damjan

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

View/Reply Online (#11004): https://lists.fd.io/g/vpp-dev/message/11004
Mute This Topic: https://lists.fd.io/mt/27743376/675164
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[j...@netgate.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

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

[vpp-dev] Regarding vlib_buffer_alloc

2018-11-02 Thread Prashant Upadhyaya

Hi,

When I allocate a buffer using the vlib_buffer_alloc, are the fields
in the vlib_buffer_t guaranteed to be properly initialized (eg. with
all zero values) or is there any obligation on the caller to
initialize these because the values may be unpredictable ?

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

View/Reply Online (#11078): https://lists.fd.io/g/vpp-dev/message/11078
Mute This Topic: https://lists.fd.io/mt/27829857/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] PPPoE plugin documentation/support

2018-11-02 Thread alp . arslan

Hello, 

I want to use the latest VPP, instead of 17.10. The latest ( 18.10 ) version
pppoe plugin is not working correctly. 

The PADI packets are successfully sent to the cp interface, but it is not
creating and pppoe fib, due to which the PADO packets are being dropped.

Packet 1

02:34:23:456994: virtio-input
  virtio: hw_if_index 3 next-index 4 vring 0 len 63
hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0
csum_offset 0 num_buffers 1
02:34:23:457015: ethernet-input
  PPPOE_DISCOVERY: e6:b1:bd:65:91:c1 -> 52:54:00:79:64:b9
02:34:23:457031: error-drop
  ethernet-input: l3 mac mismatch

vpp# show pppoe fib
no pppoe fib entries

Is this behavior intentional? Do I need to configure anything else other
than the cp interface?  

-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Wednesday, October 24, 2018 2:51 PM
To: 'Ni, Hongjun'; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support

Its working fine with VPP 17.10. I can see that a pppoe fib is created as
soon as the 1st PADI request arrives, which sets up the reverse path.
However, in VPP 18.07 & 18.10 there is no fib entry created and the PADO
packets are being dropped. 

The slides don't show a trace for the PADO replies. 

-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni,
Hongjun
Sent: Wednesday, October 24, 2018 1:38 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support

Hi Alp Arslan,

Please see below slides for more details. There is some packet trace for
your reference.

https://schd.ws/hosted_files/onsna18/cf/Accelerated%20Open%20Source%20vBRAS%
20Solution%20Based%20on%20OpenBRAS%20and%20VPP%26DPDK.PPTX

Thanks,
Hongjun

-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Wednesday, October 24, 2018 2:49 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support

Dell - Internal Use - Confidential  

Dear Hongjun, 

I was able to correctly set up the cp interface, my mistake as I was giving
the wrong interface index. 
Now the PADI packets are passed to cp interface. 

I started a pppoe-server on the Linux side (tap0) interface, but VPP is
dropping the PADO packets. 
Adding a trace on the virtio-input shows this: 

00:04:07:498195: virtio-input
  virtio: hw_if_index 2 next-index 4 vring 0 len 71
hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0
csum_offset 0 num_buffers 1
00:04:07:498204: ethernet-input
  PPPOE_DISCOVERY: f6:a0:85:84:98:e6 -> 3c:fd:fe:25:e6:20
00:04:07:498209: error-drop
  ethernet-input: l3 mac mismatch

The destination MAC address belongs to the pppoe-client, that's connected to
the 10G interface. However, VPP doesn't seem to know where to forward the
PADO replies. 
Also there are no entries in the pppoe fib for this client. Can you please
help me with this one? Please let me know if you need any more information. 

Regards,
Alp Arslan


-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni,
Hongjun
Sent: Tuesday, October 23, 2018 1:07 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support

Hi Alp Arslan,

To make tap_cli work, you need to revert the code as per this patch:
https://gerrit.fd.io/r/#/c/9467/ 

Thanks,
Hongjun

-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 4:01 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support

Dell - Internal Use - Confidential  

Dear Hongjun, 

Thanks for the reply. 

I am using the VPP version 18.07. If the tap_cli is still present, can you
please point me towards what could be the problem with the existing plugin. 
I would like to see this one working a little bit, before starting to look
into tapv2.

Regards,
Alp Arslan

-Original Message-
From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, October 23, 2018 12:51 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] PPPoE plugin documentation/support

Hi Alp Arslan,

Since tap_cli code is going to be deprecated in favour of tapv2.
I suggest you leverage tapv2, and also need some rework for PPPoE plugin.

Thanks,
Hongjun

-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 3:08 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] PPPoE plugin documentation/support

Dear All, 

I am trying to evaluate the support of pppoe in vpp. However, I am facing
some issues, here is my startup conf file. 

unix {
  nodaemon
  log /var/log/vpp/vpp.log
  full-coredump
  cli-listen

Re: [vpp-dev] Incrementing node counters

2018-11-02 Thread Dave Barach via Lists.Fd.Io

Yes, you missed something. This pattern is used in inline functions called with 
compile-time constant values for is_ip6:

always_inline uword
ah_encrypt_inline (vlib_main_t * vm,
  vlib_node_runtime_t * node, vlib_frame_t * from_frame,
  int is_ip6)


VLIB_NODE_FN (ah4_encrypt_node) (vlib_main_t * vm,
 vlib_node_runtime_t * node,
 vlib_frame_t * from_frame)
{
  return ah_encrypt_inline (vm, node, from_frame, 0 /* is_ip6 */ );
}



VLIB_NODE_FN (ah6_encrypt_node) (vlib_main_t * vm,
 vlib_node_runtime_t * node,
 vlib_frame_t * from_frame)
{
  return ah_encrypt_inline (vm, node, from_frame, 1 /* is_ip6 */ );
}

The compiler discards either the “if” clause or the “else” clause, and 
(certainly) never tests is_ip6 at runtime. It might be marginally worth 
s/xxx_node.index/node->node_index/.

Another instance of this game may make sense in performance-critical nodes. 
Here, we remove packet-tracer code:

always_inline uword
nsim_inline (vlib_main_t * vm,
  vlib_node_runtime_t * node, vlib_frame_t * frame, int is_trace)
{
  
  if (is_trace)
 {
   if (b[0]->flags & VLIB_BUFFER_IS_TRACED)
 {
   nsim_trace_t *t = vlib_add_trace (vm, node, b[0], sizeof (*t));
   t->expires = expires;
   t->is_drop = is_drop0;
   t->tx_sw_if_index = (is_drop0 == 0) ? ep->tx_sw_if_index : 0;
 }
 }
  
}

VLIB_NODE_FN (nsim_node) (vlib_main_t * vm, vlib_node_runtime_t * node,
  vlib_frame_t * frame)
{
  if (PREDICT_FALSE (node->flags & VLIB_NODE_FLAG_TRACE))
return nsim_inline (vm, node, frame, 1 /* is_trace */ );
  else
return nsim_inline (vm, node, frame, 0 /* is_trace */ );
}

From: vpp-dev@lists.fd.io  On Behalf Of Kingwel Xie
Sent: Thursday, November 1, 2018 8:43 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Incrementing node counters

Hi vPPers,

I’m looking at the latest changes in IPSEC, and I notice ip4 and ip6 nodes are 
separated. So there are a lot of code in the node function like this:

  if (is_ip6)
vlib_node_increment_counter (vm, esp6_decrypt_node.index,

ESP_DECRYPT_ERROR_RX_PKTS,

from_frame->n_vectors);
  else
vlib_node_increment_counter (vm, esp4_decrypt_node.index,

ESP_DECRYPT_ERROR_RX_PKTS,

from_frame->n_vectors);


I’m wondering why not like this:

vlib_node_increment_counter (vm, node->node_index,

ESP_DECRYPT_ERROR_RX_PKTS,

from_frame->n_vectors);

My understanding is that node functions are always dispatched with the correct 
node instances. Or do I miss something? BTW, nt just ipsec, quite some other 
nodes are written as the former.

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

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

2018-11-02 Thread alp . arslan

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:vpp-dev@lists.fd.io] On Behalf Of Kevin Yan
Sent: Friday, November 2, 2018 12:16 PM
To: alp.ars...@xflowresearch.com  ;
vpp-dev@lists.fd.io  
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

 

And also remove 
else if (r->rtm.rtm_family == AF_MPLS)

part

 

From: Kevin Yan 
Sent: Friday, November 02, 2018 3:15 PM
To: 'alp.ars...@xflowresearch.com' mailto:alp.ars...@xflowresearch.com> >; vpp-dev@lists.fd.io
 
Subject: RE:

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

2018-11-02 Thread alp . arslan

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:vpp-dev@lists.fd.io] On Behalf Of Kevin Yan
Sent: Friday, November 2, 2018 12:16 PM
To: alp.ars...@xflowresearch.com  ;
vpp-dev@lists.fd.io  
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

 

And also remove 
else if (r->rtm.rtm_family == AF_MPLS)

part

 

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

 

for(int i = 1; label != 0; i++)

change to :
int I;
for(i = 1; label != 0; i++)

 

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

 

Tried removing both

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

2018-11-02 Thread Kevin Yan

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 
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:vpp-dev@lists.fd.io] On Behalf Of Kevin Yan
Sent: Friday, November 2, 2018 12:16 PM
To: alp.ars...@xflowresearch.com; 
vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

And also remove
else if (r->rtm.rtm_family == AF_MPLS)
part

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

for(int i = 1; label != 0; i++)

change to :
int I;
for(i = 1; label != 0; i++)

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

Tried removing both macros (RTNLGRP_MPLS_ROUTE & RTA_VIA), failed with another 
MPLS related error in the router plugin.

make[1]: Entering directory `/vpp/build-root/build-vpp_debug-native/router'
  CC   router/tap_inject_netlink.lo
/vpp/build-data/../router/router/tap_inject_netlink.c: In function 
'get_mpls_label_stack':
/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: error: 'for' loop 
initial declarations are only allowed in C99 mode
   for(int i = 1; label != 0; i++) {
   ^
/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: note: use option 
-std=c99 or -std=gnu99 to compile your code
/vpp/build-data/../router/router/tap_inject_netlink.c: In function 
'add_del_route':
/vpp/build-data/../router/router/tap_inject_netlink.c:200:9: error: 'for' loop 
initial declarations are only allowed in C99 mode
 for(int i = 0; i < MPLS_STACK_DEPTH && stack[i] != 0; i++) {
 ^
/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: error: 'AF_MPLS' 
undeclared (first use in this function)
   else if (r->rtm.rtm_family == AF_MPLS)
 ^
/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: note: each 
undeclared identifier is reported only once for each function it appears in
In file included from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/mem.h:55:0,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/vec.h:42,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/format.h:44,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf.h:41,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf_clib.h:41,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vlib/vlib.h:44,
 from 
/vpp/build-root/install-vpp_debug-native/netlink/include/librtnl/netns.h:19,
 from /vpp/build-data/../router/router/tap_inject_netlink.c:17:
/vpp/build-data/../router/router/tap_inject_netlink.c:241:44: error: 
dereferencing pointer to incomplete type
   clib_memcpy (_addr.ip4, via->rtvia_addr, sizeof 
(rpath.frp_addr.ip4));
^
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/string.h:153:48: 
note: in definition of macro 'clib_memcpy'
#define clib_memcpy(d,s,n) memcpy_s_inline(d,n,s,n)
^
make[1]: *** [router/tap_inject_netlink.lo] Error 1
make[1]: Leaving directory `/vpp/build-root/build-vpp_debug-native/router'
make: *** [router-build] Error 2

It is compiling after I removed the whole else block, not sure how it will 
affect the plugin.

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:vpp-dev@lists.fd.io] On Behalf Of Kevin Yan
Sent: Friday, November 2, 2018 11:38 AM
To: alp.ars...@xflowresearch.com; 
vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

I also

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

2018-11-02 Thread alp . arslan

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:vpp-dev@lists.fd.io] On Behalf Of Kevin
Yan
Sent: Friday, November 2, 2018 12:16 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

 

And also remove 
else if (r->rtm.rtm_family == AF_MPLS)

part

 

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

 

for(int i = 1; label != 0; i++)

change to :
int I;
for(i = 1; label != 0; i++)

 

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

 

Tried removing both macros (RTNLGRP_MPLS_ROUTE & RTA_VIA), failed with
another MPLS related error in the router plugin. 

 

make[1]: Entering directory `/vpp/build-root/build-vpp_debug-native/router'

  CC   router/tap_inject_netlink.lo

/vpp/build-data/../router/router/tap_inject_netlink.c: In function
'get_mpls_label_stack':

/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: error: 'for'
loop initial declarations are only allowed in C99 mode

   for(int i = 1; label != 0; i++) {

   ^

/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: note: use
option -std=c99 or -std=gnu99 to compile your code

/vpp/build-data/../router/router/tap_inject_netlink.c: In function
'add_del_route':

/vpp/build-data/../router/router/tap_inject_netlink.c:200:9: error: 'for'
loop initial declarations are only allowed in C99 mode

 for(int i = 0; i < MPLS_STACK_DEPTH && stack[i] != 0; i++) {

 ^

/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: error:
'AF_MPLS' undeclared (first use in this function)

   else if (r->rtm.rtm_family == AF_MPLS)

 ^

/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: note: each
undeclared identifier is reported only once for each function it appears in

In file included from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/mem.h:55:0,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/vec.h:42,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/format.h:44,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf.h:41,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf_clib.h:41,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vlib/vlib.h:44,

 from
/vpp/build-root/install-vpp_debug-native/netlink/include/librtnl/netns.h:19,

 from
/vpp/build-data/../router/router/tap_inject_netlink.c:17:

/vpp/build-data/../router/router/tap_inject_netlink.c:241:44: error:
dereferencing pointer to incomplete type

   clib_memcpy (_addr.ip4, via->rtvia_addr, sizeof
(rpath.frp_addr.ip4));

^

/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/string.h:153:4
8: note: in definition of macro 'clib_memcpy'

#define clib_memcpy(d,s,n) memcpy_s_inline(d,n,s,n)

^

make[1]: *** [router/tap_inject_netlink.lo] Error 1

make[1]: Leaving directory `/vpp/build-root/build-vpp_debug-native/router'

make: *** [router-build] Error 2

 

It is compiling after I removed the whole else block, not sure how it will
affect the plugin. 

 

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:vpp-dev@lists.fd.io] On Behalf Of Kevin Yan
Sent: Friday, November 2, 2018 11:38 AM
To: alp.ars...@xflowresearch.com  ;
vpp-dev@lists.fd.io  
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

 

I also met this error when compiling vppsb on centos, just remove the MPLS
related macro,and re-compile

 

From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of alp.ars...@xflowresearch.com
 
Sent: Friday, November 02, 2018 1:55 PM
To: vpp-dev@lists.fd.io  
Subject: [E] [vpp-dev] VPPSB Netlink build failing

 

Dear All, 

 

I am trying to build the latest

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

2018-11-02 Thread Kevin Yan

And also remove
else if (r->rtm.rtm_family == AF_MPLS)
part

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

for(int i = 1; label != 0; i++)

change to :
int I;
for(i = 1; label != 0; i++)

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

Tried removing both macros (RTNLGRP_MPLS_ROUTE & RTA_VIA), failed with another 
MPLS related error in the router plugin.

make[1]: Entering directory `/vpp/build-root/build-vpp_debug-native/router'
  CC   router/tap_inject_netlink.lo
/vpp/build-data/../router/router/tap_inject_netlink.c: In function 
'get_mpls_label_stack':
/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: error: 'for' loop 
initial declarations are only allowed in C99 mode
   for(int i = 1; label != 0; i++) {
   ^
/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: note: use option 
-std=c99 or -std=gnu99 to compile your code
/vpp/build-data/../router/router/tap_inject_netlink.c: In function 
'add_del_route':
/vpp/build-data/../router/router/tap_inject_netlink.c:200:9: error: 'for' loop 
initial declarations are only allowed in C99 mode
 for(int i = 0; i < MPLS_STACK_DEPTH && stack[i] != 0; i++) {
 ^
/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: error: 'AF_MPLS' 
undeclared (first use in this function)
   else if (r->rtm.rtm_family == AF_MPLS)
 ^
/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: note: each 
undeclared identifier is reported only once for each function it appears in
In file included from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/mem.h:55:0,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/vec.h:42,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/format.h:44,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf.h:41,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf_clib.h:41,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vlib/vlib.h:44,
 from 
/vpp/build-root/install-vpp_debug-native/netlink/include/librtnl/netns.h:19,
 from /vpp/build-data/../router/router/tap_inject_netlink.c:17:
/vpp/build-data/../router/router/tap_inject_netlink.c:241:44: error: 
dereferencing pointer to incomplete type
   clib_memcpy (_addr.ip4, via->rtvia_addr, sizeof 
(rpath.frp_addr.ip4));
^
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/string.h:153:48: 
note: in definition of macro 'clib_memcpy'
#define clib_memcpy(d,s,n) memcpy_s_inline(d,n,s,n)
^
make[1]: *** [router/tap_inject_netlink.lo] Error 1
make[1]: Leaving directory `/vpp/build-root/build-vpp_debug-native/router'
make: *** [router-build] Error 2

It is compiling after I removed the whole else block, not sure how it will 
affect the plugin.

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:vpp-dev@lists.fd.io] On Behalf Of Kevin Yan
Sent: Friday, November 2, 2018 11:38 AM
To: alp.ars...@xflowresearch.com; 
vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

I also met this error when compiling vppsb on centos, just remove the MPLS 
related macro,and re-compile

From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of 
alp.ars...@xflowresearch.com
Sent: Friday, November 02, 2018 1:55 PM
To: vpp-dev@lists.fd.io
Subject: [E] [vpp-dev] VPPSB Netlink build failing

Dear All,

I am trying to build the latest VPP with router and netlink plugins on CentOS 
7.5. Here are the steps that I followed.

# cd /vpp
# ln -sf /vppsb/router/
# ln -sf /vppsb/netlink/
# ln -sf /vppsb/router/router.mk build-data/packages/
# ln -sf /vppsb/netlink/netlink.mk build-data/packages/
#
# make V=0 PLATFORM=vpp TAG=vpp_debug netlink-install router-install

The command fails with the following error:

make[1]: Entering directory `/vpp/build-root/build-vpp_debug-native/netlink'
  CC   librtnl/netns.lo
  CC   librtnl/rtnl.lo
/vpp/build-data/../netlink/librtnl/rtnl.c: In function 'rtnl_socket_open':
/vpp/build-data/../netlink/librtnl/rtnl.c:269:39:

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

2018-11-02 Thread Kevin Yan

for(int i = 1; label != 0; i++)

change to :
int I;
for(i = 1; label != 0; i++)

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

Tried removing both macros (RTNLGRP_MPLS_ROUTE & RTA_VIA), failed with another 
MPLS related error in the router plugin.

make[1]: Entering directory `/vpp/build-root/build-vpp_debug-native/router'
  CC   router/tap_inject_netlink.lo
/vpp/build-data/../router/router/tap_inject_netlink.c: In function 
'get_mpls_label_stack':
/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: error: 'for' loop 
initial declarations are only allowed in C99 mode
   for(int i = 1; label != 0; i++) {
   ^
/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: note: use option 
-std=c99 or -std=gnu99 to compile your code
/vpp/build-data/../router/router/tap_inject_netlink.c: In function 
'add_del_route':
/vpp/build-data/../router/router/tap_inject_netlink.c:200:9: error: 'for' loop 
initial declarations are only allowed in C99 mode
 for(int i = 0; i < MPLS_STACK_DEPTH && stack[i] != 0; i++) {
 ^
/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: error: 'AF_MPLS' 
undeclared (first use in this function)
   else if (r->rtm.rtm_family == AF_MPLS)
 ^
/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: note: each 
undeclared identifier is reported only once for each function it appears in
In file included from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/mem.h:55:0,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/vec.h:42,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/format.h:44,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf.h:41,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf_clib.h:41,
 from 
/vpp/build-root/install-vpp_debug-native/vpp/include/vlib/vlib.h:44,
 from 
/vpp/build-root/install-vpp_debug-native/netlink/include/librtnl/netns.h:19,
 from /vpp/build-data/../router/router/tap_inject_netlink.c:17:
/vpp/build-data/../router/router/tap_inject_netlink.c:241:44: error: 
dereferencing pointer to incomplete type
   clib_memcpy (_addr.ip4, via->rtvia_addr, sizeof 
(rpath.frp_addr.ip4));
^
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/string.h:153:48: 
note: in definition of macro 'clib_memcpy'
#define clib_memcpy(d,s,n) memcpy_s_inline(d,n,s,n)
^
make[1]: *** [router/tap_inject_netlink.lo] Error 1
make[1]: Leaving directory `/vpp/build-root/build-vpp_debug-native/router'
make: *** [router-build] Error 2

It is compiling after I removed the whole else block, not sure how it will 
affect the plugin.

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:vpp-dev@lists.fd.io] On Behalf Of Kevin Yan
Sent: Friday, November 2, 2018 11:38 AM
To: alp.ars...@xflowresearch.com; 
vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

I also met this error when compiling vppsb on centos, just remove the MPLS 
related macro,and re-compile

From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of 
alp.ars...@xflowresearch.com
Sent: Friday, November 02, 2018 1:55 PM
To: vpp-dev@lists.fd.io
Subject: [E] [vpp-dev] VPPSB Netlink build failing

Dear All,

I am trying to build the latest VPP with router and netlink plugins on CentOS 
7.5. Here are the steps that I followed.

# cd /vpp
# ln -sf /vppsb/router/
# ln -sf /vppsb/netlink/
# ln -sf /vppsb/router/router.mk build-data/packages/
# ln -sf /vppsb/netlink/netlink.mk build-data/packages/
#
# make V=0 PLATFORM=vpp TAG=vpp_debug netlink-install router-install

The command fails with the following error:

make[1]: Entering directory `/vpp/build-root/build-vpp_debug-native/netlink'
  CC   librtnl/netns.lo
  CC   librtnl/rtnl.lo
/vpp/build-data/../netlink/librtnl/rtnl.c: In function 'rtnl_socket_open':
/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),
   ^
/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: note: each undeclared 
identifier is reported only once for each function it appears in

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

2018-11-02 Thread alp . arslan

Tried removing both macros (RTNLGRP_MPLS_ROUTE & RTA_VIA), failed with
another MPLS related error in the router plugin. 

 

make[1]: Entering directory `/vpp/build-root/build-vpp_debug-native/router'

  CC   router/tap_inject_netlink.lo

/vpp/build-data/../router/router/tap_inject_netlink.c: In function
'get_mpls_label_stack':

/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: error: 'for'
loop initial declarations are only allowed in C99 mode

   for(int i = 1; label != 0; i++) {

   ^

/vpp/build-data/../router/router/tap_inject_netlink.c:154:3: note: use
option -std=c99 or -std=gnu99 to compile your code

/vpp/build-data/../router/router/tap_inject_netlink.c: In function
'add_del_route':

/vpp/build-data/../router/router/tap_inject_netlink.c:200:9: error: 'for'
loop initial declarations are only allowed in C99 mode

 for(int i = 0; i < MPLS_STACK_DEPTH && stack[i] != 0; i++) {

 ^

/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: error:
'AF_MPLS' undeclared (first use in this function)

   else if (r->rtm.rtm_family == AF_MPLS)

 ^

/vpp/build-data/../router/router/tap_inject_netlink.c:228:33: note: each
undeclared identifier is reported only once for each function it appears in

In file included from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/mem.h:55:0,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/vec.h:42,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/format.h:44,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf.h:41,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/elf_clib.h:41,

 from
/vpp/build-root/install-vpp_debug-native/vpp/include/vlib/vlib.h:44,

 from
/vpp/build-root/install-vpp_debug-native/netlink/include/librtnl/netns.h:19,

 from
/vpp/build-data/../router/router/tap_inject_netlink.c:17:

/vpp/build-data/../router/router/tap_inject_netlink.c:241:44: error:
dereferencing pointer to incomplete type

   clib_memcpy (_addr.ip4, via->rtvia_addr, sizeof
(rpath.frp_addr.ip4));

^

/vpp/build-root/install-vpp_debug-native/vpp/include/vppinfra/string.h:153:4
8: note: in definition of macro 'clib_memcpy'

#define clib_memcpy(d,s,n) memcpy_s_inline(d,n,s,n)

^

make[1]: *** [router/tap_inject_netlink.lo] Error 1

make[1]: Leaving directory `/vpp/build-root/build-vpp_debug-native/router'

make: *** [router-build] Error 2

 

It is compiling after I removed the whole else block, not sure how it will
affect the plugin. 

 

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:vpp-dev@lists.fd.io] On Behalf Of Kevin
Yan
Sent: Friday, November 2, 2018 11:38 AM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [E] [vpp-dev] VPPSB Netlink build failing

 

I also met this error when compiling vppsb on centos, just remove the MPLS
related macro,and re-compile

 

From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of alp.ars...@xflowresearch.com
 
Sent: Friday, November 02, 2018 1:55 PM
To: vpp-dev@lists.fd.io  
Subject: [E] [vpp-dev] VPPSB Netlink build failing

 

Dear All, 

 

I am trying to build the latest VPP with router and netlink plugins on
CentOS 7.5. Here are the steps that I followed. 

 

# cd /vpp

# ln -sf /vppsb/router/

# ln -sf /vppsb/netlink/

# ln -sf /vppsb/router/router.mk build-data/packages/

# ln -sf /vppsb/netlink/netlink.mk build-data/packages/

#

# make V=0 PLATFORM=vpp TAG=vpp_debug netlink-install router-install

 

The command fails with the following error: 

 

make[1]: Entering directory `/vpp/build-root/build-vpp_debug-native/netlink'

  CC   librtnl/netns.lo

  CC   librtnl/rtnl.lo

/vpp/build-data/../netlink/librtnl/rtnl.c: In function 'rtnl_socket_open':

/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),

   ^

/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: note: each undeclared
identifier is reported only once for each function it appears in

/vpp/build-data/../netlink/librtnl/netns.c:69:5: error: 'RTA_VIA' undeclared
here (not in a function)

   _(RTA_VIA, via, 1)\

 ^

/vpp/build-data/../netlink/librtnl/netns.c:82:13: note: in definition of
macro '_'

 .type = t, .unique = u, \

 ^

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

2018-11-02 Thread Kevin Yan

I also met this error when compiling vppsb on centos, just remove the MPLS 
related macro,and re-compile

From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of 
alp.ars...@xflowresearch.com
Sent: Friday, November 02, 2018 1:55 PM
To: vpp-dev@lists.fd.io
Subject: [E] [vpp-dev] VPPSB Netlink build failing

Dear All,

I am trying to build the latest VPP with router and netlink plugins on CentOS 
7.5. Here are the steps that I followed.

# cd /vpp
# ln -sf /vppsb/router/
# ln -sf /vppsb/netlink/
# ln -sf /vppsb/router/router.mk build-data/packages/
# ln -sf /vppsb/netlink/netlink.mk build-data/packages/
#
# make V=0 PLATFORM=vpp TAG=vpp_debug netlink-install router-install

The command fails with the following error:

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

Can anyone help me with this? Or point me towards the versions of VPP and VPPSB 
where they are working with each other.

Regards,
Alp Arslan

This e-mail message may contain confidential or proprietary information of 
Mavenir Systems, Inc. or its affiliates and is intended solely for the use of 
the intended recipient(s). If you are not the intended recipient of this 
message, you are hereby notified that any review, use or distribution of this 
information is absolutely prohibited and we request that you delete all copies 
in your control and contact us by e-mailing to secur...@mavenir.com. This 
message contains the views of its author and may not necessarily reflect the 
views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor 
email messages, but make no representation that such messages are authorized, 
secure, uncompromised, or free from computer viruses, malware, or other 
defects. Thank You
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11068): https://lists.fd.io/g/vpp-dev/message/11068
Mute This Topic: https://lists.fd.io/mt/27825214/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] Regarding vlib_buffer_alloc

Re: [vpp-dev] Regarding vlib_buffer_alloc

Re: [vpp-dev] auto-abandon

[vpp-dev] Regarding vlib_buffer_alloc

Re: [vpp-dev] PPPoE plugin documentation/support

Re: [vpp-dev] Incrementing node counters

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

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

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

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

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

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

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

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

14 matches

Site Navigation

Mail list logo

Footer information