<?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 Thanks JJohnston.  Another in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/supernetting/m-p/2721501#M191744</link>
    <description>&lt;P&gt;Thanks JJohnston. &amp;nbsp;Another question to this. &amp;nbsp;Our 192.168.0.x&amp;nbsp;environment has&amp;nbsp;a VPN connection to 2 remote sites from this ASA. &amp;nbsp;In the ASA, we have the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list 101 extended permit ip 192.168.0.0 255.255.255.0 192.168.2.0 255.255.255.0&lt;BR /&gt;access-list 101 extended permit ip 192.168.0.0 255.255.255.0 192.168.15.0 255.255.255.0&lt;BR /&gt;access-list 120 extended permit ip 192.168.0.0 255.255.255.0 192.168.2.0 255.255.255.0&lt;BR /&gt;access-list 130 extended permit ip 192.168.0.0 255.255.255.0 192.168.15.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would we need to add separate access list statements in the same pattern as above, or would changing the command (like below), to adjust the subnet mask be sufficient?&lt;/P&gt;&lt;P&gt;access-list 101 extended permit ip 192.168.0.0 255.255.252.0 192.168.2.0 255.255.255.0&lt;/P&gt;&lt;P&gt;access-list 101 extended permit ip 192.168.0.0 255.255.252.0 192.168.15.0 255.255.255.0&lt;BR /&gt;access-list 120 extended permit ip 192.168.0.0 255.255.252.0 192.168.2.0 255.255.255.0&lt;BR /&gt;access-list 130 extended permit ip 192.168.0.0 255.255.252.0 192.168.15.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mooge&lt;/P&gt;</description>
    <pubDate>Mon, 11 May 2015 17:32:00 GMT</pubDate>
    <dc:creator>moogeboo1</dc:creator>
    <dc:date>2015-05-11T17:32:00Z</dc:date>
    <item>
      <title>supernetting</title>
      <link>https://community.cisco.com/t5/network-security/supernetting/m-p/2721499#M191740</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I need to expand the available hosts on our network. &amp;nbsp;The network is 192.168.0.x/24 and we are running out of IPs. &amp;nbsp;We have &amp;nbsp;single ASA and dumbswitches (Netgears). &amp;nbsp;If I change the subnet to 255.255.252.0, that would allow access to 192.168.0.x, 192.168.1.x, 192.168.2.x. &amp;nbsp;I can change the subnet mask on each static device, create a brand new DHCP scope, but will there be any change on the ASA besides just the subnet mask? &amp;nbsp;Remember, my switches are dumbswitches, and are not manageable.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mooge&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:54:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/supernetting/m-p/2721499#M191740</guid>
      <dc:creator>moogeboo1</dc:creator>
      <dc:date>2019-03-12T05:54:39Z</dc:date>
    </item>
    <item>
      <title>Changing the subnet mask on</title>
      <link>https://community.cisco.com/t5/network-security/supernetting/m-p/2721500#M191742</link>
      <description>&lt;P&gt;Changing the subnet mask on the ASA&amp;nbsp;should be sufficient. You should also be mindful of any objects/NAT rules referencing 192.168.0.x/24 and changing their subnet masks as well to accomodate the new supernet.&lt;/P&gt;</description>
      <pubDate>Sun, 10 May 2015 07:47:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/supernetting/m-p/2721500#M191742</guid>
      <dc:creator>jj27</dc:creator>
      <dc:date>2015-05-10T07:47:39Z</dc:date>
    </item>
    <item>
      <title>Thanks JJohnston.  Another</title>
      <link>https://community.cisco.com/t5/network-security/supernetting/m-p/2721501#M191744</link>
      <description>&lt;P&gt;Thanks JJohnston. &amp;nbsp;Another question to this. &amp;nbsp;Our 192.168.0.x&amp;nbsp;environment has&amp;nbsp;a VPN connection to 2 remote sites from this ASA. &amp;nbsp;In the ASA, we have the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list 101 extended permit ip 192.168.0.0 255.255.255.0 192.168.2.0 255.255.255.0&lt;BR /&gt;access-list 101 extended permit ip 192.168.0.0 255.255.255.0 192.168.15.0 255.255.255.0&lt;BR /&gt;access-list 120 extended permit ip 192.168.0.0 255.255.255.0 192.168.2.0 255.255.255.0&lt;BR /&gt;access-list 130 extended permit ip 192.168.0.0 255.255.255.0 192.168.15.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would we need to add separate access list statements in the same pattern as above, or would changing the command (like below), to adjust the subnet mask be sufficient?&lt;/P&gt;&lt;P&gt;access-list 101 extended permit ip 192.168.0.0 255.255.252.0 192.168.2.0 255.255.255.0&lt;/P&gt;&lt;P&gt;access-list 101 extended permit ip 192.168.0.0 255.255.252.0 192.168.15.0 255.255.255.0&lt;BR /&gt;access-list 120 extended permit ip 192.168.0.0 255.255.252.0 192.168.2.0 255.255.255.0&lt;BR /&gt;access-list 130 extended permit ip 192.168.0.0 255.255.252.0 192.168.15.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mooge&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2015 17:32:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/supernetting/m-p/2721501#M191744</guid>
      <dc:creator>moogeboo1</dc:creator>
      <dc:date>2015-05-11T17:32:00Z</dc:date>
    </item>
    <item>
      <title>You should change the subnet</title>
      <link>https://community.cisco.com/t5/network-security/supernetting/m-p/2721502#M191745</link>
      <description>&lt;P&gt;You should change the subnet mask to reflect the /22 network keeping in mind that you will need to make the same changes on the remote end VPN device.&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2015 18:47:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/supernetting/m-p/2721502#M191745</guid>
      <dc:creator>jj27</dc:creator>
      <dc:date>2015-05-11T18:47:26Z</dc:date>
    </item>
  </channel>
</rss>

