Verified that the fix resolves the Bihash test failure (rebased 30734):
https://logs.fd.io/sandbox/vex-yul-rot-jenkins-2/daw_30773-vpp-verify-master-ubuntu2004-aarch64/2/
There are still 6 ikev2 test failures from this test run that need to be
resolved. These all have core file stack traces av
Hi Filip,
Thanks, I understand, det44 plugin is working separately but we should manually
manage mapping local network to external IP.
But in case we try to use standard nut configuration with pools:
vpp# nat44 forwarding enable
vpp# set int nat44 in GigabitEthernet0/5/0 out GigabitEthernet0/4/0
> I see that this change is done as part of following commit.
I only edited variable names and such.
The previous code contained the same logic [1],
and it seems to come from the initial code [2].
> we are deleting the socket_main.input_buffer
No, we are deleting just some (perhaps all)
elements
Merged. Thanks Dave! :-)
--a
> On 10 Feb 2021, at 16:17, Dave Wallace wrote:
>
> Thanks Dave!
> -daw-
>
> On 2/10/2021 7:54 AM, v...@barachs.net wrote:
>> To make the pain go away, I quadrupled the vapi timeout for the bihash test
>> vectors. Turns out that a couple of tests run for almost
Hi Nikhil,
That’s a vcl api, it can only fail if it’s called twice or if the attachment to
vpp fails. Enable vcl debug by exporting VCL_DEBUG=2 and check what failed.
Regards,
Florin
> On Feb 10, 2021, at 6:40 AM, nikhil subhedar wrote:
>
> Hi All,
>
> my vppcom_app_create() is failing .
Thanks Dave!
-daw-
On 2/10/2021 7:54 AM, v...@barachs.net wrote:
To make the pain go away, I quadrupled the vapi timeout for the bihash
test vectors. Turns out that a couple of tests run for /almost/ 5
seconds (on aarch64, debug) which caused sporadic failures.
That’s probably about the rig
Hi All,
my vppcom_app_create() is failing . so tried to trace the error and
converted the error in string format and i am getting below error as
""UNKNOWN_STATE".
the config which is suggested over forum i used as is except one thing
i.e. i did not added
dpdk {
dev :03:00.0
}
remaining c
To make the pain go away, I quadrupled the vapi timeout for the bihash test
vectors. Turns out that a couple of tests run for almost 5 seconds (on aarch64,
debug) which caused sporadic failures.
That’s probably about the right size hammer for this specific problem.
FWIW... Dave
From:
Hello,
For clarification i will explain how the nat is devided.
At this point NAT functionality is devided in multiple sub plugins because of
it's previous complexity and issues with it.
We have det44 and nat44 plugins that are completely separate. The whole
separation is still in progress. So
Hi ,
While using AddressSanitizer with VPP, it detected use-after-poison in
vl_socket_read_ready() function.
Closely looking at the code, it seems that this is happening due to the
following code.
if (vec_len (msg_buffer) > msgbuf_len)
/* There are some fragments left. Shrink the msg_buffer to
10 matches
Mail list logo
