You are about to define here the default policy for a connection request between a client and a server zone.
For this policy to be activated, the connection must be originated by a machine from the "Client Zone" and directed to a machine belonging to the "Server Zone". Then the "Default policy" action will be taken for that connection. Optionally, if this policy has been activated, it will generate a log entry with level "Log Level".
Policy ID | The unique ID number identifying this policy rule. |
Client Zone | The zone from which the connection must be originated for the policy to activate. |
Server Zone | The zone to which the connection is targeted. |
Default policy | The action that will be taken if the policy is actually activated. See the table below for details about all possible actions. |
Log Level | If set to "-", no log message is generated when the policy is applied. Otherwise, a syslog message is generated with the indicated syslog level. See the syslog.conf man page for a description of each log level. |
Here is a short description of the four possible policies:
ACCEPT | The connection is allowed. |
DROP | The connection request is ignored. |
REJECT | The connection request is blocked and a "destination-unreachable" message is sent back to the client. |
CONTINUE | The connection is neither ACCEPTed, DROPped nor REJECTed. CONTINUE may be used when one or both of the zones named in the entry are sub-zones of or intersect with another zone. |
Example: you trust the people that are on your local network "lan" and do not wish to restrict them access to any service on the Web (zone "wan"). You do not wish to log their activity either.
Client Zone | lan |
Server Zone | wan |
Default policy | ACCEPT |
Log Level | - |