Product specifications

Chapter 4: System Management Efficient Networks

Router family

Technical Reference Guide

Page 4-28 Efficient Networks

-> system addserver <ipaddr> tcp t120

All IP addresses on the LAN can continue to connect to addresses outside the LAN,

but only the specified IP address can receive the specified TCP connections from the

outside.

Scenario 2: Interface-Specific Server Connection

Scenario 2 is the same as scenario 1, except that you want to limit the connections

from outside to a specific interface. For a remote interface, you specify the IP address

and the remote name on the following commands:

-> remote addserver <ipaddr> tcp h323 <remote>

-> remote addserver <ipaddr> tcp t120 <remote>

For a dual-Ethernet router where the connection to the WAN is through an Ethernet

interface, you would use these commands that specify the IP address and the

Ethernet interface that is connected to the WAN:

-> eth ip addserver <ipaddr> tcp h323 <interface>

-> eth ip addserver <ipaddr> tcp t120 <interface>

Scenario 3: Address Remapping

If the local LAN has more than one IP address visible from the WAN, you could map

one of those visible IP addresses to a private IP address on the LAN. The router

would then direct all connections for the “outside” IP address to the “inside” IP

address. The command to do this is:

-> system addhostmapping <private ipaddr> <privateipaddr>

The first two parameters specify the first and last addresses in the address range. To

remap just one address, you specify the same private address twice and then the

public IP address.

Address remapping can also be done for a specific interface. For a remote interface,

you would specify the addresses and the remote name on the following command:

-> remote addhostmapping <private ipaddr> <privateipaddr>

For an Ethernet interface, you would specify the addresses and the Ethernet interface

on this command:

-> eth ip addhostmapping <private ipaddr> <privateipaddr>