<?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 Multiple VLANs and ACLs in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/multiple-vlans-and-acls/m-p/2153749#M361143</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, looks like that would work the best and be fastest to implement.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 Feb 2013 15:24:19 GMT</pubDate>
    <dc:creator>alexray92</dc:creator>
    <dc:date>2013-02-28T15:24:19Z</dc:date>
    <item>
      <title>Multiple VLANs and ACLs</title>
      <link>https://community.cisco.com/t5/network-security/multiple-vlans-and-acls/m-p/2153747#M361140</link>
      <description>&lt;P&gt;I'm having a bit of trouble determing the best way to do this... I have 12 VLANs set up (subinterfaces on a redundant group of two NICs) on my ASA 5510.&amp;nbsp; On several of these, I want them to be able to access the internet but not access other VLANs.&amp;nbsp; By default, they have a rule like "any to any less secure", and since the outside interface has a lower security level, this works great.&amp;nbsp; But if I create an ACL on the interface, this rule disappears.&amp;nbsp; I can restore internet access by adding an "any to any" or "(this interface's subnet) to any" rule, but this seems to imply that it allows access to any vlan.&amp;nbsp; Do I have to create a set of "deny" rules for each VLAN, on each VLAN, followed by an any-any rule to allow internet access, or is there a cleaner approach?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:07:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-vlans-and-acls/m-p/2153747#M361140</guid>
      <dc:creator>alexray92</dc:creator>
      <dc:date>2019-03-12T01:07:31Z</dc:date>
    </item>
    <item>
      <title>Multiple VLANs and ACLs</title>
      <link>https://community.cisco.com/t5/network-security/multiple-vlans-and-acls/m-p/2153748#M361141</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I personally 99% of the time using ACL on each interface and not relying on the "security-level" values of interfaces. When I configure an ACL and create the rules I want, I know exactly who gets where and I dont have to wonder and play around with the "security-level" value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also naturally if you play with the "security-level" value the situation is so that either all traffic is blocked or allowed between the Vlans and you might eventually end up in a situation where you add an ACL anyway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could for example do the follwing&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Create an "object-group" that contains all the 12 Vlan networks&lt;/LI&gt;&lt;LI&gt;Create an "access-list" that first blocks any traffic with the destination set to the created "object-group"&lt;/LI&gt;&lt;LI&gt;Create a rule in the "access-list" that permits all the rest of the traffic&lt;/LI&gt;&lt;LI&gt;In the cases where the Vlan using the mentioned ACL needs to access some other Vlans&lt;UL&gt;&lt;LI&gt;First create rules to allow certain traffic at the top &lt;/LI&gt;&lt;LI&gt;Block rest of the traffic with the "object-group" as destination&lt;/LI&gt;&lt;LI&gt;Permit rest of the traffic&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A simple example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;OBJECT-GROUP CONTAININ ALL NETWORKS&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object-group ALL-VLAN-NETWORKS&lt;/P&gt;&lt;P&gt; network-object 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt; network-object 10.10.20.0 255.255.255.0&lt;/P&gt;&lt;P&gt; network-object 10.10.30.0 255.255.255.0&lt;/P&gt;&lt;P&gt; network-object 10.10.40.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ACCESS-LIST THAT BLOCK INTER-VLAN TRAFFIC&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN remark Block Inter-Vlan traffic&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN deny ip any object-group ALL-VLAN-NETWORKS&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN remark Permit all other traffic&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN permit ip 10.10.10.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ACCESS-LIST THAT ALLOWS AND BLOCKS SOME INTER-VLAN TRAFFIC&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN remark Permit traffic to Vlan20&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN permit ip 10.10.10.0 255.255.255.0 10.10.20.0 255.255.255.0&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN remark Block Inter-Vlan traffic&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN deny ip any object-group ALL-VLAN-NETWORKS&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN remark Permit all other traffic&lt;/P&gt;&lt;P&gt;access-list VLAN-10-IN permit ip 10.10.10.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Feb 2013 15:22:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-vlans-and-acls/m-p/2153748#M361141</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-02-28T15:22:09Z</dc:date>
    </item>
    <item>
      <title>Multiple VLANs and ACLs</title>
      <link>https://community.cisco.com/t5/network-security/multiple-vlans-and-acls/m-p/2153749#M361143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, looks like that would work the best and be fastest to implement.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Feb 2013 15:24:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-vlans-and-acls/m-p/2153749#M361143</guid>
      <dc:creator>alexray92</dc:creator>
      <dc:date>2013-02-28T15:24:19Z</dc:date>
    </item>
  </channel>
</rss>

