Hi All,
I am trying to make NAT44 ed work for TCP/UDP traffic on my setup. My setup is
as follows
Host A, Host B <-VPP <- Host C
Host A , Host B and Host C can communicate to each other via VPP. The VPP
container has two interfaces. My current version of VPP is
Hi Ben,
It is coming out of D state and not staying there, we saw memif buffer
exhaustion on client side so started debugging and saw VPP worker is going in D
state and this happens after 2-3 hours of run.
Will try to capture vpp worker stack and share.
Line 39896: 6701 root 20 0
Merged, thanks Atzm!
Best
ben
> -Original Message-
> From: vpp-dev@lists.fd.io On Behalf Of
> atzm...@gmail.com
> Sent: Monday, August 8, 2022 10:18
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] ikev2 rekeying with multiple notify payloads
>
> Hi,
>
> In RFC 7296, Child SA rekey
Hi,
In RFC 7296, Child SA rekey using CREATE_CHILD_SA may include multiple Notify
payloads.
VPP's current ikev2 plugin implementation seems to support multiple Notify
payloads but to expect the REKEY_SA message is placed after any other Notify
payloads.
Some implementation sends rekey request
Can you share the output of 'cat /proc//stack'?
This should tell us where the worker is stuck in the kernel.
Best
ben
> -Original Message-
> From: vpp-dev@lists.fd.io On Behalf Of Satish Singh
> Sent: Saturday, August 6, 2022 20:36
> To: vpp-dev@lists.fd.io; vpp-dev+h...@lists.fd.io
>
Hi Saravana,
As far as I know, it was lack of maintenance (by lack of interest from the
community). There was no maintainer, and the code did not keep up and was
broken.
For it to re-instantiated, it would need to be updated for current master, and
someone should volunteer to maintain it.