<?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: V-lan Communication in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062808#M895880</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can we make sub interfaces on L3 Switch like as in ASA. Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 28 Sep 2008 02:36:16 GMT</pubDate>
    <dc:creator>ray_stone</dc:creator>
    <dc:date>2008-09-28T02:36:16Z</dc:date>
    <item>
      <title>V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062779#M895848</link>
      <description>&lt;P&gt;Hi, Currently we have two sites which are connected via STS IP Sec Tunnel and using Cisco ASA 5505. By default three zones are created:-&lt;/P&gt;&lt;P&gt;1) DMZ&lt;/P&gt;&lt;P&gt;2) Inside&lt;/P&gt;&lt;P&gt;3) Outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inside and DMZ are a part of V-lan 1 and outside is V-lan2. We have make exempted rule for communication between Inside and DMZ and added other remote local network also.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now we have decided to make seperate V-lans for Inside and DMZ of eack site. Just want to know do we need any additional change in the configuration for communication among V-lans locally and remotely. Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:49:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062779#M895848</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2019-03-11T13:49:45Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062780#M895849</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ray,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No - as long as the VLAN's are sperate from each other - and the ASA has an interface in each of the VLAN's, you only need to allow traffic thru the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 07:01:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062780#M895849</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-09-26T07:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062781#M895850</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Would same exempted rule applicable for V-lan communication or it requires ip routing command like as a l3 switch configuration? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 07:36:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062781#M895850</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2008-09-26T07:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062782#M895851</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ray - here is what I mean:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firewall Outside interface in a vlan with NO SVI Layer 3 interface on the switch&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firewall DMZ interface in a vlan with NO SVI Layer 3 interface on the switch&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firewall Inside interface in a vlan with SVI Layer 3 interface on the switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then all other VLAN SVI's will communicate inter-vlan on the inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 08:01:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062782#M895851</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-09-26T08:01:34Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062783#M895852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry, I didn't understand properly. Request you to please mention in more details. Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 08:03:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062783#M895852</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2008-09-26T08:03:53Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062784#M895853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The outside vlan - does NOT have an ip address on the switch, it just passes traffic at layer 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The DMZ VLAN does not have an IP address on the switch, it just passes traffic at layer 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Inside VLAN does have an IP address on the switch - the inside VLAN does pass traffic at layer 3 to the internal network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 08:18:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062784#M895853</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-09-26T08:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062785#M895854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; hi Andrew &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i think the routing between vlans from security prespective should be done through the firewall right ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ray &lt;/P&gt;&lt;P&gt;u have now inside in vlan and dmz in other vlan &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if u make the intervlan routing on a switch then the comunication between dmz and inside will baypass the firewall not secure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;however if u dont make SVIs as Andrew mentioned amd just make the switch pass L2 traffic to the firewall interface&lt;/P&gt;&lt;P&gt;and the firewall interface IP address should be the defual gateway for each host i the corsponding vlan &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this way the firewall will handel the communication between VLANs &lt;/P&gt;&lt;P&gt;and take care of the requrment of NATing and ACL &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if helpful Rate&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 11:37:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062785#M895854</guid>
      <dc:creator>Marwan ALshawi</dc:creator>
      <dc:date>2008-09-26T11:37:49Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062786#M895855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if u make the intervlan routing on a switch then the comunication between dmz and inside will baypass the firewall not secure :- Will the comunication secure between the V-lans through the FW. Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 11:51:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062786#M895855</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2008-09-26T11:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062787#M895856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Correct.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 11:53:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062787#M895856</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-09-26T11:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062788#M895857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yep - correct&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 11:54:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062788#M895857</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-09-26T11:54:00Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062789#M895858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;May I know why its not secured while configuring on switch. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another Query : If I configure three different V-lans like 100,200,300 on a L3 switch and add one interface for each V-lan and assign IP address which would be the gateway of client machines and switch is connected with FW and we are using STS Tunnel. Now I want the remote machines of other sites communicate with my all local V-lans. What wud be the process. Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 12:08:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062789#M895858</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2008-09-26T12:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062790#M895859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you have layer 3 interfaces in those vlans, the IP traffic will bypass the firewall all together.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 12:11:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062790#M895859</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-09-26T12:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062791#M895860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do we require to make sub interfaces on FW as it will bypass all network traffic for remote nodes. Please suggest? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 12:23:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062791#M895860</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2008-09-26T12:23:31Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062792#M895861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ray - this is off this topic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is it you are asking now?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 12:25:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062792#M895861</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-09-26T12:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062793#M895862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi guys&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ray &lt;/P&gt;&lt;P&gt;u can do it in diffrent ways first of all u need to know what u wana acieve &lt;/P&gt;&lt;P&gt;do u want the communication between vlans pass through the switch and the firewall do firewalling between ur internal networks and outside and remote site network&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or u want the communication between vlans be firewalled and routed by the firewall as well &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;once u decide which method u wanna use then we can guid u easier &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thank you &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 12:40:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062793#M895862</guid>
      <dc:creator>Marwan ALshawi</dc:creator>
      <dc:date>2008-09-26T12:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062794#M895863</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this is 4 from me andrew &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 12:41:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062794#M895863</guid>
      <dc:creator>Marwan ALshawi</dc:creator>
      <dc:date>2008-09-26T12:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062795#M895864</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":monkey_face:"&gt;🐵&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 12:46:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062795#M895864</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-09-26T12:46:32Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062796#M895865</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you explain both scenario, if possible. Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 13:21:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062796#M895865</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2008-09-26T13:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062797#M895866</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ray,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The solution is born from the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are you trying to do/what do you want to do - if you do not know this, there is no solution - I hope this is plain enough.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2008 13:24:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062797#M895866</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-09-26T13:24:41Z</dc:date>
    </item>
    <item>
      <title>Re: V-lan Communication</title>
      <link>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062798#M895867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ok i will explain both &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;first one &lt;/P&gt;&lt;P&gt;lets say we have two internal vlans &lt;/P&gt;&lt;P&gt;vlan 10 10.1.1.0/24&lt;/P&gt;&lt;P&gt;vlan 20 20.1.1.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and the scenario like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access_switch with two vlan 10,20---L3 switch---ASA--internet--&lt;/P&gt;&lt;P&gt;ok&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now lets consider the first way which is intervaln on the switch &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i will creat third valn for the port connected from L3 switch and ASA called vlan 50&lt;/P&gt;&lt;P&gt;and the ASA ip is 50.1.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now on the access switchs only make L2 vlans like&lt;/P&gt;&lt;P&gt;vlan 10&lt;/P&gt;&lt;P&gt;vlan 20&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and the link between L2 switch and L3 switch is trunk&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on L3 switch we need to creat L2 and L3 vlans&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;like:&lt;/P&gt;&lt;P&gt;vlan 10&lt;/P&gt;&lt;P&gt;interface vlan 10&lt;/P&gt;&lt;P&gt;ip address 10.1.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt;no shut&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vlan 20&lt;/P&gt;&lt;P&gt;interface vlan 20&lt;/P&gt;&lt;P&gt;ip address 20.1.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt;no shut&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vlan 50&lt;/P&gt;&lt;P&gt;interface vlan 50 &lt;/P&gt;&lt;P&gt;ip address 50.1.1.2 255.255.255.0&lt;/P&gt;&lt;P&gt;no shut&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now enable ip routing on L3 switch &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip routing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now make the port with ASA as acces port and put it in valn 50&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now creat a defualt route point to ASA inside IP&lt;/P&gt;&lt;P&gt;ip route 0.0.0.0 0.0.0.0 5.1.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if u do show ip route &lt;/P&gt;&lt;P&gt;u will see all VLANs interfaces as directly connected and defualt static route to the ASA&lt;/P&gt;&lt;P&gt;on ASA u need two route for internal networks through vlan50 interface&lt;/P&gt;&lt;P&gt;like&lt;/P&gt;&lt;P&gt;route inside 10.1.1.0 255.255.255.0 50.1.1.2&lt;/P&gt;&lt;P&gt;route inside 20.1.1.0 255.255.255.0 50.1.1.2&lt;/P&gt;&lt;P&gt;route outisde 0.0.0.0 0.0.0.0 interface [outisde interface]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 1 0 0&lt;/P&gt;&lt;P&gt;global (outisde) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the defualt gateway for hosts in vlan 10 wil be 10.1.1.1&lt;/P&gt;&lt;P&gt;in vlan 20 will be 20.1.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OR...:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;dont make the VLAN interface on the L3 switch only L2 vlans and on the switch creat trunk port to the ASA and on ASA creat two subinterfaces each one in corsponding vlan like vlan 10 and vlan 20 and the same IP addressing&lt;/P&gt;&lt;P&gt;or &lt;/P&gt;&lt;P&gt;on the L3 switch&lt;/P&gt;&lt;P&gt;create make two access ports each one in a vlan that u have like one 10 and the other 20&lt;/P&gt;&lt;P&gt;and connect the access ports to diffrent physical por on ASA&lt;/P&gt;&lt;P&gt;now each vlan has its own interface or subinterface&lt;/P&gt;&lt;P&gt;both works and in both ways each ASA interface will have IP in this case this IP will be the defual gateway for the hosts in the corsponding vlan &lt;/P&gt;&lt;P&gt;thus the communication will be through ASA&lt;/P&gt;&lt;P&gt;u need only the route be done on the ASA&lt;/P&gt;&lt;P&gt;as we have done above each netwrok through the right interface and good luck u need ACLs as well from lower security to hgiher security interface communications&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if helpful Rate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Sep 2008 00:19:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/v-lan-communication/m-p/1062798#M895867</guid>
      <dc:creator>Marwan ALshawi</dc:creator>
      <dc:date>2008-09-27T00:19:00Z</dc:date>
    </item>
  </channel>
</rss>

