Re: [vpp-dev] vppsb's librtnl is broken with top of VPP tree

Oh, doh, it's vppsb that has the issue. I'll go back to sleep. :) Chris

Re: [vpp-dev] vppsb's librtnl is broken with top of VPP tree

I just submitted a patch to fix it. https://gerrit.fd.io/r/#/c/11127/ 2018-03-13 18:35 GMT-04:00 Jon Loeliger : > Hey VPP-dev > > Is it me? It's me, isn't it. > > jdl > > > > > librtnl/mapper.c: In function 'mapper_add_del_route': > librtnl/mapper.c:101:31: error: passing

[vpp-dev] vppsb's librtnl is broken with top of VPP tree

Hey VPP-dev Is it me? It's me, isn't it. jdl librtnl/mapper.c: In function 'mapper_add_del_route': librtnl/mapper.c:101:31: error: passing argument 10 of 'fib_table_entry_path_add' from incompatible pointer type [-Werror] FIB_ROUTE_PATH_FLAG_NONE);

Re: [vpp-dev] issues with opensuse and centos verify job for stable/1801

hey matus, tl;dr: https://gerrit.fd.io/r/11124 should get around this for now and future This is because the newer version is not only installed but in some cases the repo ‘ledgers’ are older than whats currently installed. (Due to the fact that I build the base build containers far more

[vpp-dev] FD.io ARM virtual key signing Wed Mar 14 6am PST

Dear all, If you wish to access Arm hardware in the community lab for FD.io work, please join tomorrow’s meeting, with your keys, IDs, webcams ready, you will be signed virtual key. https://wiki.fd.io/view/VPP/AArch64 https://zoom.us/j/5301185804 More information how to get

[vpp-dev] issues with opensuse and centos verify job for stable/1801

Hi, I see issues with opensuse and centos verify jobs for stable/1801 branch. The error is same for both jobs: 11:39:26 11:39:27 package vpp-dpdk-devel-18.02-vpp1.x86_64 (which is newer than vpp-dpdk-devel-17.11-vpp1.x86_64) is already installed

Re: [vpp-dev] make TEST=test_ip6 test failing on multiple machines, when NOT run as root.

On Tue, Mar 13, 2018 at 5:47 AM, Klement Sekera wrote: > I would say that this should be worth the extra effort just to have the > same conditions. Otherwise the verify job does something different than > `make test` on your box and that could be confusing. > > Thanks, >

Re: [vpp-dev] order of running 2 plugins

The feature arc infra handles dispatching packets from feature to feature, depending on the set of enabled features. It's fine to define static arcs to e.g. error-drop, but there's no need to manually dispatch packets to the next feature node. Use vnet_get_config_data(...) to set next0 as

Re: [vpp-dev] Decision point for next node ipv4 or ipv6

Thank you Ole On Tue, Mar 13, 2018 at 11:39 AM, Ole Troan wrote: > Hi Sara, > >> Can someone refer to a code where a decision is made for the next >> node - ipv4 or ipv6 ? > > Take a look at ethernet_register_input_type() > You can also look at the graph (e.g. show vlib

[vpp-dev] order of running 2 plugins

Hi, i've implemented 2 plugins plgA and plgB 1. plgA is running immediately after 'device-input' node 2. plgB should run after plgA 3. interface-output should run after plgB i set this these for plgA and plgB VNET_FEATURE_INIT (plgA, static) = { .arc_name = "device-input", .node_name =

Re: [vpp-dev] flowprobe ip4 at L2 interface

Hi Ole, already tried that, just not exactly this way. shell# ip link add name spanout type veth peer name spanhost shell# ip link set up dev spanout shell# ip link set up dev spanhost vpp# create host-interface name spanout vpp# set int state host-spanout up vpp# set int ip addr host-spanout

Re: [vpp-dev] make TEST=test_ip6 test failing on multiple machines, when NOT run as root.

I would say that this should be worth the extra effort just to have the same conditions. Otherwise the verify job does something different than `make test` on your box and that could be confusing. Thanks, Klement > -Original Message- > From: vpp-dev@lists.fd.io

Re: [vpp-dev] flowprobe ip4 at L2 interface

Hi Linas, > are there any plans to make inbound flowprobe? > > I'm drafting xeon box (connected to a switch span port) with flow collector > and several pmacct instances (each with different aggregation vectors and > time intervals) waiting for netflow/ipfix. Unfortunately I've got stuck in >

Re: [vpp-dev] Decision point for next node ipv4 or ipv6

Hi Sara, > Can someone refer to a code where a decision is made for the next > node - ipv4 or ipv6 ? Take a look at ethernet_register_input_type() You can also look at the graph (e.g. show vlib graph) to see which node has ip4-input / ip6-input as next nodes. Best regards, Ole > I

Re: [vpp-dev] Freezing Session Deletion Operation

Dear Rubina, I have adjusted my trex config to match yours - increased 2m to 4m, but that still didn't change much. The only thing your config could be adapted is to have "deny" instead of "drop" in the ACL configuration - right now one of your ACLs does not have any rules, it is best to avoid

[vpp-dev] Decision point for next node ipv4 or ipv6

HI, Can someone refer to a code where a decision is made for the next node - ipv4 or ipv6 ? I understand that in order to keep the instruction cache - ip nodes must be separated to ipv4 and ipv6 , correct ? Thank you -Sara -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this

Re: [vpp-dev] VPP As A Router Between Namespaces - 10ms latency

Thank you John On Mon, Mar 12, 2018 at 9:11 PM, John Lo (loj) wrote: > The functions in the area you are interested may be the unformat functions > unformat_vnet_sw_interface(), unformat_vnet_hw_interface() in > src/vnet/interface_format.c used by VPP CLI to get sw_if_index or

Re: [vpp-dev] flowprobe ip4 at L2 interface

Hello, are there any plans to make inbound flowprobe?  I'm drafting xeon box (connected to a switch span port) with flow collector and several pmacct instances (each with different aggregation vectors and time intervals) waiting for netflow/ipfix. Unfortunately I've got stuck in stalemate:

Re: [vpp-dev] Freezing Session Deletion Operation

Dear Andrew My Trex config is uploaded; I also tested the scenario with your Trex config. The stability of vpp in your run is strange. When I run this scenario, vpp crashes in my DUT machine after about 200 second of running Trex. In this period I see #del sessions is 0 until session pool