5 - 149
The
NAT Pool
tab displays by default. The NAT Pool tab lists those NAT policies created thus far. Any of these policies can
be selected and applied to the access point profile.
5. Select
Add
to create a new NAT policy that can be applied to a profile. Select
Edit
to modify the attributes of a existing
policy or select
Delete
to remove obsolete NAT policies from the list of those available to a profile.
Figure 5-96
Profile Security - NAT Pool tab - NAT Pool field
6. If adding a new NAT policy or editing the configuration of an existing policy, define the following parameters:
7. Select the
+ Add Row
button to append additional rows to the
IP Address Range
table.
8. Select
OK
to save the changes made to the profile’s NAT Pool configuration. Select
Reset
to revert to the last saved
configuration.
9. Select the
Static NAT
tab. The
Source
tab displays by default.
The
Source
tab displays by default and lists existing static NAT configurations. Existing static NAT configurations are not
editable, but new configurations can be added or existing ones deleted as they become obsolete.
Static NAT creates a permanent, one-to-one mapping between an address on an internal network and a perimeter or
external network. To share a Web server on a perimeter interface with the Internet, use static address translation to map
the actual address to a registered IP address. Static address translation hides the actual address of the server from users
on insecure interfaces. Casual access by unauthorized users becomes much more difficult. Static NAT requires a dedicated
address on the outside network for each host.
Name
If adding a new NAT policy, provide a name to help distinguish it from others with similar
configurations. The length cannot exceed 64 characters.
IP Address Range
Define a range of IP addresses that are hidden from the public Internet. NAT modifies network
address information in the defined IP range while in transit across a traffic routing device. NAT
only provides IP address translation and does not provide a firewall. A branch deployment with
NAT by itself will not block traffic from being potentially routed through a NAT device.
Consequently, NAT should be deployed with a stateful firewall.
Summary of Contents for WiNG 5.7.1
Page 1: ...WiNG 5 7 1 ACCESS POINT SYSTEM REFERENCE GUIDE ...
Page 2: ......
Page 3: ...WING 5 7 1 ACCESS POINT SYSTEM REFERENCE GUIDE MN001977A01 Revision A April 2015 ...
Page 4: ...ii WiNG 5 7 1 Access Point System Reference Guide ...
Page 24: ...1 4 WiNG 5 7 1 Access Point System Reference Guide ...
Page 36: ...2 12 WiNG 5 7 1 Access Point System Reference Guide ...
Page 72: ...3 36 WiNG 5 7 1 Access Point System Reference Guide ...
Page 470: ...5 386 WiNG 5 7 1 Access Point System Reference Guide ...
Page 472: ...6 2 WiNG 5 7 1 Access Point System Reference Guide Figure 6 1 Configuration Wireless menu ...
Page 624: ...7 46 WiNG 5 7 1 Access Point System Reference Guide ...
Page 724: ...9 56 WiNG 5 7 1 Access Point System Reference Guide ...
Page 783: ...12 35 Figure 12 46 Device Summary screen 4 Click File Management ...
Page 816: ...12 68 WiNG 5 7 1 Access Point System Reference Guide ...
Page 1006: ...13 190 WiNG 5 7 1 Access Point System Reference Guide ...
Page 1026: ...14 20 WiNG 5 7 1 Access Point System Reference Guide ...
Page 1028: ...A 2 WiNG 5 7 1 Access Point System Reference Guide ...
Page 1089: ......
Page 1090: ...MN001977A01 Revision A April 2015 ...