<?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: Why Destination NAT has no option for Bi Directional? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/why-destination-nat-has-no-option-for-bi-directional/m-p/255971#M72607</link>
    <description>&lt;P&gt;Many Thanks for confirmation&lt;/P&gt;</description>
    <pubDate>Wed, 03 Apr 2019 19:12:30 GMT</pubDate>
    <dc:creator>MP18</dc:creator>
    <dc:date>2019-04-03T19:12:30Z</dc:date>
    <item>
      <title>Why Destination NAT has no option for Bi Directional?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/why-destination-nat-has-no-option-for-bi-directional/m-p/255859#M72563</link>
      <description>&lt;P&gt;Need to understand when we do destination nat why there is no option for bidirectional ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For destination nat the return traffic comes without bi directional option not available due to the PA being stateful and matching&lt;/P&gt;&lt;P&gt;the session?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 04:19:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/why-destination-nat-has-no-option-for-bi-directional/m-p/255859#M72563</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2019-04-03T04:19:03Z</dc:date>
    </item>
    <item>
      <title>Re: Why Destination NAT has no option for Bi Directional?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/why-destination-nat-has-no-option-for-bi-directional/m-p/255962#M72601</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/75039"&gt;@MP18&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;It's more to do with how a destination NAT actually works; you can't make a bi-directional destination NAT policy, and it really wouldn't make any sense to do so.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 18:19:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/why-destination-nat-has-no-option-for-bi-directional/m-p/255962#M72601</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2019-04-03T18:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: Why Destination NAT has no option for Bi Directional?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/why-destination-nat-has-no-option-for-bi-directional/m-p/255971#M72607</link>
      <description>&lt;P&gt;Many Thanks for confirmation&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 19:12:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/why-destination-nat-has-no-option-for-bi-directional/m-p/255971#M72607</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2019-04-03T19:12:30Z</dc:date>
    </item>
  </channel>
</rss>

