<?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 Incorrect Geolocation classification in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/incorrect-geolocation-classification/m-p/588956#M3276</link>
    <description>&lt;P&gt;We have a user trying to connect with Global Protect from South Africa on IP 102.22.126.232&lt;BR /&gt;This IP belongs to an ISP in South Africa, and is matching correctly on &lt;A href="https://ipinfo.io/102.22.126.232" target="_blank"&gt;https://ipinfo.io/102.22.126.232&lt;/A&gt; to be in Cape Town&lt;/P&gt;
&lt;P&gt;However, when looking up the IP location on any of our Palo Alto Firewalls, all of them match this to MU (Mauritius )&lt;BR /&gt;This is incorrect and must be fixed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We cannot add a manual entry for this, as we would need to do this on all of our Firewalls. We feel this is an incorrect match on Palo Alto's side, or whomever they source their location data from.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can this be looked into and checked?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 06 Jun 2024 14:57:55 GMT</pubDate>
    <dc:creator>UtkarshKumar</dc:creator>
    <dc:date>2024-06-06T14:57:55Z</dc:date>
    <item>
      <title>Incorrect Geolocation classification</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/incorrect-geolocation-classification/m-p/588956#M3276</link>
      <description>&lt;P&gt;We have a user trying to connect with Global Protect from South Africa on IP 102.22.126.232&lt;BR /&gt;This IP belongs to an ISP in South Africa, and is matching correctly on &lt;A href="https://ipinfo.io/102.22.126.232" target="_blank"&gt;https://ipinfo.io/102.22.126.232&lt;/A&gt; to be in Cape Town&lt;/P&gt;
&lt;P&gt;However, when looking up the IP location on any of our Palo Alto Firewalls, all of them match this to MU (Mauritius )&lt;BR /&gt;This is incorrect and must be fixed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We cannot add a manual entry for this, as we would need to do this on all of our Firewalls. We feel this is an incorrect match on Palo Alto's side, or whomever they source their location data from.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can this be looked into and checked?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2024 14:57:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/incorrect-geolocation-classification/m-p/588956#M3276</guid>
      <dc:creator>UtkarshKumar</dc:creator>
      <dc:date>2024-06-06T14:57:55Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Geolocation classification</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/incorrect-geolocation-classification/m-p/588957#M3277</link>
      <description>&lt;P&gt;I am also facing the same issue&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2024 14:59:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/incorrect-geolocation-classification/m-p/588957#M3277</guid>
      <dc:creator>Didar-Bajwa</dc:creator>
      <dc:date>2024-06-06T14:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Geolocation classification</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/incorrect-geolocation-classification/m-p/588958#M3278</link>
      <description>&lt;P&gt;Same issue&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2024 15:00:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/incorrect-geolocation-classification/m-p/588958#M3278</guid>
      <dc:creator>Jagdeep1</dc:creator>
      <dc:date>2024-06-06T15:00:07Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect Geolocation classification</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/incorrect-geolocation-classification/m-p/589092#M3286</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;In the past I opened a support case and they have to take care of it on the backend.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2024 18:56:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/incorrect-geolocation-classification/m-p/589092#M3286</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2024-06-07T18:56:14Z</dc:date>
    </item>
  </channel>
</rss>

