>
    Strata Copilot
    Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
    Focus
    Download PDF
    Focus
    1. Home
    2. Next-Generation Firewall
    3. NAT
    4. Configure NAT
    5. Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
    Download PDF
    Next-Generation Firewall

    Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)

    Table of Contents

    Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)

    Configure source DIPP NAT to translate internal client IP addresses to your public IP address.
    Where Can I Use This?What Do I Need?
    • NGFW (Managed by PAN-OS or Panorama)
    When a client on your internal network sends a request, the source address in the packet contains the IP address for the client on your internal network. If you use private IP address ranges internally, the packets from the client will not be able to be routed on the internet unless you translate the source IP address in the packets leaving the network into a publicly routable address.
    On the firewall you can do this by configuring a source NAT policy that translates the source address (and optionally the port) into a public address. One way to do this is to translate the source address for all packets to the egress interface on your firewall, as shown in the following procedure.
    On the PA-7500 Series running PAN-OS 12.1.8 and later, a single DIPP NAT policy rule supports a translated address pool of up to 32,768 IP addresses (/17 subnet), enabling you to consolidate what would otherwise require up to 128 separate NAT rules into a single policy. This expanded per-policy capacity takes effect automatically after upgrade and requires no additional configuration. The system-wide maximum for DIPP NAT translated IP addresses on the PA-7500 is also 32,768. If you later downgrade from PAN-OS 12.1.8, the downgrade is blocked when any single DIPP NAT policy rule contains more than 256 translated IP addresses, and the following message is displayed:
    Downgrading from PAN-OS 12.1.8 is not allowed if a DIPP NAT policy has a number of translated IP addresses configured that exceeds the maximum capacity of 256 translated IP addresses per DIPP NAT policy. Reduce the number of DIPP NAT IP addresses in the policy, commit, and then retry the downgrade.
    This task covers regular DIPP, and this task also includes the step to enable persistent NAT for DIPP in PAN-OS 11.1.0 and earlier releases. To enable persistent NAT for DIPP in PAN-OS 11.1.1 and later releases, 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 do not 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, select Dynamic IP And Port from the Translation Type list in the Source Address Translation section of the screen.
      7. For Address Type, there are two choices. You could select Translated Address and then click Add. Select the address object you just created.
        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.
      Click Commit.
    4. (PAN-OS 11.1.0 and earlier releases) Enable persistent NAT for DIPP. (Skip this step for regular DIPP.)
      1. Access the CLI.
      2. >set system setting persistent-dipp enable yes
      3. >request restart system
      4. If you have HA configured, repeat this step on the other HA peer.
    5. (Optional) Verify the translation.
      1. Use the show session all command to view the session table, where you can verify the source IP address and port and the corresponding translated IP address and port.
      2. Use the show session id <id_number> to view more details about a session.
      3. If you configured Dynamic IP NAT, use the show counter global filter aspect session severity drop | match nat command to see if any sessions failed due to NAT IP allocation. If all of the addresses in the Dynamic IP NAT pool are allocated when a new connection is supposed to be translated, the packet will be dropped.

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