From 6231b26d62c5d04bd58c68e21f2eab7ffccb5839 Mon Sep 17 00:00:00 2001 From: teastep Date: Thu, 27 Apr 2006 15:28:30 +0000 Subject: [PATCH] Add 'ethtool' tip to XenMyWay document -- take 2 git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3819 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- docs/XenMyWay.xml | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/docs/XenMyWay.xml b/docs/XenMyWay.xml index 7037fb6d4..e51293192 100644 --- a/docs/XenMyWay.xml +++ b/docs/XenMyWay.xml @@ -259,19 +259,6 @@ hostname = name # storage devices: disk = [ 'phy:hda3,hda3,w' ] - - Under some circumstances, UDP and/or TCP communication from a - domU won't work for no obvious reason. That happend with the 'lists' - domain in my setup. Looking at the IP traffic with tcpdump - -nvvi eth1 in the firewall domU showed that UDP packets - from the lists domU had incorrect checksums. That problem was - corrected by arranging for the following command to be executed in - the 'lists' domain when its eth0 device was brought up: - - ethtool -K eth0 tx off - - /etc/xen/auto/03-wireless — configuration file for the wireless domain. @@ -310,6 +297,21 @@ disk = [ 'phy:hdb4,hdb4,w' ] The zones correspond to the Shorewall zones in the Dom0 configuration. + + Under some circumstances, UDP and/or TCP communication from a + domU won't work for no obvious reason. That happened with the + lists domain in my setup. Looking at + the IP traffic with tcpdump -nvvi eth1 in the + firewall domU showed that UDP packets + from the lists domU had incorrect + checksums. That problem was corrected by arranging for the following + command to be executed in the lists + domain when its eth0 device + was brought up: + + ethtool -K eth0 tx off + + SuSE 10.0 includes Xen 3.0 which does not support PCI delegation PCI delegation was a feature of Xen 2.0 but that capability