mirror of
https://gitlab.com/shorewall/code.git
synced 2025-01-18 11:38:14 +01:00
Add third laptop to description of our network
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@7972 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
d5073f0b3f
commit
4b5a77dd67
@ -186,7 +186,8 @@
|
|||||||
class="directory">/etc/xen/auto</filename> shown below correspond to
|
class="directory">/etc/xen/auto</filename> shown below correspond to
|
||||||
my configuration under Xen 3.0. I'm now running Xen 3.1 which does
|
my configuration under Xen 3.0. I'm now running Xen 3.1 which does
|
||||||
not use configuration files for the domains but rather keeps the
|
not use configuration files for the domains but rather keeps the
|
||||||
configuration in a database managed by xend.</para>
|
configuration in a database managed by xend. See <link
|
||||||
|
linkend="Xen3.1">below</link>.</para>
|
||||||
</important></para>
|
</important></para>
|
||||||
|
|
||||||
<blockquote>
|
<blockquote>
|
||||||
@ -309,8 +310,8 @@ bootentry = 'hda2:/boot/vmlinuz-xen,/boot/initrd-xen'
|
|||||||
</blockquote></para>
|
</blockquote></para>
|
||||||
</blockquote>
|
</blockquote>
|
||||||
|
|
||||||
<para>Instructions for editing entries in the Xen 3.1 xend database may
|
<para id="Xen3.1">Instructions for editing entries in the Xen 3.1 xend
|
||||||
be found at <ulink
|
database may be found at <ulink
|
||||||
url="http://www.novell.com/documentation/vmserver/config_options/index.html?page=/documentation/vmserver/config_options/data/b8uh3zr.html">http://www.novell.com/documentation/vmserver/config_options/index.html?page=/documentation/vmserver/config_options/data/b8uh3zr.html</ulink>,
|
url="http://www.novell.com/documentation/vmserver/config_options/index.html?page=/documentation/vmserver/config_options/data/b8uh3zr.html">http://www.novell.com/documentation/vmserver/config_options/index.html?page=/documentation/vmserver/config_options/data/b8uh3zr.html</ulink>,
|
||||||
The following are excerpts from the XML representations of the two user
|
The following are excerpts from the XML representations of the two user
|
||||||
domains (produced by "xm list -l …").</para>
|
domains (produced by "xm list -l …").</para>
|
||||||
@ -433,16 +434,16 @@ bootentry = 'hda2:/boot/vmlinuz-xen,/boot/initrd-xen'
|
|||||||
url="shorewall_setup_guide.htm">Shorewall Setup Guide</ulink> with the
|
url="shorewall_setup_guide.htm">Shorewall Setup Guide</ulink> with the
|
||||||
exception that I've added a fourth interface for our wireless network.
|
exception that I've added a fourth interface for our wireless network.
|
||||||
The firewall runs a routed <ulink url="OPENVPN.html">OpenVPN
|
The firewall runs a routed <ulink url="OPENVPN.html">OpenVPN
|
||||||
server</ulink> to provide roadwarrior access for our two laptops and a
|
server</ulink> to provide roadwarrior access for our three laptops and a
|
||||||
bridged OpenVPN server for the wireless network in our home. Here is the
|
bridged OpenVPN server for the wireless network in our home. Here is the
|
||||||
firewall's view of the network:</para>
|
firewall's view of the network:</para>
|
||||||
|
|
||||||
<graphic align="center" fileref="images/network4a.png" />
|
<graphic align="center" fileref="images/network4a.png" />
|
||||||
|
|
||||||
<para>The two laptops can be directly attached to the LAN as shown above
|
<para>The three laptops can be directly attached to the LAN as shown
|
||||||
or they can be attached wirelessly -- their IP addresses are the same in
|
above or they can be attached wirelessly -- their IP addresses are the
|
||||||
either case; when they are directly attached, the IP address is assigned
|
same in either case; when they are directly attached, the IP address is
|
||||||
by the DHCP server running in Dom0 and when they are attached
|
assigned by the DHCP server running in Dom0 and when they are attached
|
||||||
wirelessly, the IP address is assigned by OpenVPN.</para>
|
wirelessly, the IP address is assigned by OpenVPN.</para>
|
||||||
|
|
||||||
<para>The Shorewall configuration files are shown below. All routing and
|
<para>The Shorewall configuration files are shown below. All routing and
|
||||||
|
Binary file not shown.
Binary file not shown.
Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 66 KiB |
Loading…
Reference in New Issue
Block a user