: Wednesday, August 30, 2017 9:45 AM
To: Florin Coras ; Prabhjot Singh Sethi
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Issue forwarding TCP packets
Hi Florin,
For now we can proceed with a requirement to disable offload on VMs. but still
keeping performance in view i think VPP should have
;Prabhjot Singh Sethi" .
Cc:
Sent:
Tue, 29 Aug 2017 11:13:14 -0700
Subject:
Re: [vpp-dev] Issue forwarding TCP packets
Hi Prabhjot,
In your setup, VPP just switches packets from one interface to the
other, irrespective of their L4 checksum. That is, it does not read
nor update them. Therefo
Hi Prabhjot,
In your setup, VPP just switches packets from one interface to the other,
irrespective of their L4 checksum. That is, it does not read nor update them.
Therefore, since the source Linux interface does not provide correct checksums,
the destination rejects all packets.
As you’ve
Thanks Florin,
it works with offload disabled, earlier when i tried changing
offload settings i missed doing it on one machine.
However my question is still about why VPP is unable to handle it, is
it a missing configuration or missing functionality in VPP?
i can ssh from one vm to ano
Hi Prabhjot,
>From your description, I suspect it may be a linux tcp checksum offload issue.
>Could you try disabling it for all interfaces with:
ethtool --offload rx off tx off
Hope this helps,
Florin
> On Aug 28, 2017, at 10:56 AM, Prabhjot Singh Sethi
> wrote:
>
> We have been trying
We have been trying to use VPP as a L2/L3 forwarding data path between
VMs.
where we have connected tap interfaces from VM to VPP using "create
host-interface name "
after adding both the interfaces to same bridge-domain (bd_id = 2), we
are able to ping from
one VM to another (both in same subnet
