From 6c455428f91d1ab7b1345b815fd9a6f7beca2c2b Mon Sep 17 00:00:00 2001 From: teastep Date: Mon, 2 Jan 2006 23:14:50 +0000 Subject: [PATCH] Add some information about server config git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3212 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs2/myfiles.xml | 30 +++++++++++++++++++++++------- 1 file changed, 23 insertions(+), 7 deletions(-) diff --git a/Shorewall-docs2/myfiles.xml b/Shorewall-docs2/myfiles.xml index 182e08084..d7a65f309 100644 --- a/Shorewall-docs2/myfiles.xml +++ b/Shorewall-docs2/myfiles.xml @@ -15,10 +15,10 @@ - 2005-12-31 + 2006-01-02 - 2001-2005 + 2001-2006 Thomas M. Eastep @@ -87,11 +87,10 @@ use SNAT through 206.124.146.179 for my Wife's Windows XP - system Tarry, our SUSE 10.0 laptop - Tipper which connects through the - Wireless Access Point (wap) via a Wireless Bridge (wet), and my work - laptop (eastepnc6000) when it is not docked in my - office. + system Tarry and our SUSE 10.0 + laptop Tipper which connects + through the Wireless Access Point (wap) via a Wireless Bridge + (wet). 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 wireless card) has proved very unsatisfactory (lots of lost @@ -161,6 +160,23 @@ Ursa's Shorewall configuration is described in the article about Xen and Shorewall. + + About the only thing that is unique about the configuration of + Domain 1 (lists) is that its (virtualized) eth0 has two addresses: + + + + 192.168.1.7/24 + + + + 206.124.146.177/32 + + + + 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.