NAT66, NAT46, NAT64, and DNS64
NAT66, NAT46, NAT64, and DNS64 each offer their own distinct strategies and solutions to tackle the obstacles encountered during the transition from IPv4 to IPv6. This section provides a concise overview of these methods.
Method |
Overview |
---|---|
|
|
|
|
|
Note that these are broad use cases and the specific use of each type of NAT can vary depending on the network configuration and requirement.
Multiple NAT46 and NAT64 related objects are consolidated into regular objects. A per-VDOM virtual interface, naf.<vdom>, is automatically added to process NAT46 and NAT64 traffic. The features include:
-
vip46
andvip64
settings are consolidated invip
andvip6
configurations. -
policy46
andpolicy64
settings are consolidated infirewall policy
settings. -
nat46
andnat64
are included infirewall policy
settings. -
ippool
andippool6
support NAT46 and NAT64 (when enabled, the IP pool should match a subnet). -
Central SNAT supports NAT46 and NAT64.
-
add-nat46-route
inippool6
andadd-nat64-route
inippool
are enabled by default. The FortiGate generates a static route that matches the IP range inippool6
orippool
for the naf tunnel interface.
Automatic processing of the naf tunnel interface is not supported in security policies. |
To configure NAT46 or NAT64 translation, use the standard vip
or vip6
setting, apply it in a firewall policy, enable NAT46 or NAT64, and enter the IP pool to complete the configuration.
The external IP address cannot be the same as the external interface IP address. |