Hello
I am facing a problem where eth+nsh encapsulated packets egress OVS
with incorrect checksum.
The scenario is
client vnf server
all guests on the same host so this is vm2vm traffic, tap ports are
directly added to the ovs bridge. TCP traffic from/to server port 80 is
encapsulate
: Jaime Caamaño Ruiz
Reply-To: jcaam...@suse.com
To: ovs-discuss@openvswitch.org, jcaam...@suse.de
Subject: [ovs-discuss] Bad checksums observed with nsh encapsulation
Date: Wed, 13 Jun 2018 12:51:59 +0200
Hello
I am facing a problem where eth+nsh encapsulated packets egress OVS
with incorrect
skb);
}
Tried that and got rid of my problem.
Any thoughts?
BR
Jaime.
-Original Message-
From: Jaime Caamaño Ruiz
Reply-To: jcaam...@suse.com
To: jcaam...@suse.com, ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] Bad checksums observed with nsh
encapsulation
Date: Thu, 14 Jun 2018 18
Jaime Caamaño Ruiz
Sent: Monday, June 25, 2018 5:45 PM
To: jcaam...@suse.com; ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] Bad checksums observed with nsh encapsulation
Hello
I looked a bit more into the issue.
This is happenning when OVS receives a CHECKSUM_PARTIAL. For a normal vm2vm
> But when we are pushing nsh headers, the first receiver may not be
> the final receiver and CHECKSUM_PARTIAL may not reach the final
> reciever which will then verify and reject a bad checksum.
I don't understand this. Could you please provide a minimal test case?
I will then reproduce locally a
/datapath/datapath.c#L439
-Original Message-
From: Jiri Benc
To: Yi Y Yang
Cc: ovs-discuss@openvswitch.org , jcaamano
@suse.de
Subject: Re: [ovs-discuss] Bad checksums observed with nsh
encapsulation
Date: Tue, 26 Jun 2018 17:07:11 +0200
> But when we are pushing nsh headers, the fi
Hi Jiri
Did you have the chance to take a look at this?
Thanks,
Jaime.
-Original Message-
From: Jaime Caamaño Ruiz
Reply-To: jcaam...@suse.com
To: Jiri Benc , Yi Y Yang
Cc: ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] Bad checksums observed with nsh
encapsulation
Date: Fri
