NATing down an IPsec tunnel

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

NATing down an IPsec tunnel

L0 Member

I've got a PA-850 with fairly typical many-to-one NAT outbound to the internet, and some IPsec tunnels. Due to one partner that I'm connecting to with IPsec using 10.0.0.0/8 on their network (don't ask), I need to NAT my 10.28.1.0/24 subnet to 172.28.1.0/24 going to/from their end. I've got a working tunnel for two other subnets (a 172.19.x.x and 192.168.x.x), but I cannot get the NAT working correctly for this third subnet. I've tried several different combinations, including narrowing the NAT down to a single IP 10.28.1.28 <-> 172.28.1.28 but I don't get any hits on the NAT policy and the Traffic logs do not show any 10.28.1.28-sourced traffic pointed at the partner destination.

10.28.1.0/24 is on Trust-L3 (interface Eth1/5), and the IPsec zone is Denver-IPsec (tunnel.5).

Attached is a screenshot of two different rules that are still not working.

Can someone help with either a troubleshooting pointer or what element I'm missing?



Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.
1 accepted solution

Accepted Solutions

L6 Presenter

Hi @SteveBoyd ,

 

Attaching the traffic log may give some more clarity on the issue. You can also verify the traffic logs again and confirm what source and destination zone and routes are matching for the traffic that you are looking at.

 

For the NAT that I am seeing in the attached file, I am seeing you have configured Bi-Directional NAT. Do you have your IPSEC configured in Bi-Directional, I mean both end will act as sender as well as responder? If yes, why there is one more rule which is dynamic one?

 

Also, can you check routing configuration for  subnet 172.28.1.0/24 ? You need to make sure to point its route to the desired tunnel interface. 

Incorrect/missing routing configurations may cause matching the wrong destination zones, so please verify routing once.

 

Hope it helps!

Mayur

 

 

M

Check out my YouTube channel - https://www.youtube.com/@NetworkTalks

View solution in original post

3 REPLIES 3

L6 Presenter

Hi @SteveBoyd ,

 

Attaching the traffic log may give some more clarity on the issue. You can also verify the traffic logs again and confirm what source and destination zone and routes are matching for the traffic that you are looking at.

 

For the NAT that I am seeing in the attached file, I am seeing you have configured Bi-Directional NAT. Do you have your IPSEC configured in Bi-Directional, I mean both end will act as sender as well as responder? If yes, why there is one more rule which is dynamic one?

 

Also, can you check routing configuration for  subnet 172.28.1.0/24 ? You need to make sure to point its route to the desired tunnel interface. 

Incorrect/missing routing configurations may cause matching the wrong destination zones, so please verify routing once.

 

Hope it helps!

Mayur

 

 

M

Check out my YouTube channel - https://www.youtube.com/@NetworkTalks

L4 Transporter

Hi 

 

I agree with @SutareMayur I would definitely check routing for the NAT range. 

PCCSA PCNSA PCNSE PCSAE
Mode44 LTD Palo Alto Consultants

L0 Member

Thank you both for your help!
The reason there was two rules is I figured I'd create one for each direction. In practice, the one worked and the other didn't, and then thanks to your helpful nudge I realized that I hadn't enabled bidirectional on the one that was working. Another element was getting the security policies set as well; apparently (correct me if I'm wrong) while the NAT policies get processed before the security policies, if the NAT is working but security rules don't allow the traffic, it still won't increment the NAT or show up in the traffic logs.

I've tweaked it, disabled the nonworking NAT policy, and updated the security policies needed additional to the existing in and out policies for the IPsec tunnel. Attached are the working NAT policy and security policies for this, for the benefit of others with a similar question.

  • 1 accepted solution
  • 3433 Views
  • 3 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!