Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
Table of Contents
10.1
Expand all | Collapse all
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
Translate Internal Client IP Addresses to Your Public IP
Address (Source DIPP NAT)
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.
Beginning with
PAN-OS 10.1.6, you can enable persistent NAT
for DIPP to mitigate the compatibility issues that symmetric
NAT may have with applications that use STUN.
- Create an address object for the external IP address you plan to use.
- SelectandObjectsAddressesAddaNameand optionalDescriptionfor the object.
- SelectIP Netmaskfrom theTypeand then enter the IP address of the external interface on the firewall, 203.0.113.100 in this example.
- ClickOK.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.
- Create the NAT policy.
- Selectand clickPoliciesNATAdd.
- On theGeneraltab, enter a descriptiveNamefor the policy.
- (Optional) Enter a tag, which is a keyword or phrase that allows you to sort or filter policies.
- ForNAT Type, selectipv4(default).
- On theOriginal Packettab, select the zone you created for your internal network in theSource Zonesection (clickAddand then select the zone) and the zone you created for the external network from theDestination Zonelist.
- On theTranslated Packettab, selectDynamic IP And Portfrom theTranslation Typelist in the Source Address Translation section of the screen.
- ForAddress Type, there are two choices. You could selectTranslated Addressand then clickAdd. Select the address object you just created.An alternativeAddress TypeisInterface Address, in which case the translated address will be the IP address of the interface. For this choice, you would select anInterfaceand optionally anIP Addressif the interface has more than one IP address.
- ClickOK.
- Commit your changes.ClickCommit.
- (PAN-OS 10.1.6 and later 10.1 releases) Enable persistent NAT for DIPP.
- >set system setting persistent-dipp enable yes
- >request restart system
- If you have HA configured, repeat this step on the other HA peer.
- (Optional) Verify the translation.
- Use theshow session allcommand to view the session table, where you can verify the source IP address and port and the corresponding translated IP address and port.
- Use theshow session id <id_number>to view more details about a session.
- If you configured Dynamic IP NAT, use theshow counter global filter aspect session severity drop | match natcommand 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.