Changes between Version 2 and Version 3 of Concepts
- Timestamp:
- 09/13/07 00:36:37 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Concepts
v2 v3 13 13 A zone is a container for networks and a network is a container for hosts. With groups you may group hosts together (within one network). And a host is — of course — a single machine in a network. For now lets consider this simple example: 14 14 15 image 15 [[Image(Simple_Network_with_Server.png)]] 16 16 17 17 You can think of zone as a possibility to group networks and hosts of equal security level together. For example you may define two zones: 'int' and 'ext' to distinguish the internal part of you network from the external one. It becomes inherently clear that those two zones mean different levels of access. … … 21 21 For the sake of simplicity we will refer to zones with red colour and to networks with orange. Vuurmuur shows your network in the following way: network.zone: In our example we have lan.int and inet.ext. For the definition of a network in Vuurmuur you have to add network address, netmask and at least one interface via which the network can be reached. Then there are hosts: Imagine — as in our example — there is a special host in the internal network that should be reachable from the internet. 22 22 23 image 23 [[Image(Simple_Network_with_Server_and_zones_and_networks_and_host.png)]] 24 24 25 25 To refer to the host in the example above we may use server.lan.int. This is how network elements will show up when creating rules. The same applies for zones, networks and groups.