Configuring NAT
to a corresponding address in a range of global addresses (which you specify in the next step).
7.In the “Global Address From/To:” fields, type the starting and ending IP address that identify the pool of public IP addresses to be translated to your private IP addresses. Or, type the same IP address in both fields (if you also specified a single address in the previous step).
8.Enter a “Destination Address From/To:” ….
9.Enter a starting and ending port number in the “Destination Port From/To:” fields if incoming traffic destined for these port types should be redirected to the address(es) ….
10.When you have completed entering all information, click the Submit button. A page appears to confirm the changes.
11.Click Close to return to the NAT Configuration page. The new rule should no be displayed in the NAT Rule table.
12.On the NAT Configuration page, ensure that the Enable radio button is selected and then click the Submit button. A page appears to confirm your changes.
13.Select Admin > Commit & Reboot and click the Commit button to save your changes to permanent storage.
8.5.5The BIMAP Rule
Unlike the other NAT flavors, the BIMAP flavor performs address translation in both the outgoing and incoming directions.
In the incoming direction, when the specified interface receives a packet destined to your public IP address, this address is translated to the private IP address of a computer on your LAN.
In the outgoing direction, the private source IP address in a data packet is translated to the LAN’s public IP address.
BIMAP rules can be used to provide external access to a LAN device. They do not provide the same level of security as RDR rules, because RDR rules also reroute incoming packets based on the port ID. BIMAP rules do not account for the port number, and therefore allow external access regardless of the destination port type specified in the incoming packet.
To create a BIMAP rule, proceed as follows:
66 | EN/LZT 108 6492 R2 - October 2003 |
