<?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 Cisco Twice NAT in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/cisco-twice-nat/m-p/519079#M512</link>
    <description>&lt;P&gt;I am working a migration of a Cisco ASA Firewall to Palo Alto and the NATs are confusing.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here are a couple of the NATs:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(Outside) to (Vendor) source static 10.5.1.0/24 10.5.1.0/24 destination static (10.24.49.47 &amp;amp; 10.24.49.46) (10.24.49.47 &amp;amp; 10.24.49.46)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(Outside) to (Outside) source static 10.160.100.100 67.91.127.197 destination static 69.167.253.23/32 69.167.253.23/32 service 5721-5722 5721-5722&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(DMZ) to (Vendor) source static 192.168.200.21/32 192.168.200.21/32 destination static 10.24.49.46/32 10.24.49.46/32 no-proxy-arp&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(inside) to (Outside) source static any any destination static 10.5.1.0/24 10.5.1.0/24 no-proxy-arp route-lookup&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(inside) to (Vendor) source dynamic (10.140.0.0/16 &amp;amp; 10.80.1.0/24 &amp;amp; 10.80.3.0/24) 172.16.1.200/32 destination static (170.209.0.2 &amp;amp; 170.209.0.3 &amp;amp; 170.209.0.4) (170.209.0.2 &amp;amp; 170.209.0.3 &amp;amp; 170.209.0.4)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(inside) to (Vendor) source static 10.100.100.100 10.100.100.100&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would love some help with Palo Alto NATs and Security Policies that go with them.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Oct 2022 18:20:59 GMT</pubDate>
    <dc:creator>Justin_Lucas</dc:creator>
    <dc:date>2022-10-25T18:20:59Z</dc:date>
    <item>
      <title>Cisco Twice NAT</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/cisco-twice-nat/m-p/519079#M512</link>
      <description>&lt;P&gt;I am working a migration of a Cisco ASA Firewall to Palo Alto and the NATs are confusing.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here are a couple of the NATs:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(Outside) to (Vendor) source static 10.5.1.0/24 10.5.1.0/24 destination static (10.24.49.47 &amp;amp; 10.24.49.46) (10.24.49.47 &amp;amp; 10.24.49.46)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(Outside) to (Outside) source static 10.160.100.100 67.91.127.197 destination static 69.167.253.23/32 69.167.253.23/32 service 5721-5722 5721-5722&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(DMZ) to (Vendor) source static 192.168.200.21/32 192.168.200.21/32 destination static 10.24.49.46/32 10.24.49.46/32 no-proxy-arp&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(inside) to (Outside) source static any any destination static 10.5.1.0/24 10.5.1.0/24 no-proxy-arp route-lookup&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(inside) to (Vendor) source dynamic (10.140.0.0/16 &amp;amp; 10.80.1.0/24 &amp;amp; 10.80.3.0/24) 172.16.1.200/32 destination static (170.209.0.2 &amp;amp; 170.209.0.3 &amp;amp; 170.209.0.4) (170.209.0.2 &amp;amp; 170.209.0.3 &amp;amp; 170.209.0.4)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(inside) to (Vendor) source static 10.100.100.100 10.100.100.100&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would love some help with Palo Alto NATs and Security Policies that go with them.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 18:20:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/cisco-twice-nat/m-p/519079#M512</guid>
      <dc:creator>Justin_Lucas</dc:creator>
      <dc:date>2022-10-25T18:20:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Twice NAT</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/cisco-twice-nat/m-p/522517#M623</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/210016"&gt;@Justin_Lucas&lt;/a&gt; .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would recommend you to check my reply in this discussion - &lt;A href="https://live.paloaltonetworks.com/t5/next-generation-firewall/twice-nat-of-asa-fw-equivalent-nat-rules-on-palo-alto-fw/m-p/516389#M432" target="_blank"&gt;https://live.paloaltonetworks.com/t5/next-generation-firewall/twice-nat-of-asa-fw-equivalent-nat-rules-on-palo-alto-fw/m-p/516389#M432&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please check it and let me know if you still have some questions about Palo NAT and how it translates to Cisco&lt;/P&gt;</description>
      <pubDate>Sun, 27 Nov 2022 22:02:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/cisco-twice-nat/m-p/522517#M623</guid>
      <dc:creator>aleksandar.astardzhiev</dc:creator>
      <dc:date>2022-11-27T22:02:39Z</dc:date>
    </item>
  </channel>
</rss>

