User's Manual

BelAirOS User Guide Network Address Translation
April 22, 2012 Confidential Page 199 of 362
Document Number BDTM00000-A02 Draft
Preventing AP
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 AP’s management interface. The default setting is disabled , meaning
that the APs within that scope cannot access the management interface of the
AP 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 .
Changing NAT
Admin State
/protocol/nat/set admin-state {enabled | disabled}
This command lets you enable or disable NAT functionality. The default setting
is disabled .
When you enable or disable NAT functionality, you must:
1 Issue the config-save command. See “Saving your Changes” on page 37 for
details.
2 Reboot the AP. See “Activating a Software Load” on page 250 for details.
Managing APs in a
NAT Cluster
This section describes functions that you can use to manage APs that are part
of a NAT cluster.
In a NAT cluster, one AP serves as an egress point to several other APs. The
egress AP uses NAT to provide IP addresses to the APs that are cluster
members.
In such a configuration, the cluster members are normally hidden from network
management behind the egress AP. To help manage the cluster members, you
can use the egress AP functions described in the following sections:
• “Mac Address to IP Address Mapping” on page 199
• “Port Forwarding” on page 200
Mac Address to IP
Address Mapping
/protocol/nat/add scope <index (1-8)>
mac-static <MAC_addr> ip <IP_addr)
/protocol/nat/del scope <index (1-8)>
mac-static <MAC_addr> ip <IP_addr)
These commands let you specify which IP address to provide to specific cluster
members based on their MAC address.