<?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: Block the Internet in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/block-the-internet/m-p/1659545#M561311</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can try supernetting on class A addresses. Depending on the mask you choose, you can get either 4 or 8 parts of the entire ip range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By using a 2 bit mask, ie (192.0.0.0) you would get 4 parts:&lt;/P&gt;&lt;P&gt;0.0.0.0 - 63.255.255.255&lt;/P&gt;&lt;P&gt;64.0.0.0 - 127.255.255.255&lt;/P&gt;&lt;P&gt;128.0.0.0 - 191.255.255.255&lt;/P&gt;&lt;P&gt;192.0.0.0 - 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By using a 3 bit mask, ie (224.0.0.0) you would get 8 parts:&lt;/P&gt;&lt;P&gt;0.0.0.0 - 31.255.255.255&lt;/P&gt;&lt;P&gt;32.0.0.0 - 63.255.255.255&lt;/P&gt;&lt;P&gt;64.0.0.0 - 95.255.255.255&lt;/P&gt;&lt;P&gt;96.0.0.0 - 127.255.255.255&lt;/P&gt;&lt;P&gt;128.0.0.0 - 159.255.255.255&lt;/P&gt;&lt;P&gt;160.0.0.0 - 191.255.255.255&lt;/P&gt;&lt;P&gt;192.0.0.0 - 223.255.255.255&lt;/P&gt;&lt;P&gt;224.0.0.0 - 255.255.255.255 //This includes multicast(class D) and experimental(class E) ranges, and can probably be skipped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Shrikant&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P.S.: Please mark this question as answered if it has been resolved. Do rate helpful posts. Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 03 Jun 2011 06:12:52 GMT</pubDate>
    <dc:creator>Shrikant Sundaresh</dc:creator>
    <dc:date>2011-06-03T06:12:52Z</dc:date>
    <item>
      <title>Block the Internet</title>
      <link>https://community.cisco.com/t5/network-security/block-the-internet/m-p/1659544#M561308</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For phasing out a certain port - 143 - we decide to block the whole internet part by part as to effect a few customers at a time.&lt;BR /&gt;How can I break the Internet IPs into like 5-6 parts and deny each at a time?&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;John,&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:42:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-the-internet/m-p/1659544#M561308</guid>
      <dc:creator>MpacanaJr_2</dc:creator>
      <dc:date>2019-03-11T20:42:03Z</dc:date>
    </item>
    <item>
      <title>Re: Block the Internet</title>
      <link>https://community.cisco.com/t5/network-security/block-the-internet/m-p/1659545#M561311</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can try supernetting on class A addresses. Depending on the mask you choose, you can get either 4 or 8 parts of the entire ip range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By using a 2 bit mask, ie (192.0.0.0) you would get 4 parts:&lt;/P&gt;&lt;P&gt;0.0.0.0 - 63.255.255.255&lt;/P&gt;&lt;P&gt;64.0.0.0 - 127.255.255.255&lt;/P&gt;&lt;P&gt;128.0.0.0 - 191.255.255.255&lt;/P&gt;&lt;P&gt;192.0.0.0 - 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By using a 3 bit mask, ie (224.0.0.0) you would get 8 parts:&lt;/P&gt;&lt;P&gt;0.0.0.0 - 31.255.255.255&lt;/P&gt;&lt;P&gt;32.0.0.0 - 63.255.255.255&lt;/P&gt;&lt;P&gt;64.0.0.0 - 95.255.255.255&lt;/P&gt;&lt;P&gt;96.0.0.0 - 127.255.255.255&lt;/P&gt;&lt;P&gt;128.0.0.0 - 159.255.255.255&lt;/P&gt;&lt;P&gt;160.0.0.0 - 191.255.255.255&lt;/P&gt;&lt;P&gt;192.0.0.0 - 223.255.255.255&lt;/P&gt;&lt;P&gt;224.0.0.0 - 255.255.255.255 //This includes multicast(class D) and experimental(class E) ranges, and can probably be skipped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Shrikant&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P.S.: Please mark this question as answered if it has been resolved. Do rate helpful posts. Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Jun 2011 06:12:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-the-internet/m-p/1659545#M561311</guid>
      <dc:creator>Shrikant Sundaresh</dc:creator>
      <dc:date>2011-06-03T06:12:52Z</dc:date>
    </item>
    <item>
      <title>Re: Block the Internet</title>
      <link>https://community.cisco.com/t5/network-security/block-the-internet/m-p/1659546#M561314</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Shrikant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your reply. I appreciate it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in this ex.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By using a 2 bit mask, ie (192.0.0.0) you would get 4 parts:&lt;/P&gt;&lt;P&gt;0.0.0.0 - 63.255.255.255&lt;/P&gt;&lt;P&gt;64.0.0.0 - 127.255.255.255&lt;/P&gt;&lt;P&gt;128.0.0.0 - 191.255.255.255&lt;/P&gt;&lt;P&gt;192.0.0.0 - 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;So in an ASA 5510 ACL block this subnets?:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;0.0.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.0.0.0&lt;BR /&gt;64.0.0.0&amp;nbsp;&amp;nbsp; 192.0.0.0&lt;BR /&gt;128.0.0.0 192.0.0.0&lt;BR /&gt;192.0.0.0 192.0.0.0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;John&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;###&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you comment on the below suggestions, if it makes sense or not.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Called support twice:&lt;/P&gt;&lt;P&gt;One cisco tech suggested:&lt;/P&gt;&lt;P&gt;access-l outside_access_in deny tcp 0.0.0.0 64.0.0.0 any eq 143&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # CLI accepts but asdm does not. &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; it becomes 0.0.0.0.0/64.0.0.0 network as seen in ASDM ACL rules list.&lt;/P&gt;&lt;P&gt;access-l outside_access_in deny tcp 65.0.0.0 128.0.0.0 any eq 143&amp;nbsp; #error: does not pair&lt;BR /&gt;access-l outisde_access_in deny tcp 129.0.0.0 255.0.0.0 any eq 143&amp;nbsp;&amp;nbsp; # no effect/change on the ACL list&lt;BR /&gt;access-l outside_access_in deny tcp 0.0.0.0 128.0.0.0 any eq 143&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; # 0.0.0.0/1&amp;nbsp; *works&lt;BR /&gt;access-l outside_access_in deny tcp 128.0.0.0 128.0.0.0 any eq 143&amp;nbsp; # 128.0.0.0/1&amp;nbsp; *works&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another cisco tech suggested this ranges:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;0.0.0.0 32.0.0.0&lt;BR /&gt;32.0.0.0 32.0.0.0&lt;BR /&gt;64.0.0.0 224.0.0.0 --this will include 64-95 range&lt;BR /&gt;96.0.0.0 240.0.0.0 --this includes 96-111 fine ?&lt;BR /&gt;112.0.0.0 248.0.0.0&lt;BR /&gt;120.0.0.0 248.0.0.0&lt;BR /&gt;120.0.0.0 252.0.0.0&lt;BR /&gt;124.0.0.0 254.0.0.0.&lt;BR /&gt;126.0.0.0 255.0.0.0.&lt;BR /&gt;128.0.0.0 224.0.0.0&lt;/P&gt;&lt;P&gt;160.0.0.0 248.0.0.0&lt;BR /&gt;168.0.0.0 252.0.0.0&lt;BR /&gt;172.0.0.0. 255.240.0.0&lt;BR /&gt;172.32.0.0 255.224.0.0&lt;BR /&gt;172.64.0.0 255.192.0.0&lt;BR /&gt;172.128.0.0 255.128.0.0&lt;BR /&gt;173.0.0.0 255.0.0.0&lt;BR /&gt;174.0.0.0 254.0.0.0&lt;BR /&gt;182.0.0.0 254.0.0.0&lt;BR /&gt;184.0.0.0 254.0.0.0&lt;BR /&gt;188.0.0.0 252.0.0.0&lt;BR /&gt;192.0.0.0 255.128.0.0&lt;BR /&gt;192.128.0.0 255.224.0.0&lt;BR /&gt;192.169.0.0 255.255.0.0&lt;BR /&gt;192.170.0.0 255.254.0.0&lt;BR /&gt;192.172.0.0 255.252..0&lt;BR /&gt;192.176.0.0 255.240.0.0&lt;BR /&gt;192.192.0.0 255.192.0.0&lt;BR /&gt;193.0.0.0 255.0.0.0&lt;BR /&gt;194.0.0.0 254.0.0.0&lt;BR /&gt;196.0.0.0 252.0.0.0&lt;BR /&gt;200.0.0.0 248.0.0.0&lt;BR /&gt;208.0.0.0 240.0.0.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Jun 2011 18:58:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/block-the-internet/m-p/1659546#M561314</guid>
      <dc:creator>MpacanaJr_2</dc:creator>
      <dc:date>2011-06-03T18:58:38Z</dc:date>
    </item>
  </channel>
</rss>

