BelAir100SN User Guide
Network Address Translation
May 31, 2010
Confidential
Document Number BDTM11001-A01 Released
Choosing an
Egress Interface
/protocol/nat/set egress {eth-1-1|cm-9-1}
This command applies to the DRU only.
The DRU has two interfaces that can act as an egress point for NAT: the
ethernet interface and the cable modem interface. This command lets you
define which interface to use.
Preventing Node
Management from
within the Scope
/protocol/nat/set scope <index (1-8)>
management {enabled | disabled}
This command lets you control whether clients within a particular scope can
access the BelAir100SN’s management interface. The default setting is
disabled
,
meaning that the nodes within that scope cannot access the management
interface of the BelAir100SN providing NAT.
Enabling or
Disabling
Individual Scopes
/protocol/nat/set scope <index (1-8)>
status {enabled | disabled}
This command lets you enable or disable individual NAT scopes. The default
setting is
disabled
.
Configuring an
HTTP Portal
Traffic is directed to required scope and portal based on its VLAN ID. See
“Configuring Network Address Translation” on page 147
.
To configure an HTTP portal:
1 Make sure your radio SSIDs are configured properly. See
for details.
2 Make sure DHCP is configured properly. See
for details.
3 Specify the required portal parameters. See
.
4 Enable the portal. See
“Enabling or Disabling the HTTP Portal” on page 149
Customizing
Scope
Configuration
/protocol/nat/show config scope <index 1-8)>
/protocol/nat/export scope <index 1-8)> host <hostname>
remotefile <filename>
[{tftp | ftp [user <username> password <password>]}]
/protocol/nat/import scope <index 1-8)> host <hostname>
remotefile <filename>
[{tftp | ftp [user <username> password <password>]}]