<?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: Public to Public RFC 1918 blocks in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/public-to-public-rfc-1918-blocks/m-p/343024#M85906</link>
    <description>&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/139406" target="_blank" rel="noopener"&gt;@shafi021&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;it looks like&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480" target="_blank" rel="noopener"&gt;@BPry&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;got you taken care of with his reply.&amp;nbsp; I would just add that even if your firewall isn't using a public IP, and&amp;nbsp; your ISP was doing a source NAT on your outbound traffic, I wouldn't expect it to be doing any source NAT on the return traffic.&amp;nbsp; You would most likely see that the return traffic has the proper public IPs.&amp;nbsp; Also, the return traffic for established connections (those initiated from your LAN to the Internet) should be allowed anyway.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You would most likely only have an issue w/ RFC1918 traffic going from your Public zone to your LAN zone if you were both 1) using private IPs on your firewall's Public interface because your ISP is doing source NAT, and 2) needing some other device on the network between your firewall and ISP's device (the Public zone according to the firewall, but the private side according to the ISP's NAT device) to the firewall's LAN zone.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you're interested in a more comprehensive BOGON list than just RFC1918, I'm a fan of CYMRU's Full Bogon list, which also includes public IP ranges not yet allocated by IANA.&amp;nbsp; It can be used as an external dynamic list (EDL) on the Palo Alto firewall.&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://team-cymru.com/community-services/bogon-reference/bogon-reference-http/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://team-cymru.com/community-services/bogon-reference/bogon-reference-http/&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 27 Apr 2021 18:39:28 GMT</pubDate>
    <dc:creator>OwenFuller</dc:creator>
    <dc:date>2021-04-27T18:39:28Z</dc:date>
    <item>
      <title>Public to Public RFC 1918 blocks</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/public-to-public-rfc-1918-blocks/m-p/342944#M85897</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am looking to block the RFC 1918 blocks coming from internet to our LAN zone. So, Policy will be Source zone: Public , IP: RFC1918 blocks, Destination zone: LAN, IP : any .&lt;BR /&gt;&lt;BR /&gt;Can you guys please confirm that creating this policy will fulfill my requirement?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/107710"&gt;@OwenFuller&lt;/a&gt;&amp;nbsp;can you please give your input?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thank you&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2020 00:17:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/public-to-public-rfc-1918-blocks/m-p/342944#M85897</guid>
      <dc:creator>shafi021</dc:creator>
      <dc:date>2020-08-10T00:17:50Z</dc:date>
    </item>
    <item>
      <title>Re: Public to Public RFC 1918 blocks</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/public-to-public-rfc-1918-blocks/m-p/342962#M85900</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/139406"&gt;@shafi021&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;That will work as you expect. Are you actively seeing 1918 addresses coming across your untrust interface on the ISP side of things though? If so, the one thing you will want to double check is that your untrust interface actually has a public IP address being assigned to it, and not an RFC 1918 address which is being NAT'd by the carrier.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2020 03:35:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/public-to-public-rfc-1918-blocks/m-p/342962#M85900</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2020-08-10T03:35:13Z</dc:date>
    </item>
    <item>
      <title>Re: Public to Public RFC 1918 blocks</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/public-to-public-rfc-1918-blocks/m-p/343024#M85906</link>
      <description>&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/139406" target="_blank" rel="noopener"&gt;@shafi021&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;it looks like&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480" target="_blank" rel="noopener"&gt;@BPry&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;got you taken care of with his reply.&amp;nbsp; I would just add that even if your firewall isn't using a public IP, and&amp;nbsp; your ISP was doing a source NAT on your outbound traffic, I wouldn't expect it to be doing any source NAT on the return traffic.&amp;nbsp; You would most likely see that the return traffic has the proper public IPs.&amp;nbsp; Also, the return traffic for established connections (those initiated from your LAN to the Internet) should be allowed anyway.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You would most likely only have an issue w/ RFC1918 traffic going from your Public zone to your LAN zone if you were both 1) using private IPs on your firewall's Public interface because your ISP is doing source NAT, and 2) needing some other device on the network between your firewall and ISP's device (the Public zone according to the firewall, but the private side according to the ISP's NAT device) to the firewall's LAN zone.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you're interested in a more comprehensive BOGON list than just RFC1918, I'm a fan of CYMRU's Full Bogon list, which also includes public IP ranges not yet allocated by IANA.&amp;nbsp; It can be used as an external dynamic list (EDL) on the Palo Alto firewall.&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://team-cymru.com/community-services/bogon-reference/bogon-reference-http/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://team-cymru.com/community-services/bogon-reference/bogon-reference-http/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Apr 2021 18:39:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/public-to-public-rfc-1918-blocks/m-p/343024#M85906</guid>
      <dc:creator>OwenFuller</dc:creator>
      <dc:date>2021-04-27T18:39:28Z</dc:date>
    </item>
  </channel>
</rss>

