I have built the new release with vpp version 18.10 on my local machine.
I have seen "git log" and your commit is showing in it.
I am still experiencing the crash when VM connects with VPP in deterministic
mode.
Kindly, provide an explanation for the crash or a workaround for this.
Hi, Florin,
Based on this discuss, I have submitted a code review #14156 for this. Please
help review it.
The main change is:
1) Add a point in ctx_id to point engine specific data, and point to a
openssl_tls_ctx data structure.
2) Add 2 engine specific API such for start listen
Hello VPP folks,
I have several questions/comments on memif and libmemif.
1) I believe "mq[x].last_tail = 0" is missing from
memif_init_regions_and_queues().
2) I have a libmemif app connecting to two different memif sockets and I
noticed that if my app fails to connect to the first socket it
VPP interface by default is in L3 mode and has to be set into L2 mode for
either bridging or cross connect. The reason, setting up an interface cross
connected to the 2nd interface only does not work, is that the second interface
is not in L2 mode. Thus, L2 forwarding cannot output packets on
Hi,
I want to use the L2 xconnect feature only in one direction, i.e suppose i
have 2 ports x and y,
i want to only do "set interface l2 xconnect X Y" so that all traffic from
port X is sent to port Y.
If I do this only one direction it is not working. It works only if i do it
both the direction
I decided to use Trex for generating packet.
I could not find any information about how to setup a client-server
scenario in Trex.
My scenario is that I have to device each of which has eight port. Each
port of first device is connected to the corresponding port of the second
device.
Now I want
