NAT Between VR's

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

NAT Between VR's

L0 Member

Hello.

Despite my best efforts I am unable to get this concept working.

 

We have 1 x Palo Alto 3020.

It has 2 Virtual routers configured.  Both use 192.168.*.* networks.

 

I'd like to access a machine in the neighbour VR, from the opposite VR.  As the networks overlap, I presumed this would be a case of using NAT.  

 

I can't get the configuration to work at all.  The closest I've come is to use PBF, but that doesn't incorporate the NAT element.

 

Can anyone who has done this, recommend an example configuration?  I t can be as simple as:

 

default-VR

Client = 192.168.1.1

 

Next-VR

Client = 192.168.1.1

 

How does the default-VR client access the Next-VR client (and vice-versa).

 

Thanks

1 REPLY 1

L4 Transporter

I am afraid you cannot make this setup work with 2 VRs in same VSYS.

 

You should deploy 2 VSYS, each of them with their own VR. Then you can make NAT rules between the 2 VSYS.

  • 1850 Views
  • 1 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!