Technical data

89
Server Request Hierarchy
When handling a request from a remote router (to which the local router has NAT enabled), the local
router selects a server based on the following priority (order) algorithm:
1.
remote addserver
— The local router selects a server for the remote router that handles that
particular protocol/port.
2.
system addserver
— The local router selects a global server that handles that particular protocol/
port.
3.
remote addserver
with
port
0 — The local router selects a server for the remote router that handles
that particular protocol (such as tcp/udp) and ANY port.
4.
system addserver
with
port
0 — The local router selects a global server that handles that particular
protocol and ANY port.
5. If an IP address is used for true NAT host remapping as well as for IP address/port translation, the IP
address of the local remapped host as the server is selected.
6. Router’s
IP address
— The local router selects itself (the local router) as the server.
Classic NAT (one NAT IP address assigned per one PC IP address)
With classic NAT, one PC IP address is translated to one NAT IP address. This NAT technique is primarily used
to make certain hosts on a private LAN globally visible and give them the ability to remap these IP addresses as
well.
Client Configuration
Classic NAT requires that you first enable NAT Masquerading as described in the previous section; thus, for
the Classic and Masquerading forms of NAT, the clients are configured in the same way. Please, refer to the
Client Configuration section, page 86
.
Host Remapping
Remote Commands
Use these commands to enable or disable host remapping on a-per-remote basis:
remote addHostMapping <
first private addr
> <
second private addr
> <
first public addr
>
<
remoteName
>
remote delHostMapping <
first private addr
> <
second private addr>
<
first public addr
>
<
remoteName
>
Use
remote addHostMapping
when a host on the local LAN is known by different IP addresses to
different remotes.