[Edited Message Follows]
I tried to send the reverse traffic from 192.168.200.20 <-> 192.168.100.20.
I investigated further. It looks like DPDK is not transmitting the traffic on
the VPP n after it got decrypted from IPSEC.
Same issue but this time interface eth3 owned by DPDK on VPP1 is still u
I tried to send the reverse traffic from 192.168.200.20 <-> 192.168.100.20.
I investigated further. It looks like DPDK is not transmitting the traffic
on the VPP1 node after it got decrypted from IPSEC.
Same issue but this time interface eth3 owned by DPDK on VPP1 is still up.
The local ping from
That looks suspicious for sure... Can you try with VPP native virtio driver
instead of DPDK?
ben
> -Original Message-
> From: satish amara
> Sent: jeudi 19 août 2021 17:43
> To: Benoit Ganne (bganne)
> Cc: vpp-dev@lists.fd.io; Damjan Marion
> Subject: Re: [vpp-dev] DPDK initialization
Also, I noticed an interesting thing. After I stop the (exit) VPP the
queued packets are sent out by the DPDK driver.
On Thu, Aug 19, 2021 at 11:32 AM satish amara
wrote:
> What is surprising is everything works fine until I do IPSEC. The ping to
> local networks on the eth3 interface works fi
What is surprising is everything works fine until I do IPSEC. The ping to
local networks on the eth3 interface works fine until IPSEC traffic starts.
After IPSEC traffic starts on VPP2 the connectivity on eth3 to local LAN is
gone.
On Thu, Aug 19, 2021 at 11:20 AM Benoit Ganne (bganne)
wrote:
>
I do not see any issue in these logs, everything looks like it is working fine.
This could be a config issue on the host side.
If you use dpdk testpmd between the interfaces instead of VPP, does it work?
Also, you can try using VPP native virtio driver instead of dpdk, see "create
interface virtio
Hi,
Here are the attached logs. I also see the counters on eth3 get
increments after pings packets are sent out. The packets are never sent out
after that.
They are stuck on tx queue. Thank you for looking into this.
Regards,
Satish K Amara
On Thu, Aug 19, 2021 at 3:13 AM Benoit Ganne (bgan
What version of VPP are you using? A patch was merged 2 days ago which may
fix the problem - https://gerrit.fd.io/r/c/vpp/+/33018.
-Matt
On Thu, Aug 19, 2021 at 7:57 AM wrote:
> vpp version: 21.06
> vpp main core will be stucked after bridge and loop interfaces and snat is
> configured, here
Sounds like the issue fixed in [0] (so after 21.06).
Vratko.
[0] https://gerrit.fd.io/r/c/vpp/+/33018
From: vpp-dev@lists.fd.io On Behalf Of g.good...@gmail.com
Sent: Thursday, 2021-August-19 14:58
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vpp got stucked after bridge and loop interfaces is cr
vpp version: 21.06
vpp main core will be stucked after bridge and loop interfaces and snat is
configured, here is my topology.
/--\/--\/--\
| || || |
|
I do not think those are hard errors, especially if packets go through.
To debug the ipsec issue we'll need a packet trace, eg.:
~# vppctl cle tr
~# vppctl tr add dpdk-input 100
~# vppctl sh tr
Best
ben
> -Original Message-
> From: vpp-dev@lists.fd.io On Behalf Of satish amara
> Sent: m
11 matches
Mail list logo
