<?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 PA-220 is not allowing inbound traffic in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pa-220-is-not-allowing-inbound-traffic/m-p/478303#M103736</link>
    <description>&lt;P&gt;HI PA Community! I have a very odd issue. My Palo will not allow any inbound connection. I was setting up GP and wondered why I can't hit the portal.&amp;nbsp; Then realized I can't even PING the public IP.&amp;nbsp;&amp;nbsp;I am using a dynamic PPoE connection to my ISP. I created a special rule to allow my testing external computer and can see the rules being hit. I can't even see my testing IP in the logs and yes, I enabled logging for it. I can see the bad IPs getting blocked in the logs. When doing a pcap, I can see the external interface is not responding to PING request (no response found). I enabled PING on the management profile, allowed the rules. I removed the zone protection. I removed threat protection. I'm at a loss as I've tried everything!&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 05 Apr 2022 11:00:04 GMT</pubDate>
    <dc:creator>DJ_Palo</dc:creator>
    <dc:date>2022-04-05T11:00:04Z</dc:date>
    <item>
      <title>PA-220 is not allowing inbound traffic</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-220-is-not-allowing-inbound-traffic/m-p/478303#M103736</link>
      <description>&lt;P&gt;HI PA Community! I have a very odd issue. My Palo will not allow any inbound connection. I was setting up GP and wondered why I can't hit the portal.&amp;nbsp; Then realized I can't even PING the public IP.&amp;nbsp;&amp;nbsp;I am using a dynamic PPoE connection to my ISP. I created a special rule to allow my testing external computer and can see the rules being hit. I can't even see my testing IP in the logs and yes, I enabled logging for it. I can see the bad IPs getting blocked in the logs. When doing a pcap, I can see the external interface is not responding to PING request (no response found). I enabled PING on the management profile, allowed the rules. I removed the zone protection. I removed threat protection. I'm at a loss as I've tried everything!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2022 11:00:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-220-is-not-allowing-inbound-traffic/m-p/478303#M103736</guid>
      <dc:creator>DJ_Palo</dc:creator>
      <dc:date>2022-04-05T11:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: PA-220 is not allowing inbound traffic</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-220-is-not-allowing-inbound-traffic/m-p/478304#M103737</link>
      <description>&lt;P&gt;In addition - Even internally, I cannot PING the Public IP. The Bell ISP says they are not blocking anything.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2022 11:01:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-220-is-not-allowing-inbound-traffic/m-p/478304#M103737</guid>
      <dc:creator>DJ_Palo</dc:creator>
      <dc:date>2022-04-05T11:01:17Z</dc:date>
    </item>
  </channel>
</rss>

