Add 'ethtool' tip to XenMyWay document

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3818 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb

docs/MultiISP.xml

@@ -15,7 +15,7 @@
       </author>
     </authorgroup>
 
-    <pubdate>2006-04-02</pubdate>
+    <pubdate>2006-04-24</pubdate>
 
     <copyright>
       <year>2005</year>
@@ -42,8 +42,8 @@
     this setup, older distributions do not meet the minimum requirements,and
     you will need to recompile iptables, kernel and other software on your
     system. If you don't follow this advice,<emphasis role="bold">we will
-    <emphasis role="bold">not</emphasis> be able to help you</emphasis>.
+    <emphasis role="bold">not</emphasis> be able to help
-    </para>
+    you</emphasis>.</para>
   </warning>
 
   <section>
@@ -530,7 +530,7 @@ eth1             eth2              130.252.99.27</programlisting>
       <warning>
         <para>Entries in <filename>/etc/shorewall/masq</filename> have no
         effect on which ISP a particular connection will be sent through. That
-        is rather the purpuse of entries in
+        is rather the purpose of entries in
         <filename>/etc/shorewall/tcrules</filename>.</para>
       </warning>
 

docs/Xen.xml

@@ -66,9 +66,9 @@
         <command>xend </command>and assumes that the host system has a single
         ethernet interface named <filename
         class="devicefile">eth0</filename>.</para>
-      </footnote> in each domain. In Dom0, Xen also creates a bridge
+      </footnote>in each domain. In Dom0, Xen also creates a bridge (<filename
-    (<filename class="devicefile">xenbr0</filename>) and a number of virtual
+    class="devicefile">xenbr0</filename>) and a number of virtual interfaces
-    interfaces as shown in the following diagram.</para>
+    as shown in the following diagram.</para>
 
     <graphic align="center" fileref="images/Xen1.png" />
 

docs/XenMyWay.xml

@@ -15,7 +15,7 @@
       </author>
     </authorgroup>
 
-    <pubdate>2006-04-15</pubdate>
+    <pubdate>2006-04-27</pubdate>
 
     <copyright>
       <year>2006</year>
@@ -259,6 +259,19 @@ hostname = name
 # storage devices:
 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
         domain.</para>
 

docs/useful_links.xml

@@ -13,7 +13,7 @@
       <surname>Eastep</surname>
     </author>
 
-    <pubdate>2006-02-23</pubdate>
+    <pubdate>2006-04-20</pubdate>
 
     <copyright>
       <year>2003-2006</year>
@@ -83,7 +83,12 @@
 
         <row rowsep="0" valign="middle">
           <entry>Tom's 2005 LinuxFest NW Presentation: <ulink
-          url="http://www.shorewall.net/LinuxFest.pdf">http://www.shorewall.net/LinuxFest.pdf</ulink></entry>
+          url="http://www.shorewall.net/LinuxFest2005.pdf">http://www.shorewall.net/LinuxFest2005.pdf</ulink></entry>
+        </row>
+
+        <row>
+          <entry>Tom's 2006 LinuxFest NW Presentation: <ulink
+          url="http://www.shorewall.net/LinuxFest2006.pdf">http://www.shorewall.net/LinuxFest2006.pdf</ulink></entry>
         </row>
       </tbody>
     </tgroup>