<?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 Acess-list in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/acess-list/m-p/1796299#M531007</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you configure access-list to deny, you will also need to explicitly configure the allow for the remaining of the other networks that you would like to allow, because there is an implicit deny any any at the end of the access-list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your scenario, if you just want to block 10.1.1.0/24 network, then you can configure the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside-acl deny ip 10.1.1.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;access-list inside-acl permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OR/ if you want to be more restrictive, you can also configure the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside-acl deny ip 10.1.1.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;access-list inside-acl permit ip 192.168.1.0 255.255.255.0 any&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Sep 2011 08:46:28 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2011-09-13T08:46:28Z</dc:date>
    <item>
      <title>Acess-list</title>
      <link>https://community.cisco.com/t5/network-security/acess-list/m-p/1796298#M531001</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In firewall traffic flows from higher level to lower level by default.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I apply access-list to deny particular traffic say 10.1.1.0 /24 network&amp;nbsp; should not flow to lower interface level and apply access-list on inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is that remaining network traffic say 192.168.1.0 /24 will also be blocked.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:23:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acess-list/m-p/1796298#M531001</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2019-03-11T21:23:56Z</dc:date>
    </item>
    <item>
      <title>Acess-list</title>
      <link>https://community.cisco.com/t5/network-security/acess-list/m-p/1796299#M531007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you configure access-list to deny, you will also need to explicitly configure the allow for the remaining of the other networks that you would like to allow, because there is an implicit deny any any at the end of the access-list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your scenario, if you just want to block 10.1.1.0/24 network, then you can configure the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside-acl deny ip 10.1.1.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;access-list inside-acl permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OR/ if you want to be more restrictive, you can also configure the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside-acl deny ip 10.1.1.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;access-list inside-acl permit ip 192.168.1.0 255.255.255.0 any&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Sep 2011 08:46:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acess-list/m-p/1796299#M531007</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-09-13T08:46:28Z</dc:date>
    </item>
    <item>
      <title>Acess-list</title>
      <link>https://community.cisco.com/t5/network-security/acess-list/m-p/1796300#M531011</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So same concept as on routers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Sep 2011 09:30:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acess-list/m-p/1796300#M531011</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2011-09-13T09:30:43Z</dc:date>
    </item>
    <item>
      <title>Acess-list</title>
      <link>https://community.cisco.com/t5/network-security/acess-list/m-p/1796301#M531015</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, absolutely correct, same concept as access-list on routers.&lt;/P&gt;&lt;P&gt;Pls kindly mark the post as answered if you have no further question. Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Sep 2011 10:15:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acess-list/m-p/1796301#M531015</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-09-13T10:15:07Z</dc:date>
    </item>
  </channel>
</rss>

