Hi ,
I have looked at the ipsec code in VPP and trying to understand how it
works in a multi threaded environment. Noticed that the datastructures for
spd, sad and tunnel interface are pools and there are no locks to prevent
race conditions.
For instance the ipsec-input node passes SA index to
Hi all,
We edited vpp.mk like this:
vpp.mk
# vector packet processor
vpp_arch = native
ifeq ($(shell uname -m),x86_64)
vpp_march = core2# Nehalem Instruction set
vpp_mtune = intel# Optimize for Sandy Bridge
else ifeq ($(shell uname -m),aarch64)
ifeq ($(TARGET_PLATFORM),thunderx)
Hi,
We are using VPP release 18.01 . We want to move "clib_warning" output from
/var/log/messages" to some other path.
Please provide your suggestions.
Thanks,
Chetan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9707):
On Mon, Jun 25, 2018 at 7:09 PM, Jeff Bushman wrote:
> Is there any documentation, examples or discussion of how to use the VPP
> API Modules beyond the short documentation here?
> https://docs.fd.io/vpp/18.07/vapi_doc.html
Jeff,
If you are interested in the C API, there is also this:
Yes, good indicator is "average vectors/node" in show run. Bigger number means
VPP is more busy but also more efficient.
Maximum value us 255 (unless you change VLIB_FRAME_SIZE in code). It basically
means how many packets are processed
in batch. If VPP is not loaded it will likely poll so fast
Hi,
I've tested nat64 functionality with ping6 in vpp 1807, the ping
responses after more than 60 seconds. it seems that the ipv6 neighbor
created with a long delay. how can I fixed it?
This is my configuration :
set interface nat64 in GigabitEthernet0/6/0
set interface nat64 out
