From e7ab1fcbe2f8599b429c31013e8e0ad3b6029fd2 Mon Sep 17 00:00:00 2001 From: mhnoyes Date: Wed, 17 Dec 2003 19:10:04 +0000 Subject: [PATCH] Content moved to Multiple_Zones.xml git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@879 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs/Multiple_Zones.html | 551 ----------------------------- 1 file changed, 551 deletions(-) delete mode 100755 Shorewall-docs/Multiple_Zones.html diff --git a/Shorewall-docs/Multiple_Zones.html b/Shorewall-docs/Multiple_Zones.html deleted file mode 100755 index 4f45281b1..000000000 --- a/Shorewall-docs/Multiple_Zones.html +++ /dev/null @@ -1,551 +0,0 @@ - - - - - Multiple Zones per Interface - - - - - -

-
-

Multiple Zones per Interface
-

-While most configurations can be handled with each of the firewall's -network interfaces assigned to a single zone, there are cases where you -will want to divide the hosts accessed through an interface between two -or more zones.
-
    -
  1. The interface has multiple addresses on multiple subnetworks. -This case is covered in the Aliased Interface -documentation.
    2. -
  2. You are using some form of NAT and want to access a server by its -external IP address from the same LAN segment. This is covered in FAQs 2 and 2a.
    -
    3. -
  3. There are routers accessible through the interface and you want -to treat the networks accessed through that router as a separate zone.
    4. -
  4. Some of the hosts accessed through an interface have -significantly different firewalling requirements from the others so you -want to assign them to a different zone.
    5. -
-The key points to keep in mind when setting up multiple zones per -interface are:
- -These examples use the local zone but -the same technique works for any zone. Remember that Shorewall -doesn't have any conceptual knowledge of "Internet", "Local", or "DMZ" -so all zones except the firewall itself ($FW) are the same as far as -Shorewall is concerned.  Also, the examples use private (RFC 1918) -addresses but public IP addresses can be used in exactly the same way.
-

Router in the Local Zone
-

-Here is an example of a router in the local zone.  Note that the box called "Router" could be a VPN -server or other such device; from the point of view of this -discussion, it makes no difference.
-
-
(Firewall connected to Internal Router)
-
-
-

-
-
-

Can You Use the Standard Configuration?
-

-In many cases, the standard two-interface -Shorewall setup will work fine in this configuration.  It will -work if:
- -All you have to do on the firewall is add a route to 192.168.2.0/24 -through the router and restart -Shorewall.
-

Will One Zone be Enough?

-If the firewalling requirements for the two local networks is the same -but the hosts in 192.168.1.0/24 don't know how to route to -192.168.2.0/24 then you need to configure the firewall slightly -differently. This type of configuration is rather stupid from an IP -networking point of view but it is sometimes necessary because you -simply don't want to have to reconfigure all of the hosts in -192.168.1.0/24 to add a persistent route to 192.168.2.0/24. On the -firewall:
- -

I Need Separate Zones

-If you need to make 192.168.2.0/24 into it's own zone, you can do it -one of two ways; Nested Zones or Parallel Zones.
-

Nested Zones:

-You can define one zone (called it 'loc') as being all hosts connectied -to eth1 and a second zone 'loc1' (192.168.2.0/24) as a sub-zone.
-
-

