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

Add some information about server config

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3212 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-01-02 23:14:50 +00:00
parent df5f12e53b
commit 6c455428f9
1 changed files with 23 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
Shorewall-docs2/myfiles.xml
View File

@ -15,10 +15,10 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2005-12-31</pubdate> <pubdate>2006-01-02</pubdate>
<copyright> <copyright>
<year>2001-2005</year> <year>2001-2006</year>
<holder>Thomas M. Eastep</holder> <holder>Thomas M. Eastep</holder>
</copyright> </copyright>
@ -87,11 +87,10 @@
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>use SNAT through 206.124.146.179 for&nbsp;my Wife's Windows XP <para>use SNAT through 206.124.146.179 for&nbsp;my Wife's Windows XP
system <quote><emphasis>Tarry</emphasis></quote>, our SUSE 10.0 laptop system <quote><emphasis>Tarry</emphasis></quote> and our SUSE 10.0
<quote><emphasis>Tipper</emphasis></quote> which connects through the laptop <quote><emphasis>Tipper</emphasis></quote> which connects
Wireless Access Point (wap) via a Wireless Bridge (wet), and my work through the Wireless Access Point (wap) via a Wireless Bridge
laptop (<emphasis>eastepnc6000</emphasis>) when it is not docked in my (wet).<note>
office.<note>
<para>While the distance between the WAP and where I usually use <para>While the distance between the WAP and where I usually use
the laptop isn't very far (50 feet or so), using a WAC11 (CardBus the laptop isn't very far (50 feet or so), using a WAC11 (CardBus
wireless card) has proved very unsatisfactory (lots of lost wireless card) has proved very unsatisfactory (lots of lost
@ -161,6 +160,23 @@
<para>Ursa's Shorewall configuration is described in <ulink <para>Ursa's Shorewall configuration is described in <ulink
url="Xen.html">the article about Xen and Shorewall</ulink>.</para> url="Xen.html">the article about Xen and Shorewall</ulink>.</para>
<para>About the only thing that is unique about the configuration of
Domain 1 (lists) is that its (virtualized) eth0 has two addresses:</para>
<itemizedlist>
<listitem>
<para>192.168.1.7/24</para>
</listitem>
<listitem>
<para>206.124.146.177/32</para>
</listitem>
</itemizedlist>
<para>This prevents the DNS server from getting confused due to the fact
that the two different views have a different IP addresses for the primary
name server for the domain shorewall.net.</para>
</section> </section>
<section> <section>