>
    Strata Copilot
    Create a Source NAT Rule with Persistent DIPP
    Focus
    Download PDF
    Focus
    1. Home
    2. Next-Generation Firewall
    3. NAT
    4. Configure NAT
    5. Create a Source NAT Rule with Persistent DIPP
    Download PDF
    Next-Generation Firewall

    Create a Source NAT Rule with Persistent DIPP

    Table of Contents

    Create a Source NAT Rule with Persistent DIPP

    Create a source NAT rule that uses persistent Dynamic IP and Port (DIPP).
    Where Can I Use This?What Do I Need?
    • NGFW
    One of these licenses for Strata Cloud Manager managed NGFWs:
    • Strata Cloud Manager Essentials
    • Strata Cloud Manager Pro
    Beginning with PAN-OS 11.1.1 and later releases, you configure persistent DIPP in an individual NAT policy rule.
    If your firewall is already configured with the DIPP or persistent DIPP NAT policy rules, then you must reboot the firewall after adding, deleting, or modifying the DIPP or persistent DIPP NAT policy rules. If your firewall does not have these policy rules configured, then you need not reboot after adding (new) NAT policy rules.
    Persistent DIPP NAT rules operate with constrained resources and lack oversubscription capabilities. Therefore, configure these rules exclusively for persistent traffic to ensure optimal performance.
    Follow the below configuration guidelines when creating persistent DIPP NAT policy rule and port:
    1. Identify the persistent traffic.
    2. If you are not able to identify which traffic is persistence, perform the following:
      Review the traffic logs to identify well-known non-persistent services. The common non-persistent traffic includes:
      • TCP ports: 443 (HTTPS), 20-22 (FTP/SSH), 80 (HTTP), 8080 (HTTP alternate)
      • UDP ports: 443 (QUIC), 53 (DNS), and other ephemeral connections
    3. Configure two identical NAT rules as follows:
      • In the first persistent DIPP NAT policy rule, populate service with above TCP or UDP applications. Optionally, you can also create additional service objects with ObjectServices.
      • In the second persistent DIPP NAT policy rule, leave service empty to capture all other traffic.
      This approach ensures the second rule handles minimal traffic volume, since most connections utilize common application protocols covered by the first rule.
      Both the rules can either share the same translated IP address pool, or use distinct IP address ranges based on your network requirements.
    When you are using NAT for video or voice applications behind the firewall and you need to access STUN, create your policy rule using a translation type of persistent dynamic IP and port.

    PAN-OS

    For PAN-OS, create a source NAT rule that uses persistent DIPP.
    For PAN-OS, follow this procedure to create a source NAT rule with persistent DIPP.
    1. Create an address object for the external IP address you plan to use.
      1. Select ObjectsAddresses and Add a Name and optional Description for the object.
      2. Select IP Netmask from the Type and then enter the IP address of the external interface on the firewall, 203.0.113.100 in this example.
      3. Click OK.
        Although you don't have to use address objects in your policies, it is a best practice because it simplifies administration by allowing you to make updates in one place rather than having to update every policy where the address is referenced.
    2. Create the NAT policy.
      1. Select PoliciesNAT and click Add.
      2. On the General tab, enter a descriptive Name for the policy.
      3. (Optional) Enter a tag, which is a keyword or phrase that allows you to sort or filter policies.
      4. For NAT Type, select ipv4 (default).
      5. On the Original Packet tab, select the zone you created for your internal network in the Source Zone section (click Add and then select the zone) and the zone you created for the external network from the Destination Zone list.
      6. On the Translated Packet tab, for Translation Type, select Persistent Dynamic IP And Port.
      7. For Address Type, there are two choices. You could select Translated Address and then click Add. Select the address object you created or enter the translated source address.
        An alternative Address Type is Interface Address, in which case the translated address will be the IP address of the interface. For this choice, you would select an Interface and optionally an IP Address if the interface has more than one IP address.
      8. Click OK.
    3. Commit your changes.
    4. (Optional) Use operational CLI commands to view persistent DIPP information.
      1. Access the CLI.
      2. > show running persistent-dipp-pool
      3. > show running persistent-dipp-client pool <nat-pool-index>
      4. > show running persistent-dipp-client-translation ip <client-ip-address>
      Use the last two show commands at runtime to track persistent NAT resource usage by client IP address.
    5. (Optional) Use configuration CLI commands to monitor persistent DIPP pool utilization. A syslog is generated if resource utilization exceeds the threshold you configured.
      1. Access the CLI.
      2. > configure
      3. # set deviceconfig setting session persistent-dipp-alert-enable <no|yes>
      4. # set deviceconfig setting session persistent-dipp-alert-threshold <1-99>
      5. # set deviceconfig setting session persistent-dipp-alert-interval <5-120>

    Strata Cloud Manager

    In Strata Cloud Manager, create a source NAT rule with persistent DIPP.
    Strata Cloud Manager supports a source NAT rule that uses persistent DIPP.
    1. In Strata Cloud Manager, select ConfigurationNGFW and Prisma Access.
    2. Select Network PoliciesNAT
    3. Add Rule and enter a Name for the source NAT policy rule.
    4. Configure the original packet source zones and addresses, destination zone, interface, and addresses, and service.
    5. For the translated packet, select Source Address Only or Both (source address and destination address).
    6. For Translation Type, select Dynamic IP and Port.
    7. Select Persistent NAT.
    8. You can select Translated Address and then select the + to select the address object you created or enter the translated source address.
    9. Alternatively, you can select Interface Address, in which case the translated address will be the IP address of the interface. For this choice, select an Interface and an IP address if the interface has more than one IP address. Or you could select Floating IP (and select an address object).
    10. If you selected Both source and destination translation, continue by configuring the destination Translated Address and Translated Port.
    11. Save the configuration.

    © 2026 Palo Alto Networks, Inc. All rights reserved.