-
-
-The advantage of this approach is that the zone 'loc1' can use CONTINUE -policies such that if a connection request doesn't match a 'loc1' rule, -it will be matched against the 'loc' rules. For example, if your -loc1->net policy is CONTINUE then if a connection request from loc1 -to the internet doesn't match any rules for loc1->net then it will -be checked against the loc->net rules.
-
-/etc/shorewall/zones:
-
-
- - - - - - - - - - - - - - - - - - -
ZONE
- 		DISPLAY
- 		COMMENTS
-
loc1
- 		Local2
- 		Hosts access through internal -router
-
loc
- 		Local
- 		All hosts accessed via eth1
-
-
-Note that the sub-zone (loc1) is defined first!
-
-
-/etc/shorewall/interfaces
-
-
- - - - - - - - - - - - - - - -
ZONE
- 		INTERFACE
- 		BROADCAST
- 		OPTIONS
-
loc
- 		eth1
- 		192.168.1.255
- 		...
-
-
-
-/etc/shorewall/hosts
-
-
- - - - - - - - - - - - - -
ZONE
- 		HOSTS
- 		OPTIONS
-
loc1
- 		eth1:192.168.2.0/24
-
-
-
-
-If you don't need Shorewall to set up infrastructure to route traffic -between 'loc' and 'loc1', add these two policies:
-
-
- - - - - - - - - - - - - - - - - - - - - - - - -
SOURCE
- 		DEST
- 		POLICY
- 		LOG
-LEVEL
- 		RATE:BURST
-
loc
- 		loc1NONE
-
-
-
loc1
- 		loc
- 		NONE
-
-
-
-
-

Parallel Zones:

-You define both zones in the /etc/shorewall/hosts file to create two -disjoint zones.
-
-

-
-
-/etc/shorewall/zones:
-
-
- - - - - - - - - - - - - - - - - - -
ZONE
- 		DISPLAY
- 		COMMENTS
-
loc1
- 		Local1
- 		Hosts accessed Directly from -Firewall
-
loc2
- 		Local2
- 		Hosts accessed via internal -Router
-
-
-Here it doesn't matter which zone is defined first.
-
-
-/etc/shorewall/interfaces
-
-
- - - - - - - - - - - - - - - -
ZONE
- 		INTERFACE
- 		BROADCAST
- 		OPTIONS
-
-
- 		eth1
- 		192.168.1.255
- 		...
-
-
-
-/etc/shorewall/hosts
-
-
- - - - - - - - - - - - - - - - - - -
ZONE
- 		HOSTS
- 		OPTIONS
-
loc1
- 		eth1:192.168.1.0/24
-
-
loc2
- 		eth1:192.168.2.0/24
-
-
-
-
-If you don't need Shorewall to set up infrastructure to route traffic -between 'loc' and 'loc1', add these two policies:
-
-
- - - - - - - - - - - - - - - - - - - - - - - - -
SOURCE
- 		DEST
- 		POLICY
- 		LOG
-LEVEL
- 		RATE:BURST
-
loc
- 		loc1NONE
-
-
-
loc1
- 		loc
- 		NONE
-
-
-
-
-

Some Hosts have Special Firewalling Requirements

-There are cases where a subset of the addresses associated with an -interface need special handling.  Here's an example.
-
-

-
-
-In this example, addresses 192.168.1.8 - 192.168.1.15 (192.168.1.8/29) -are to be treated as their own zone (loc1).
-
-/etc/shorewall/zones:
-
-
- - - - - - - - - - - - - - - - - - -
ZONE
- 		DISPLAY
- 		COMMENTS
-
loc1
- 		Local2
- 		192.168.1.8 - 192.168.1.15
-
loc
- 		Local
- 		All hosts accessed via eth1
-
-
-Note that the sub-zone (loc1) is defined first!
-
-
-/etc/shorewall/interfaces
-
-
- - - - - - - - - - - - - - - -
ZONE
- 		INTERFACE
- 		BROADCAST
- 		OPTIONS
-
loc
- 		eth1
- 		192.168.1.255
- 		...
-
-
-
-/etc/shorewall/hosts
-
-
- - - - - - - - - - - - - -
ZONE
- 		HOSTS
- 		OPTIONS
-
loc1
- 		eth1:192.168.1.8/29
-
-
-
-
-You probably don't want Shorewall to set up infrastructure to route -traffic -between 'loc' and 'loc1' so you should add these two policies:
-

- - - - - - - - - - - - - - - - - - - - - - - - -
SOURCE
- 		DEST
- 		POLICY
- 		LOG
-LEVEL
- 		RATE:BURST
-
loc
- 		loc1NONE
-
-
-
loc1
- 		loc
- 		NONE
-
-
-
- 
-
-

Last updated 11/21/2003 - Tom Eastep

-Copyright © 2003 Thomas M. Eastep.
- -