extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-01-18 11:38:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add 'ethtool' tip to XenMyWay document -- take 2

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3819 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-04-27 15:28:30 +00:00
parent b47c0e676a
commit 6231b26d62
1 changed files with 15 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
docs/XenMyWay.xml
View File

@ -259,19 +259,6 @@ hostname = name
# storage devices: # storage devices:
disk = [ 'phy:hda3,hda3,w' ]</programlisting> disk = [ 'phy:hda3,hda3,w' ]</programlisting>
<caution>
<para>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 <command>tcpdump
-nvvi eth1</command> 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 <filename
class="devicefile">eth0</filename> device was brought up:</para>
<para><command>ethtool -K eth0 tx off</command></para>
</caution>
<para>/etc/xen/auto/03-wireless — configuration file for the wireless <para>/etc/xen/auto/03-wireless — configuration file for the wireless
domain.</para> domain.</para>
@ -310,6 +297,21 @@ disk = [ 'phy:hdb4,hdb4,w' ]</programlisting>
<para>The zones correspond to the Shorewall zones in the Dom0 <para>The zones correspond to the Shorewall zones in the Dom0
configuration.</para> configuration.</para>
<caution>
<para>Under some circumstances, UDP and/or TCP communication from a
domU won't work for no obvious reason. That happened with the
<emphasis role="bold">lists</emphasis> domain in my setup. Looking at
the IP traffic with <command>tcpdump -nvvi eth1</command> in the
<emphasis role="bold">firewall</emphasis> domU showed that UDP packets
from the <emphasis role="bold">lists</emphasis> domU had incorrect
checksums. That problem was corrected by arranging for the following
command to be executed in the <emphasis role="bold">lists</emphasis>
domain when its <filename class="devicefile">eth0</filename> device
was brought up:</para>
<para><command>ethtool -K eth0 tx off</command></para>
</caution>
<para>SuSE 10.0 includes Xen 3.0 which does not support PCI <para>SuSE 10.0 includes Xen 3.0 which does not support PCI
delegation<footnote> delegation<footnote>
<para>PCI delegation was a feature of Xen 2.0 but that capability <para>PCI delegation was a feature of Xen 2.0 but that capability