Hi Damjan,
So vpp2 is basically the container APP doing the l2fwd. Will give it a try.
Thanks
William
On Fri, Aug 23, 2019 at 8:41 AM Damjan Marion wrote:
>
>
> I typically used 2 vpp instances, one doing xconnect between physical NIC and
> memif interface, another VPP instance routing between
I typically used 2 vpp instances, one doing xconnect between physical NIC and
memif interface, another VPP instance routing between 2 memif interfaces.
i.e.
trex-port1 — (p)vpp1(m) — (m)vpp2(m) — (m)vpp1(p) — trex-port2
Where (p) is physical nic interface, and (m) is memif interface.
On the V
Hi,
I'm looking for something like l2fwd application using memif interfaces.
So at a container, simply receive packets from one memif port, and forward
to another memif port.
I'm trying to measure the performance in slide
Memif Performance – L2
https://events.linuxfoundation.org/wp-content/upload
Please try master/latest: https://gerrit.fd.io/r/c/vpp/+/21468 fixed a source
of trivial spin-lock bugs.
HTH... Dave
From: Dave Barach (dbarach)
Sent: Thursday, August 22, 2019 12:11 PM
To: Carlito Nueno
Cc: vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] Crash when using dns_name_server
NP, sorry
Congratulations to all guys involved!
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Andrew
Yourtchenko
Sent: Wednesday, August 21, 2019 1:58 PM
To: vpp-dev ; csit-dev
Subject: [vpp-dev] VPP 19.08 release is available!
Hi all,
the VPP release 1
Hi Neale,
that's my desired flow, the actual flow is
00:04:08:057376: dpdk-input
GigabitEthernet0/b/0 rx queue 0
buffer 0xcc2f: current data 0, length 98, free-list 0, clone-count 0,
totlen-nifb 0, trace 0x3
ext-hdr-valid
l4-cksum-computed l4-cksum-correct
Hi Dave,
That flow would suggest the packet was correctly sent out of GigEth0/a/0 with
the destination MAC of 172.16.3.1. was that not the case? Or was that your
desired flow not the actual?
/neale
De : shi dave
Date : vendredi 23 août 2019 à 09:11
À : "Neale Ranns (nranns)" , "vpp-dev@lists
Hi Neale,
sorry, clerical error, the flow is
dpdk-input
ip4-input (GigabitEthernet0/b/0)
ip4-lookup
ip4-rewrite (GigabitEthernet0/a/0)
ipsec-output-ip4
dpdk-esp-encrypt
dpdk-crypto-input
ip4-lookup (dst 172.16.3.1)
ip4-rewrite (GigabitEthernet0/a/0)
ipsec-output-ip4 (by pass)
Best Rregards
D
Hi Neale,
When routing to GigabitEthernet0/a/0, it could run into ipsec-output-ip4, then
the packet will be added a ipsec tunnel ip (src 172.16.3.15, dst 172.16.3.1),
so the destination MAC is the mac of 172.16.3.1
the flow is like:
dpdk-input
ip4-input (GigabitEthernet0/b/0)
ip4-lookup
ip4-re
