NAT Translated Packet Tab
- Policy > NAT > Translated Packet
Select the 
to perform on the
source, and the address and/or port to which the source will be
translated.
Translated Packet
tab to determine,
for Source Address Translation, the type of translation
to perform on the
source, and the address and/or port to which the source will be
translated.You can also enable Destination Address Translation for an internal
host that needs to be accessed by a public IP address. In this case,
you define a public source address and destination address in the
Original
Packet
tab for an internal host, and in the Translated
Packet
tab you enable Destination Address
Translation
and enter the Translated Address
.
When the public address is accessed, it will be translated to the
internal (destination) address of the internal host.NAT Rule - Translated Packet Settings | Description |
|---|---|
Source Address Translation | Select the Translation Type (dynamic or
static address pool), and enter an IP address or address range (address1-address2)
that the source address is translated to ( Translated
Address ). The size of the address range is limited by
the type of address pool:
|
Bi-directional | ( Optional ) Enable bidirectional
translation if you want the firewall to create a corresponding translation
(NAT or NPTv6) in the opposite direction of the translation you
configure.If you enable bidirectional translation,
you must ensure that you have security policies in place to control
the traffic in both directions. Without such policies, the bidirectional
feature allows packets to be translated automatically in both directions. |
Destination Address Translation | Enter an IP address or range of IP addresses
and a translated port number (1-65535) to which the destination
address and port number are translated. If the Translated
Port field is blank, the destination port is not changed.
Destination translation is typically used to allow an internal server,
such as an email server, to be accessed from the public network.For
NPTv6, the prefixes configured for Destination prefix Translated
Address must be in the format xxxx:xxxx::/yy. The address
cannot have an interface identifier (host) portion defined. The
range of supported prefix lengths is /32 to /64.Translated
Port is not supported for NPTv6 because NPTv6 is strictly prefix
translation. The Port and Host address section is simply forwarded
unchanged. |
