<?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 Re: Destination NAT question in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/destination-nat-question/m-p/37856#M27705</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no problem here.&lt;/P&gt;&lt;P&gt;Page 28 is Vwire not Layer3 that is the difference&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Jun 2013 14:57:38 GMT</pubDate>
    <dc:creator>Retired Member</dc:creator>
    <dc:date>2013-06-17T14:57:38Z</dc:date>
    <item>
      <title>Destination NAT question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/destination-nat-question/m-p/37855#M27704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In this document is described how the NAT function at the Palo Alto.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-wiki-small" data-containerid="2021" data-containertype="14" data-objectid="1517" data-objecttype="102" href="https://live.paloaltonetworks.com/docs/DOC-1517"&gt;https://live.paloaltonetworks.com/docs/DOC-1517&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anything changed in the 5, in contrast to 4.1er?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So far, the destination NAT zone was generally on the incoming interface as the source and destination zone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the document is on page 20 (case3) and page 28 (Destination NAT) is the NAT-destination once (untrust / trust) and once untrust/ untrust with a service port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which act as is now correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jun 2013 14:50:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/destination-nat-question/m-p/37855#M27704</guid>
      <dc:creator>register</dc:creator>
      <dc:date>2013-06-17T14:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Destination NAT question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/destination-nat-question/m-p/37856#M27705</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no problem here.&lt;/P&gt;&lt;P&gt;Page 28 is Vwire not Layer3 that is the difference&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jun 2013 14:57:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/destination-nat-question/m-p/37856#M27705</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2013-06-17T14:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: Destination NAT question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/destination-nat-question/m-p/37857#M27706</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The general concept of D-NAT for any traffic is to verify source/destination zone ( forward lookup) and then firewall will evaluate the NAT policy. As a result the policy applied from Untrust-L3 to Untrust-L3. But page no-28 explained the NAT in VW mode. In VW mode IP address configured into Route-1 &amp;amp; router-2. The PA firewall is acting as a transparent device for R-1&amp;nbsp; and R-2. so, that is the reason D-NAT policy is applied from VW-Untrust to VW-trust here here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Subhankar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jun 2013 22:40:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/destination-nat-question/m-p/37857#M27706</guid>
      <dc:creator>HULK</dc:creator>
      <dc:date>2013-06-17T22:40:26Z</dc:date>
    </item>
  </channel>
</rss>

