Dear VPP Dev Team,
i found a problem with creating a VPP ACL with IPv6 SRC / DST Address. The ACL
created incorrectly. The problem occurs when "any" ::/0 is used as the SRC
address.
Example (correct)
vpp# set acl-plugin acl permit src 2a00:c940::/32
ACL index:35
vpp# show acl-plugin acl
Hi Jens,
Thanks for the report !
There are two issues. First, if a parameter is omitted, it is implicitly
initialized to 0.0.0.0/0 - as a shortcut for the debugging.
So even the “working” case is not correct - you end up with ipv6 source and
ipv4 destination, which may give you
Dear Filip,
Thank you very much for your prompt reply!
I have attached the startup.conf files for the case with 2 workers
(startup.conf-mc1wc02) and for the case when I used only the main core
(startup.conf-mc0). In both cases, 4 CPU cores (0-3) were enabled and
cores 0-2 were excluded from
Hi Gabor,
I will look into it and get back to you. Meanwhile could you run the same
test with a debug build and post the results ? Maybe even core dump. Also
please post your startup.conf file
Best regards,
Filip Varga
st 9. 11. 2022 o 7:50 Gabor LENCSE napísal(a):
> Dear VPP Developers,
>
>
Dear VPP Developers,
I am a researcher and I would like to benchmark the performance of the
stateful NAT64 implementation of FD.io VPP.
Unfortunately, VPP crashed with segmentation fault.
Some details:
I used two Dell PowerEdge R430 servers as the Tester and the DUT (Device
Under Test),
Hi,Mohsin
I used linux veth pari interface as af-packet interfeace in vpp.
When the vpp run for some time, there are many "tx frame not ready " error
in host-vpp1out-tx.
If there is error, we can not ping from linux side to vpp side. Must need
restart vpp to restore.
From old mail. you
