holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Clean up new XenMyWay

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3700 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-03-19 21:16:59 +00:00
parent 45b0a08fbf
commit 1708e4c1f2
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/XenMyWay.xml
View File

@ -134,8 +134,8 @@
and the firewall DomU already has three interfaces. Shorewall runs in and the firewall DomU already has three interfaces. Shorewall runs in
Dom0, in the firewall domain and in the wireless gateway..</para> Dom0, in the firewall domain and in the wireless gateway..</para>
<para>Below are the relevant configuration files for the three domains. <para>Below are the relevant configuration files for the four domains. The
The "loopback.nloopbacks=..." entries are used to restrict the number of "loopback.nloopbacks=..." entries are used to restrict the number of
"veth<emphasis>n</emphasis>" devices that the Xen kernel creates. I use "veth<emphasis>n</emphasis>" devices that the Xen kernel creates. I use
partitions on my hard drives for DomU storage devices.</para> partitions on my hard drives for DomU storage devices.</para>
@ -280,7 +280,7 @@ done</programlisting>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>Allow traffic to flow unrestricted through the three bridges. <para>Allow traffic to flow unrestricted through the four bridges.
This is done by configuring the hosts connected to each bridge as a This is done by configuring the hosts connected to each bridge as a
separate zone and relying on the implicit intra-zone ACCEPT policy to separate zone and relying on the implicit intra-zone ACCEPT policy to
permit traffic through the bridge.</para> permit traffic through the bridge.</para>