<?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 Hi,Have you thought about Sub in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547903#M206175</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Have you thought about Sub Interfaces:-&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/interface_start.html#wp1082576&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
    <pubDate>Sat, 11 Oct 2014 00:53:01 GMT</pubDate>
    <dc:creator>Vibhor Amrodia</dc:creator>
    <dc:date>2014-10-11T00:53:01Z</dc:date>
    <item>
      <title>Multiple Subnets through ASA</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547902#M206174</link>
      <description>&lt;P&gt;I need to configure a firewall to allow several subnets/vlans through it. I'm having trouble figuring out a way for all of the subnets on one side to go through the ASA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the situation&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;RouterA P2P-&amp;gt; RouterB -&amp;gt; ASA -&amp;gt; L2Switch&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;L2Switch has VLANS 187-199&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm using an ASA5515-X that only has 6 interfaces so i obviously can't have all these subnets connected.&lt;/P&gt;&lt;P&gt;I tried transparent mode but can only have up to 8 BVI's.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am i over thinking this?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:54:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547902#M206174</guid>
      <dc:creator>Andrew Clark</dc:creator>
      <dc:date>2019-03-12T04:54:27Z</dc:date>
    </item>
    <item>
      <title>Hi,Have you thought about Sub</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547903#M206175</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Have you thought about Sub Interfaces:-&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/interface_start.html#wp1082576&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
      <pubDate>Sat, 11 Oct 2014 00:53:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547903#M206175</guid>
      <dc:creator>Vibhor Amrodia</dc:creator>
      <dc:date>2014-10-11T00:53:01Z</dc:date>
    </item>
    <item>
      <title>We typically make a transit</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547904#M206176</link>
      <description>&lt;P&gt;We typically make a transit VLAN between the switch and the ASA. It has only two L3 addresses - the switch SVI for that VLAN and the ASA inside interface.&lt;/P&gt;&lt;P&gt;You then either run a routing protocol (OSPF or EIGRP) to learn the routes dynamically or else the switch has the ASA address as its default gateway and the ASA has routes (or a summarized route) for the subnets pointing towards the switch.&lt;/P&gt;</description>
      <pubDate>Sat, 11 Oct 2014 04:24:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547904#M206176</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-11T04:24:53Z</dc:date>
    </item>
    <item>
      <title>I agree with Vibhor, you need</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547905#M206177</link>
      <description>&lt;P&gt;I agree with Vibhor, you need to setup subinterfaces on the ASA and allocate each subinterface to its respective VLAN.&amp;nbsp; The interface on the L2switch which connects to the ASA should be configured as a trunk interface.&lt;/P&gt;&lt;P&gt;That should sort you out.&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Please remember to select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Mon, 13 Oct 2014 08:35:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547905#M206177</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2014-10-13T08:35:03Z</dc:date>
    </item>
    <item>
      <title>I have done subinterfaces but</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547906#M206178</link>
      <description>&lt;P&gt;I have done subinterfaces but i must be over complicating it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So the L2 switch has it's usual VLANs, then on the inside interface of the ASA i set up subinterfaces with a transition VLAN, then the outside interface of the firewall is the routers uplink port?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm going to make a visio of how i invision this going down and upload it here.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Oct 2014 13:22:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547906#M206178</guid>
      <dc:creator>Andrew Clark</dc:creator>
      <dc:date>2014-10-13T13:22:54Z</dc:date>
    </item>
    <item>
      <title>If you internal switch is</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547907#M206179</link>
      <description>&lt;P&gt;If you internal switch is only L2 then yes you use subinterfaces.&lt;/P&gt;&lt;P&gt;You need a trunk port from the switch to the&amp;nbsp;ASA so that it tags all of the VLAN traffic destined for each subinterface on the ASA.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Oct 2014 13:29:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547907#M206179</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-13T13:29:33Z</dc:date>
    </item>
    <item>
      <title>I think i understand now.</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547908#M206180</link>
      <description>&lt;P&gt;I think i understand now. Something like this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Oct 2014 13:37:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547908#M206180</guid>
      <dc:creator>Andrew Clark</dc:creator>
      <dc:date>2014-10-13T13:37:32Z</dc:date>
    </item>
    <item>
      <title>The suggestion I made was for</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547909#M206181</link>
      <description>&lt;P&gt;The suggestion I made was for an ASA in routed mode - not transparent.&lt;/P&gt;&lt;P&gt;98% of the ASA installations I have seen (and I've seen several hundred) are routed mode.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Oct 2014 13:40:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547909#M206181</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-13T13:40:16Z</dc:date>
    </item>
    <item>
      <title>Ok. Does the outside</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547910#M206182</link>
      <description>&lt;P&gt;Ok. Does the outside interface need to be trunked as well or no? I understand that the Inside interface needs to be set up with subinterfaces which essentially turns the inside interface into a trunk. But what about the outside interface?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/0&lt;BR /&gt;&amp;nbsp;nameif outside&lt;BR /&gt;&amp;nbsp;security-level 0&lt;BR /&gt;&amp;nbsp;no ip address&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/1&lt;BR /&gt;&amp;nbsp;shutdown&lt;BR /&gt;&amp;nbsp;no nameif&lt;BR /&gt;&amp;nbsp;no security-level&lt;BR /&gt;&amp;nbsp;no ip address&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/1.187&lt;BR /&gt;&amp;nbsp;vlan 187&lt;BR /&gt;&amp;nbsp;nameif Inside-187&lt;BR /&gt;&amp;nbsp;security-level 100&lt;BR /&gt;&amp;nbsp;no ip address&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/1.188&lt;BR /&gt;&amp;nbsp;vlan 188&lt;BR /&gt;&amp;nbsp;nameif Inside-188&lt;BR /&gt;&amp;nbsp;security-level 100&lt;BR /&gt;&amp;nbsp;no ip address&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/1.189&lt;BR /&gt;&amp;nbsp;vlan 189&lt;BR /&gt;&amp;nbsp;nameif Inside-189&lt;BR /&gt;&amp;nbsp;security-level 100&lt;BR /&gt;&amp;nbsp;no ip address&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/1.190&lt;BR /&gt;&amp;nbsp;vlan 190&lt;BR /&gt;&amp;nbsp;nameif Inside-190&lt;BR /&gt;&amp;nbsp;security-level 100&lt;BR /&gt;&amp;nbsp;no ip address&lt;/P&gt;</description>
      <pubDate>Mon, 13 Oct 2014 14:55:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547910#M206182</guid>
      <dc:creator>Andrew Clark</dc:creator>
      <dc:date>2014-10-13T14:55:57Z</dc:date>
    </item>
    <item>
      <title>No, the outside interface</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547911#M206183</link>
      <description>&lt;P&gt;No, the outside interface would be not trunked.&amp;nbsp; But the upstream router would need to send all the various subnets to the ASA, and if there is any inbound traffic the ACL's on the outside interface would have to permit it.&lt;/P&gt;&lt;P&gt;-- Jim Leinweber, WI State Lab of Hygiene&lt;/P&gt;</description>
      <pubDate>Mon, 13 Oct 2014 22:29:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547911#M206183</guid>
      <dc:creator>James Leinweber</dc:creator>
      <dc:date>2014-10-13T22:29:04Z</dc:date>
    </item>
    <item>
      <title>As Jim correctly noted, there</title>
      <link>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547912#M206184</link>
      <description>&lt;P&gt;As Jim correctly noted, there's no trunk necessary upstream.&lt;/P&gt;&lt;P&gt;Routing needs to work as needed - typically we NAT on the firewall to either the interface address (dynamic PAT) &amp;nbsp;or to specific addresses in the outside subnet (static NAT). In either of those cases the upstream router never sees the inside subnets - only the addresses on the connected interface whose subnet it shares with the ASA's outside interface.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In routed mode, your interfaces need to have IP addresses.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Oct 2014 03:00:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-subnets-through-asa/m-p/2547912#M206184</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-14T03:00:41Z</dc:date>
    </item>
  </channel>
</rss>

