WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] tcp/udp checksum and bridging

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] tcp/udp checksum and bridging
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sun, 6 Jan 2008 21:27:02 +1100
Delivery-date: Sun, 06 Jan 2008 02:27:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchQTq1SohWFYBr6T4mFs52Ka7ynkQ==
Thread-topic: tcp/udp checksum and bridging
I have a setup with a Linux PV DomU which is on the same bridge as a
Windows DomU using the PV drivers which Andy and I have been developing.

When a tcp packet originates from anywhere but on the same bridge,
everything is fine, but when the packet originates from a machine on the
same bridge, the checksum is wrong.

I think the problem is that the Linux DomU assumes that something else
will do the checksum of the tcp packet, which is mostly correct unless
the packet is only bridged and not routed...

Any suggestions?

Thanks

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>