Technical data

86
Client Configuration
Enable NAT
To enable NAT, use the commands:
remote setIpTranslate on <
remoteName
>
save
The
save
command makes the above changes persistent across boots which turn NAT on when connected
to this remote router.
Obtain an IP Address for NAT Translation
The IP address (the IP address “known” by the remote ISP) used for this type of NAT translation can be
assigned in two ways.
The ISP dynamically assigns the IP address. Use the commands:
remote setSrcIpAddr
0.0.0.0 0.0.0.0 <
remoteName
>
save
The IP address is assigned locally. Use the commands:
remote setSrcIpAddr
ww.xx.yy.zz
255.255.255.255 <
remoteName
>
save
Note:
ww.xx.yy.zz
is the IP address the user on the local LAN is assigning.
Server Configuration
This section is intended for users and network administrators who wish to allow WAN access to a Web
server, FTP server, SMTP server, etc., on their local LAN, while using NAT.
NAT needs a way to identify which local PC (local IP address(es)) should receive these server requests.
The servers can be configured on a per-remote-router
basis as well as globally.
Remote Commands
The following two commands are used to enable/disable a local IP address (on your LAN) as the server
for a particular protocol for the remote router
<remoteName
>.
remote addServer
<
ipaddr
> |discard|me <
protocolid
> tcp|udp <
first port
> ftp|telnet|smtp|snmp|http
[<
last port
>[<
first private port
>]] <
remoteNam
e>
remote delServer
<
ipadd
r> |discard|me <
protocolid
> tcp|udp <
first port
> ftp|telnet|smtp|snmp|http
[<
last port
>[<
first private port
>]] <
remoteName
>
first port:
it is the first or only port as seen by the remote end.
last port:
if specified, it is used with <first port> to specify a range of ports as seen by the remote end for
the server on your LAN.