Functions
MLR 3G 2.0
In order to
select the tunnel, whose settings are to be edited
, select the de-
sired tunnel from the drop-down list "Tunnel name" and click on the button
"load to edit" then. If settings are made to the currently loaded tunnel, these
must be taken over before using the button "OK", before a new tunnel is
loaded to prevent that these settings get lost. Loading a tunnel does not save
settings that have been made!
In order to
activate the loaded tunnel
, check the checkbox "Activate tunnel".
In order to
assign a descriptive name to the loaded tunnel
, enter it into the
field "Tunnel name". This makes the assignment of messages in the log or
status view easier.
In order to
specify the remote terminal, to which the tunnel is to be estab-
lished
, enter the IP address or the domain name of the remote terminal into
the field "IP address or domain name of remote site". If no remote terminal is
specified, incoming connection requests from all remote terminals are ac-
cepted, but no connection can be initiated.
In order to
define a network behind the switch of the MLR 3G 2.0 to be tun-
nelled
, enter this network with according netmask into the field "Local sub-
net". This does not have to be the actual local subnet, but can also be behind
further gateways. In such a case it must be observed that the required routing
rules are entered correctly. If this field is not completed, the local subnet is
used automatically.
In order to
define the local subnet behind the remote terminal
, enter this
network with according netmask into the field "Remote subnet". Only data,
which is addressed to this network, is packed in ESP packets.
In order to
specify the ID of the remote terminal
, enter it into the field "Re-
mote ID". The respective IP address is used as ID by default. If the actual IP ad-
dress differs from the received ID (e.g. due to NAT routers in between) or is
unknown, the ID of the remote terminal can be specified explicitly (a self-
defined string, which must contain an "@"). When using certificates, the DN
(Distinguished Name) is used as ID by default. The domain name of the re-
mote terminal can also be used as ID, because it is resolved by a DNS lookup.
In order to
adjust the own ID
, enter it into the field "Local ID". This is only nec-
essary, if the default ID can or shall not be used.
In order to
specify the authentication mode
, select it in the drop-down list
"Authentication mode". The main mode is more secure, because all authenti-
cation data is transmitted encrypted. The aggressive mode is quicker, because
it does not use encryption and the authentication is preformed via a
passphrase.
In order to
define encryption and hash algorithms as well as the Diffie-
Hellman group for the IKE key exchange
, select these from the drop-down
lists "IKE algorithms".
In order to
define encryption and hash algorithms for the IPsec connection
, se-
lect these from the drop-down lists "IPsec algorithms".
In order to
enter the maximum number of connection attempts
, which must
be exceeded that a remote terminal is considered as not available, enter this
into the field "Maximum retries". A value of "0" means an infinite number of
attempts here.
58
