Hi Carlito,
Seems like you are sending IP fragments.
Those need to be (virtually) reassembled before NATted. Reassembly is to a
large extent an attack vector, and it’s rate limited.
cheers,
Ole
> On 3 Mar 2019, at 22:46, carlito nueno wrote:
>
> Hi all,
>
> While running more iperf3 udp test
Hi Matus,
Thank you. That makes sense.
On Thu, Jan 17, 2019 at 10:59 PM Matus Fabian -X (matfabia - PANTHEON
TECHNOLOGIES at Cisco) wrote:
>
> Hi,
>
>
>
> For endpoint dependent NAT oldest session per user is recycled only when
> expired (classic/vanilla NAT recycle always).
>
>
>
> Matus
>
>
>
Hi all,
While running more iperf3 udp tests, I noticed vpp status showing this:
My current vpp conf:
https://gist.github.com/ironpillow/4b119b57e21b31a7ff6985bcb20f952b
Setup to reproduce:
1. iperf3 server on 10.155.3.2 (iperf3 -s -B 10.155.3.2)
2. iperf3 client on 10.155.6.2 but with -R flag (i
Please read this and try again:
https://fdio-vpp.readthedocs.io/en/latest/troubleshooting/reportingissues/reportingissues.html
From: vpp-dev@lists.fd.io On Behalf Of omid via
Lists.Fd.Io
Sent: Sunday, March 3, 2019 12:37 PM
To: Vpp-dev
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] problem with tw
Hi,
There's a strange problem I confront with in VPP.
Here is the scenario:1- (Success) I generate a 1 Gig/sec traffic from a port
and everything is ok with VPP.2- (Failure) I generate two 500 MB/sec traffics
from two different ports but all of sudden VPP stops forwarding and then even a
simple