<?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 Bi-Directional NAT To External IP not Configured on an Interface in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/bi-directional-nat-to-external-ip-not-configured-on-an-interface/m-p/420551#M93886</link>
    <description>&lt;P&gt;Hey All,&lt;/P&gt;&lt;P&gt;Working on a PA-220 on 10.0.6 here. I am trying to configure a BI-DI NAT for inside Zone A host 10.0.0.4 to Zone B public IP:&amp;nbsp;5.183.105.227. This traffic is to allow a vendor to build an IPSec VPN tunnel between their VPN appliance configured as 10.0.0.4 to their remote peer VPN of &lt;SPAN&gt;99.169.208.245&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Zone A = Inside (Interface 1/6: 10.0.0.1/24)&lt;/P&gt;&lt;P&gt;Zone B = Internet (Interface 1/1&amp;nbsp;5.183.105.229/29)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NAT is setup as:&lt;/P&gt;&lt;P&gt;Source Zone: A ---&amp;gt; Destination Zone: B, Destination Interface 1/1&lt;/P&gt;&lt;P&gt;Source Address: 10.0.0.4&lt;/P&gt;&lt;P&gt;Service Any&lt;/P&gt;&lt;P&gt;Source Translation: Static-IP&amp;nbsp;5.183.105.227&lt;/P&gt;&lt;P&gt;Bi-Di = Yes&lt;/P&gt;&lt;P&gt;Destination translation = Unconfigured.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have unrestricted security rules to allow traffic from Zone A to Zone B and from Zone B to Zone A.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I have been able to conclude when I look at the packet captures for this traffic is that there is never a transmit capture created but I do see in the Drop capture where 10.0.0.4 is attempting to communicate with&amp;nbsp;&lt;SPAN&gt;99.169.208.245 via ISAKMP 500 but it is dropped before getting routed.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since the IP (5.183.105.227) that i am trying to source NAT to is not configured on any interface, is there some sort of trickery to make it work with a PA?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I cannot get this to work and spent 3 hours on the phone with PA support to no avail.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jul 2021 06:10:03 GMT</pubDate>
    <dc:creator>JoeJackson</dc:creator>
    <dc:date>2021-07-20T06:10:03Z</dc:date>
    <item>
      <title>Bi-Directional NAT To External IP not Configured on an Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/bi-directional-nat-to-external-ip-not-configured-on-an-interface/m-p/420551#M93886</link>
      <description>&lt;P&gt;Hey All,&lt;/P&gt;&lt;P&gt;Working on a PA-220 on 10.0.6 here. I am trying to configure a BI-DI NAT for inside Zone A host 10.0.0.4 to Zone B public IP:&amp;nbsp;5.183.105.227. This traffic is to allow a vendor to build an IPSec VPN tunnel between their VPN appliance configured as 10.0.0.4 to their remote peer VPN of &lt;SPAN&gt;99.169.208.245&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Zone A = Inside (Interface 1/6: 10.0.0.1/24)&lt;/P&gt;&lt;P&gt;Zone B = Internet (Interface 1/1&amp;nbsp;5.183.105.229/29)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NAT is setup as:&lt;/P&gt;&lt;P&gt;Source Zone: A ---&amp;gt; Destination Zone: B, Destination Interface 1/1&lt;/P&gt;&lt;P&gt;Source Address: 10.0.0.4&lt;/P&gt;&lt;P&gt;Service Any&lt;/P&gt;&lt;P&gt;Source Translation: Static-IP&amp;nbsp;5.183.105.227&lt;/P&gt;&lt;P&gt;Bi-Di = Yes&lt;/P&gt;&lt;P&gt;Destination translation = Unconfigured.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have unrestricted security rules to allow traffic from Zone A to Zone B and from Zone B to Zone A.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I have been able to conclude when I look at the packet captures for this traffic is that there is never a transmit capture created but I do see in the Drop capture where 10.0.0.4 is attempting to communicate with&amp;nbsp;&lt;SPAN&gt;99.169.208.245 via ISAKMP 500 but it is dropped before getting routed.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since the IP (5.183.105.227) that i am trying to source NAT to is not configured on any interface, is there some sort of trickery to make it work with a PA?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I cannot get this to work and spent 3 hours on the phone with PA support to no avail.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jul 2021 06:10:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/bi-directional-nat-to-external-ip-not-configured-on-an-interface/m-p/420551#M93886</guid>
      <dc:creator>JoeJackson</dc:creator>
      <dc:date>2021-07-20T06:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: Bi-Directional NAT To External IP not Configured on an Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/bi-directional-nat-to-external-ip-not-configured-on-an-interface/m-p/420877#M93906</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Not sure on their VPN technology, however when I had to setup a tunnel between two PAN's where one was on the inside and already NAT'd. I had to use Peer Identifiers. So on the non-nated PAN, for the IKE tunnel, I had to use the Peer Identification option.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/10-0/pan-os-admin/vpns/set-up-site-to-site-vpn/set-up-an-ike-gateway" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/10-0/pan-os-admin/vpns/set-up-site-to-site-vpn/set-up-an-ike-gateway&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jul 2021 20:49:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/bi-directional-nat-to-external-ip-not-configured-on-an-interface/m-p/420877#M93906</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2021-07-20T20:49:03Z</dc:date>
    </item>
  </channel>
</rss>

