NAT64 policy
Use NAT64 policies to perform network address translation (NAT) between an internal IPv6 network and an external IPv4 network. The NAT64 Policy tab allows you to create, edit, delete, and clone NAT64 policies.
- Select the ADOM from the drop-down list in the toolbar.
- Select the policy package where you are creating the new NAT64 policy from the tree menu.
- Select NAT64 Policy in the policy toolbar.
- Right-click on the sequence number of a current policy, or in an empty area of the content pane and select Create New from the menu. The Create New Policy dialog box opens.
NAT64 policy
- Configure the following settings:
| Source Interface | Select the source interface from the drop-down list. |
| Source Address | Select the source address from the drop-down list. You can select to create a new address or address group in the Source Address dialog box. |
| Destination Interface | Select the destination interface from the drop-down list. |
| Destination Address | Select the destination address from the drop-down list. You can create a new address or address group in the Add Destination Address dialog box. |
| Schedule | Select a schedule or schedules for the policy. Schedules can also be created by selecting Create New in the dialog box. See Create a new object for more information. |
| Service | Select the service from the drop-down list. You can create a new service or service group in the Add Service dialog box. |
| Action | Select an action for the policy to take, whether ACCEPT or DENY. When Action is set to Accept, you can configure NAT and Traffic Shaping. |
| Log Allowed Traffic Log Violation Traffic | Select to log allowed traffic/violation traffic.
This setting is dependent on the Action setting. |
| NAT | NAT is enabled by default for this policy type. |
| Use Destination Interface Access | Select to use the destination interface address. |
| Fixed Port | Select to enable fixed port. |
| Dynamic IP Pool | Select to enable dynamic IP pool and select the dynamic IP pool from the dropdown list. |
| Traffic Shaping | Select to enable traffic shaping and select a default or custom traffic shaper object from the drop-down list. |
| Reverse Direction Traffic Shaping | Select to enable reverse direction traffic shaping and select a default or custom traffic shaper object from the drop-down list. |
| Per-IP Traffic Shaping | Select to enable per-IP traffic shaping and select the related object from the drop-down list. |
| Tags | You can add tags for tag management. Type a tag in the text field and select the add icon to apply the tag to the policy. |
| Comments | Type optional comments for the policy. |
- Select OK to save the policy.
Question about ADOMs. In previous versions of FortiOS 4.3 maybe earlier. When you had multiple devices under an ADOM the policies and objects were clearly separated per device being managed. With the newer FortiOS it seems as though there is overlapping and my policies and objects seem to be cross contaminated between devices. What is your perspective on this and/or work around? Thank you in advance – Richard
I always keep my devices separated by Firmware version. ADOM 4.3 ADOM 5.2 ADOM 5.4 etc to keep things nice and neat.
I have an issue for deleting the V4.2 ADOMs from FMG V5.2 getting the below error.
Some ADOM(s) were not deleted successfully because they are not empty
But those ADOMs are not used anywhere. How to find out where it is used?
No admin accounts having access to the ADOM, No policy package for the ADOM.
Usually, it experiences this issue because something somewhere is still referencing it. Whether that item be a policy package as you mentioned before or a group etc.
Is there any possibilities to find out the references for that ADOM on the FMG.
Hi Mike,
We use fortimanager v5.4.1-build1082 160629 (GA) FMG-VM64 but we cant drag and drop within the rule base. (drag en drop from the object side plain does work) I have seen a instruction video were they lock the adom but also that future is non exsistent in our GUI.
You have any idea what this could be ? I did not see any issues on this subject on the fortinet site. We have upgraded from a older version FM.
kind regards and thanks for this great support site, i look here first!
Did you follow the supported upgrade path when you moved your FortiManager up through the code?
Not sure ( I was not involved and there is no change history) but i did found this in the “alert message console”
Upgrade image from v5.2.7-build0757-160408(GA) to v5.4.1-build1082-160629
Hello,
HELP !! we have multiple firewalls we would like to upload on our Fortimanager in the same ADOM.
The problem is that some objects have the same names but different IPs adresses. i read that the only solution is mapping the objects. if we do so we will have to it manually on every object (more than ~200) which is not an option for me. Can you please help me with this problem ?