Specifications

96 Chapter 4. Configuring Special Features
¥ Multiple-Host Remapping Entries
Users may enter as many host remapping entries as they wish.
Example:
remote addHostMapping 192.168.207.40 192.168.207.49 10.0.20.11 remote1
remote addHostMapping 192.168.207.93 192.168.207.99 10.0.20.4 remote1
remote addHostMapping 192.168.209.71 192.168.209.80 10.12.14.16 remote1
The above entries create three mappings:
192.168.207.40 through 192.168.207.49 are mapped to 10.0.20.11 through 10.0.20.20
192.168.207.93 through 192.168.207.99 are mapped to 10.0.20.4 through 10.0.20.10
192.168.209.71 through 192.168.209.80 are mapped to 10.12.14.16 through 10.12.14.25
¥ Range Overlap Rules
¥ The per-interface commands, remote addHostMapping and eth ip addHostMapping have these
range overlap rules:
Private IP address ranges cannot overlap for an interface.
Public IP address ranges cannot overlap for an interface.
¥ The global command, system addHostMapping, has these range overlap rules:
Private IP address ranges cannot overlap for a system.
Public IP address ranges cannot overlap for a system.
¥ If a private IP address range for an interface and a private IP address range for the system overlap,
the private IP address range for the interface has precedence.
¥ If a public IP address range for an interface and the public IP address range for the system overlap,
the public IP address range for the interface has precedence.
¥ Private IP addresses and public IP addresses can be the same.
For example, to enable IP/port translation to a remote router and make the IP addresses 10.1.1.7 through
10.1.1.10 globally visible, it is permissible to use either one of the following commands:
remote addHostMapping 10.1.1.7 10.1.1.10 10.1.1.7 remoteName
system addHostMapping 10.1.1.7 10.1.1.10 10.1.1.7
If the remapped hostÕs IP address (classic NAT, one-to-one IP address translation) and the masquerading
IP address (many-to-one IP address translation) are the same, then NAT masquerading has precedence
over classic NAT.