<?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: IP Ranges on ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664484#M1035528</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mm  ..  what about a packet been addressed to the broadcast IP address of one of the ranges ( which is actually used by a host )..   which might be considered by the firewall as a broadcast and hence be droped  ..  just another thought  ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Nov 2006 02:12:29 GMT</pubDate>
    <dc:creator>Fernando_Meza</dc:creator>
    <dc:date>2006-11-27T02:12:29Z</dc:date>
    <item>
      <title>IP Ranges on ASA</title>
      <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664476#M1035509</link>
      <description>&lt;P&gt;A simple question as I cannot seem to find a why to do it on our ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do you specify a range of addresses that are not summarizable? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example if I wanted to create an ACL that allows access from hosts 192.168.200.50 through to 192.168.200.239 to the internet, how would I configure these hosts on the ASA?.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dean &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 08:56:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664476#M1035509</guid>
      <dc:creator>dean.x.murray</dc:creator>
      <dc:date>2019-03-11T08:56:39Z</dc:date>
    </item>
    <item>
      <title>Re: IP Ranges on ASA</title>
      <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664477#M1035512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could use an object group. &lt;/P&gt;&lt;P&gt;See this link. &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/ps6120/products_command_reference_chapter09186a008063f0f7.html#wp1648552" target="_blank"&gt;http://www.cisco.com/en/US/products/ps6120/products_command_reference_chapter09186a008063f0f7.html#wp1648552&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With in the object group you can specify hosts or ranges defined by subnet masks.  You will need to do both.&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Nov 2006 20:09:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664477#M1035512</guid>
      <dc:creator>mgaysek</dc:creator>
      <dc:date>2006-11-15T20:09:27Z</dc:date>
    </item>
    <item>
      <title>Re: IP Ranges on ASA</title>
      <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664478#M1035515</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PIX/ASA provides the object-group to allow you to group host/subnets/services/icmp in a common or specific group, and have a simple one or two lines of ACL to allow the access. This saves your time in defining hundreds of ACL line/entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object-group network INTERNET_ACCESS &lt;/P&gt;&lt;P&gt;  network-object host 192.168.200.50 &lt;/P&gt;&lt;P&gt;  network-object host 192.168.200.51 &lt;/P&gt;&lt;P&gt;  network-object host 192.168.200.52 &lt;/P&gt;&lt;P&gt;  network-object host 192.168.200.239 &lt;/P&gt;&lt;P&gt;object-group service INTERNET_TCP_PORTS tcp &lt;/P&gt;&lt;P&gt;  port-object eq www &lt;/P&gt;&lt;P&gt;  port-object eq https &lt;/P&gt;&lt;P&gt;object-group service INTERNET_UDP_PORTS udp &lt;/P&gt;&lt;P&gt;  port-object eq domain &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside permit tcp object-group INTERNET_ACCESS any object-group INTERNET_TCP_PORTS &lt;/P&gt;&lt;P&gt;access-list inside permit udp object-group INTERNET_ACCESS any object-group INTERNET_UDP_PORTS &lt;/P&gt;&lt;P&gt;access-group inside in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Nov 2006 20:44:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664478#M1035515</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-11-15T20:44:25Z</dc:date>
    </item>
    <item>
      <title>Re: IP Ranges on ASA</title>
      <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664479#M1035518</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just as I thought you cannot easily add a range, so you have to add all addresses or a mixture of summarised and individual addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so there is no command like this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object-group network Internet_Access&lt;/P&gt;&lt;P&gt; network-object range 192.168.1.1-192.168.1.221&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Seems an odd ommission.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the confirmation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dean&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2006 13:39:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664479#M1035518</guid>
      <dc:creator>dean.x.murray</dc:creator>
      <dc:date>2006-11-21T13:39:19Z</dc:date>
    </item>
    <item>
      <title>Re: IP Ranges on ASA</title>
      <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664480#M1035520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, no option for 'range' under object-group for host. The option only allows you to  specify individual host or network/subnet ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/customer/products/ps6120/products_command_reference_chapter09186a008063f0f7.html#wp1647583" target="_blank"&gt;http://www.cisco.com/en/US/customer/products/ps6120/products_command_reference_chapter09186a008063f0f7.html#wp1647583&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Nov 2006 07:22:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664480#M1035520</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-11-22T07:22:24Z</dc:date>
    </item>
    <item>
      <title>Re: IP Ranges on ASA</title>
      <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664481#M1035522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can sort of create a range by using several masks:&lt;/P&gt;&lt;P&gt;192.168.200.50...51....52 and so on to 55&lt;/P&gt;&lt;P&gt;192.168.200.56 255.255.255.248&lt;/P&gt;&lt;P&gt;192.168.200.64 255.255.255.192&lt;/P&gt;&lt;P&gt;192.168.200.128 255.255.255.192&lt;/P&gt;&lt;P&gt;192.168.200.192 255.255.255.224&lt;/P&gt;&lt;P&gt;192.168.200.224 255.255.255.240&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ugly but it works&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Nov 2006 21:00:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664481#M1035522</guid>
      <dc:creator>dflick</dc:creator>
      <dc:date>2006-11-22T21:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: IP Ranges on ASA</title>
      <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664482#M1035524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;But what happened if the IP happened to be the subnet or broadcast ID -  currently being used by a host/wks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am sure it will conflict or could create a problem:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;List/range of host IPs: 192.168.200.50 to 192.168.200.239 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;192.168.200.56 255.255.255.248 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Subnet ID: 192.168.200.56 ---&amp;gt; this IP is needed/used for host&lt;/P&gt;&lt;P&gt;Usable range: 192.168.200.57 to 192.168.200.62 &lt;/P&gt;&lt;P&gt;Broadcast ID: 192.168.200.63 ---&amp;gt; this IP is needed/used for host&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Same with the rest. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just a thought.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Nov 2006 23:12:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664482#M1035524</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-11-22T23:12:06Z</dc:date>
    </item>
    <item>
      <title>Re: IP Ranges on ASA</title>
      <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664483#M1035527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since you are using these for an ACL, it makes absolutely no difference if it is a broadcast address.  The masks work for the same reason that the 255.255.255.254 masks work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Nov 2006 01:28:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664483#M1035527</guid>
      <dc:creator>dflick</dc:creator>
      <dc:date>2006-11-27T01:28:43Z</dc:date>
    </item>
    <item>
      <title>Re: IP Ranges on ASA</title>
      <link>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664484#M1035528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mm  ..  what about a packet been addressed to the broadcast IP address of one of the ranges ( which is actually used by a host )..   which might be considered by the firewall as a broadcast and hence be droped  ..  just another thought  ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Nov 2006 02:12:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-ranges-on-asa/m-p/664484#M1035528</guid>
      <dc:creator>Fernando_Meza</dc:creator>
      <dc:date>2006-11-27T02:12:29Z</dc:date>
    </item>
  </channel>
</rss>

