<?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: GeoDB Updates file in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/geodb-updates-file/m-p/4852073#M1101459</link>
    <description>&lt;P&gt;I did that and things are working fine. The TAC submitted didn't yield anything good either. Thank you&lt;/P&gt;</description>
    <pubDate>Fri, 09 Jun 2023 18:11:14 GMT</pubDate>
    <dc:creator>Knassi</dc:creator>
    <dc:date>2023-06-09T18:11:14Z</dc:date>
    <item>
      <title>GeoDB Updates file</title>
      <link>https://community.cisco.com/t5/network-security/geodb-updates-file/m-p/4851608#M1101399</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I downloaded the&amp;nbsp;GeoDB Updates and uploaded it. I have some geolocation rules set to block traffic from certain locations. Now some IPs are being blocked by those rules but the IPs are not from the locations i am blocking. Somehow the FMC sees those IP as coming from banned locations. Anyone seen that before? I want to open the&amp;nbsp;GeoDB&amp;nbsp; file downloaded and see what's in there. I have not been successful so far. Any help will be appreciated. Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jun 2023 20:19:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/geodb-updates-file/m-p/4851608#M1101399</guid>
      <dc:creator>Knassi</dc:creator>
      <dc:date>2023-06-08T20:19:34Z</dc:date>
    </item>
    <item>
      <title>Re: GeoDB Updates file</title>
      <link>https://community.cisco.com/t5/network-security/geodb-updates-file/m-p/4852058#M1101458</link>
      <description>&lt;P&gt;I have seen this issue a lot over the past couple years.&amp;nbsp; The only work-around we have found is to white list the source and destination IPs and ports that are being blocked / add ACP rules above the GeoBlock to allow that traffic.&amp;nbsp; We have had TAC on the case earlier and they cannot do anything as these IPs are automatically fetched (from Talos I believe).&lt;/P&gt;
&lt;P&gt;We have boiled the issue down to that some of these subnets are re-allocated to different geographic locations therefore causing the issue.&amp;nbsp; Not entirely sure if this is an issue with the classification or if the subnets are actually being allocated to new geographic locations.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 17:08:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/geodb-updates-file/m-p/4852058#M1101458</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2023-06-09T17:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: GeoDB Updates file</title>
      <link>https://community.cisco.com/t5/network-security/geodb-updates-file/m-p/4852073#M1101459</link>
      <description>&lt;P&gt;I did that and things are working fine. The TAC submitted didn't yield anything good either. Thank you&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 18:11:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/geodb-updates-file/m-p/4852073#M1101459</guid>
      <dc:creator>Knassi</dc:creator>
      <dc:date>2023-06-09T18:11:14Z</dc:date>
    </item>
  </channel>
</rss>

