<?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: How do you block IP based URL names? in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33235#M6965</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for bringing these to my attention.&lt;/P&gt;&lt;P&gt;I'd like to learn more about their use cases and consequences.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Feb 2019 14:33:55 GMT</pubDate>
    <dc:creator>Vladimir</dc:creator>
    <dc:date>2019-02-14T14:33:55Z</dc:date>
    <item>
      <title>How do you block IP based URL names?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33232#M6962</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sigh...&amp;nbsp; This would be easy if you were blocking uncategorized URL sites.&amp;nbsp; &lt;A href="http://8.8.8.8"&gt;http://8.8.8.8&lt;/A&gt;. would be blocked.&amp;nbsp; But we cannot block uncategorized.&amp;nbsp; In the logs, the Application Name shows the name as an IP.&amp;nbsp; There just does not seem to be a method to drop it.&amp;nbsp; Am I missing it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2019 20:10:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33232#M6962</guid>
      <dc:creator>George_Ellis</dc:creator>
      <dc:date>2019-02-13T20:10:06Z</dc:date>
    </item>
    <item>
      <title>Re: How do you block IP based URL names?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33233#M6963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should be able to define custom Applications and use IPs in URLs.&lt;/P&gt;&lt;P&gt;If you want to be less specific and simply drop any URL containing IP address, you should be able to do so by defining the custom App's URL as REGEX:&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-1 jive-image" src="https://community.checkpoint.com/legacyfs/online/checkpoint/78448_pastedImage_1.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not being regex expert, I cannot be more specific.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There used to be "All Unknown" or some such object in R77.XX, but it is no longer available.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2019 23:00:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33233#M6963</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2019-02-13T23:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: How do you block IP based URL names?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33234#M6964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is an "uncategorized" tag you can add to the rulebase to block/allow based on that (even in R80.x).&lt;/P&gt;&lt;P&gt;Also, in R80.x, there&amp;nbsp;is a "Unknown Traffic" App Control signature that matches everything that isn't HTTP that doesn't match any other signature.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2019 05:14:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33234#M6964</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-02-14T05:14:45Z</dc:date>
    </item>
    <item>
      <title>Re: How do you block IP based URL names?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33235#M6965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for bringing these to my attention.&lt;/P&gt;&lt;P&gt;I'd like to learn more about their use cases and consequences.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2019 14:33:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33235#M6965</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2019-02-14T14:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: How do you block IP based URL names?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33236#M6966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IP V4 has about 4 billion possible addresses.&amp;nbsp; It will take awhile to add them to that custom group.&amp;nbsp; Let alone that I have people already choking on the number of objects we have now.&amp;nbsp; &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://community.checkpoint.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;BR /&gt;&lt;BR /&gt;The point is to drop IP address URL strings.&amp;nbsp; After they figure that out that decimal addresses work to, then we will have to block those too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2019 15:03:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33236#M6966</guid>
      <dc:creator>George_Ellis</dc:creator>
      <dc:date>2019-02-14T15:03:12Z</dc:date>
    </item>
    <item>
      <title>Re: How do you block IP based URL names?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33237#M6967</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When using regular expressions, you are performing pattern matching. Use 0-9 or 0-9,0-9 or 0-9,0-0,0-9 for each octet, not actually adding those by hand.&lt;/P&gt;&lt;P&gt;If you are simply trying to discriminate between normal URLs and those containing IPs, this should allow &lt;A href="https://www.checkpoint.com"&gt;https://www.checkpoint.com&lt;/A&gt;&amp;nbsp;but block&amp;nbsp;&lt;A class="jivelink1" href="https://104.76.111.191/" title="https://104.76.111.191/"&gt;https://104.76.111.191/&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2019 16:11:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33237#M6967</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2019-02-14T16:11:40Z</dc:date>
    </item>
    <item>
      <title>Re: How do you block IP based URL names?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33238#M6968</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think something like this might work -&amp;nbsp;\/[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2019 16:50:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/How-do-you-block-IP-based-URL-names/m-p/33238#M6968</guid>
      <dc:creator>Alex_Weldon</dc:creator>
      <dc:date>2019-02-19T16:50:28Z</dc:date>
    </item>
  </channel>
</rss>

