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/
Home Products Support Community News


Re: [Xen-users] tcp checksum errors across dom0-domu bridge

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-users] tcp checksum errors across dom0-domu bridge
From: Daniel Goertzen <goertzen@xxxxxxxx>
Date: Fri, 30 Dec 2005 11:29:06 -0600
Cc: ian.pratt@xxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 30 Dec 2005 17:33:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D409EDF@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D409EDF@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)
Okay, I think I've discovered where the problem lies. As I indicated in the original email, the network-bridge script did not work for me so I disabled it and rolled my own solution which consisted of completely ignoring veth0/vif0.0 and just assigning an address to a bridge and using it directly in dom0. I am assuming that this bypasses some xen checksum trickery and caused my problems. Is this correct?

My working dom0 networking setup is listed below. Note that I am still using the standard vif-bridge script.


/etc/conf.d/net (gentoo linux)

# bridge settings
bridge_br0="eth0 vif0.0"
config_br0=( "null" ) #disable dhcp

# physical adapter will be a dumb port on our bridge
config_eth0=( "null" )

# dom0 backend interface will also be a dumb port on our bridge
config_vif0_0=( "null" ) #note that we have to say vif0_0 instead of vif0.0

# dom0 frontend config
routes_veth0=("default via")

Xen-users mailing list