Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

PAT/NAT rule not working

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Palo Alto Networks Approved
Palo Alto Networks Approved
Community Expert Verified
Community Expert Verified

PAT/NAT rule not working

L2 Linker

Hi I am looking to create a PAT for an internal server which will use the /30 public IP of the Palo outside interface and port 16385 to be reachable. The below scenario:

 

PAT/static NAT towards the private IP of O-IntercomSRV-01 (the intercom server) using UDP port 16385 from sources OG-Parking-Intercom-Dest source port 16385.

 

O-IntercomSRV-01 - 192.168.1.9

OG-Parking-Intercom-Dest - O-Parking-Intercom-Dest-01 - O-Parking-Intercom-Dest-02 (public IPs)

 

Is this how I would set this up?

MAllen_0-1721916847976.png

MAllen_1-1721916864575.png

MAllen_2-1721916898264.png

 

MAllen_3-1721916944923.png

I am getting an error message when committing..

MAllen_4-1721917034857.png

 

 

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

the object used in the pre-NAT destination probably has a /30 subnet?  and the post-nat destination is a /32, this is a faulty NAT operation

 

also, it looks like you're setting up an inbound rule: an inbound NAT (or PAT) rule should be untrust to untrust as the destination address (pre-nat) is on the untrust interface

 

so your rule should read:

 

original packet: from untrust to untrust, source parking-OG destination public-IP service 16385

translated packet: static ip, destination 192.168.1.9

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

View solution in original post

4 REPLIES 4

L2 Linker

Can anyone advised on this, like hitting my head against a brick wall atm

Still not able to get this working..

Cyber Elite
Cyber Elite

the object used in the pre-NAT destination probably has a /30 subnet?  and the post-nat destination is a /32, this is a faulty NAT operation

 

also, it looks like you're setting up an inbound rule: an inbound NAT (or PAT) rule should be untrust to untrust as the destination address (pre-nat) is on the untrust interface

 

so your rule should read:

 

original packet: from untrust to untrust, source parking-OG destination public-IP service 16385

translated packet: static ip, destination 192.168.1.9

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization
  • 1 accepted solution
  • 1002 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!