<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic NAT Between VR's in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/nat-between-vr-s/m-p/134437#M47341</link>
    <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;Despite my best efforts I am unable to get this concept working.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have 1 x Palo Alto 3020.&lt;/P&gt;&lt;P&gt;It has 2 Virtual routers configured. &amp;nbsp;Both use 192.168.*.* networks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd like to access a machine in the neighbour VR, from the opposite VR. &amp;nbsp;As the networks overlap, I presumed this would be a case of using NAT. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can't get the configuration to work at all. &amp;nbsp;The closest I've come is to use PBF, but that doesn't incorporate the NAT element.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone who has done this, recommend an example configuration? &amp;nbsp;I t can be as simple as:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;default-VR&lt;/P&gt;&lt;P&gt;Client = 192.168.1.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Next-VR&lt;/P&gt;&lt;P&gt;Client = 192.168.1.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How does the default-VR client access the Next-VR client (and vice-versa).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Fri, 23 Dec 2016 10:47:08 GMT</pubDate>
    <dc:creator>PCortes</dc:creator>
    <dc:date>2016-12-23T10:47:08Z</dc:date>
    <item>
      <title>NAT Between VR's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nat-between-vr-s/m-p/134437#M47341</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;Despite my best efforts I am unable to get this concept working.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have 1 x Palo Alto 3020.&lt;/P&gt;&lt;P&gt;It has 2 Virtual routers configured. &amp;nbsp;Both use 192.168.*.* networks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd like to access a machine in the neighbour VR, from the opposite VR. &amp;nbsp;As the networks overlap, I presumed this would be a case of using NAT. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can't get the configuration to work at all. &amp;nbsp;The closest I've come is to use PBF, but that doesn't incorporate the NAT element.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone who has done this, recommend an example configuration? &amp;nbsp;I t can be as simple as:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;default-VR&lt;/P&gt;&lt;P&gt;Client = 192.168.1.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Next-VR&lt;/P&gt;&lt;P&gt;Client = 192.168.1.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How does the default-VR client access the Next-VR client (and vice-versa).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 23 Dec 2016 10:47:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nat-between-vr-s/m-p/134437#M47341</guid>
      <dc:creator>PCortes</dc:creator>
      <dc:date>2016-12-23T10:47:08Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Between VR's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nat-between-vr-s/m-p/134447#M47344</link>
      <description>&lt;P&gt;I am afraid you cannot make this setup work with 2 VRs in same VSYS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You should deploy 2 VSYS, each of them with their own VR. Then you can make NAT rules between the 2 VSYS.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Dec 2016 12:35:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nat-between-vr-s/m-p/134447#M47344</guid>
      <dc:creator>cpainchaud</dc:creator>
      <dc:date>2016-12-23T12:35:00Z</dc:date>
    </item>
  </channel>
</rss>

