Hi,
Can the vlib_time_now api be used in worker threads? Looking at the code, this
api does not seam to be thread safe.
But there are a few places where it is used in nodes that do packet processing.
For example in nat, cdp and few other places.
Found the following thread where it is mentioned
Dear all,
19.08.1 release artifacts are available on packagecloud.io.
I have tested their installability in Ubuntu and Centos.
As mentioned before, due to a couple of the fixes with the API changes
that had to be made,
the release artifacts for 19.08 have been moved to
https://packagecloud.io/fd
Hello,
Skip_n_vectors is 0 as the mask (as well as match value) is already shifted by
one vector in PAPI:
VAT mask:
PAPI mask:
But there was identi
VAT classify_add_del_session contains "skip_n 1",
but PAPI classify_add_del_session does not contain
"skip_n_vectors" argument, (so the default 0 is used).
Not sure whether that is causing the different behavior,
but there may be other differences.
Vratko.
From: csit-...@lists.fd.io On Behalf O
Sounds like one of the threads hasn't finished rebuilding its graph replica
after you crank up the ipsec tunnel. That operation occurs N-way parallel, with
each thread rebuilding its own replica.
Take a look at [aka ASSERT] *vlib_worker_threads->node_reforks_required == 0 at
the moment when you
Hi,
I'm testing following scene:
vm1-172.16.11.2 -> SNAT to public1-192.168.1.100 to access public2-192.168.1.2,
and reversely, 192.168.1.2 access 192.168.1.100 DNAT to 172.16.11.2.
With these key configs:
vppctl set int ip address host-ve_eip1 192.168.1.100/24
vppctl nat44 add interface addres
Hi Jan,
Can you try to compare the two API traces?
Either using src/tools/vppapitrace
or "api trace dump" inside of VPP.
Cheers,
Ole
> On 18 Sep 2019, at 10:30, Jan Gelety via Lists.Fd.Io
> wrote:
>
> Hello vpp-dev,
>
> We are converting CSIT Policer.py library to use PAPI instead of VAT
Hello vpp-dev,
We are converting CSIT Policer.py library to use PAPI instead of VAT commands.
Unfortunately policer functional
test is failing with "Invalid DSCP: 0, should be 20 " in case of configuration
via PAPI.
The root cause seems to be that policer_index is not set for policer-classify