<?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: IP address for NAT in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ip-address-for-nat/m-p/124391#M46306</link>
    <description>&lt;P&gt;If your ISP is routing the subnet to your PA interface as the next hop, then no proxy-arp will be needed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If your ISP has added the second subnet to their interface and given you a second gateway address, then you need to add an address in this subnet and mask to your interface. &amp;nbsp;Then the necessary proxy arp will be created when you add the NAT rules.&lt;/P&gt;</description>
    <pubDate>Sun, 06 Nov 2016 11:42:05 GMT</pubDate>
    <dc:creator>pulukas</dc:creator>
    <dc:date>2016-11-06T11:42:05Z</dc:date>
    <item>
      <title>IP address for NAT</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ip-address-for-nat/m-p/122266#M46123</link>
      <description>&lt;P&gt;Hello Experts&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was checking confiugration on my PA firewall and I foud for every source and destination NAT, the public IP for NAT with /32 was assigned to external interface of firewall. In my opinion there is no need to assign public IP /32 to external interface of firewall? Can any body explain to me this&lt;/P&gt;</description>
      <pubDate>Sat, 29 Oct 2016 14:54:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ip-address-for-nat/m-p/122266#M46123</guid>
      <dc:creator>ghostrider</dc:creator>
      <dc:date>2016-10-29T14:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: IP address for NAT</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ip-address-for-nat/m-p/122343#M46134</link>
      <description>&lt;P&gt;Palo Alto NAT rules will automatically create the proxy-arp if the address is withing the subnet range of your existing external interface. &amp;nbsp;The address would not need to be added to the interface for this to work.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Oct 2016 12:38:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ip-address-for-nat/m-p/122343#M46134</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2016-10-30T12:38:23Z</dc:date>
    </item>
    <item>
      <title>Re: IP address for NAT</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ip-address-for-nat/m-p/124347#M46301</link>
      <description>&lt;P&gt;thank you but what we need to do if public pool range isin different range than external interface subnet range? Firewall will also do the proxy-arp for this&lt;/P&gt;</description>
      <pubDate>Sat, 05 Nov 2016 19:10:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ip-address-for-nat/m-p/124347#M46301</guid>
      <dc:creator>ghostrider</dc:creator>
      <dc:date>2016-11-05T19:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: IP address for NAT</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ip-address-for-nat/m-p/124391#M46306</link>
      <description>&lt;P&gt;If your ISP is routing the subnet to your PA interface as the next hop, then no proxy-arp will be needed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If your ISP has added the second subnet to their interface and given you a second gateway address, then you need to add an address in this subnet and mask to your interface. &amp;nbsp;Then the necessary proxy arp will be created when you add the NAT rules.&lt;/P&gt;</description>
      <pubDate>Sun, 06 Nov 2016 11:42:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ip-address-for-nat/m-p/124391#M46306</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2016-11-06T11:42:05Z</dc:date>
    </item>
  </channel>
</rss>

