<?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: restrict vlan routing in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274484#M30035</link>
    <description>yes ip routing must be enable</description>
    <pubDate>Tue, 22 Feb 2011 08:31:19 GMT</pubDate>
    <dc:creator>cenk sasmaztin</dc:creator>
    <dc:date>2011-02-22T08:31:19Z</dc:date>
    <item>
      <title>restrict vlan routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274481#M30032</link>
      <description>&lt;BR /&gt;I have an HP Procurve E5406(Core) with vlan-10(guest-voice)IP-DHCP, Vlan-100(guest-data)IP-DHCP,vlan-300(switch mgmt)IP-192.168.6.X/24 and vlan-200(admin network)192.168.5.X/24. Now when  I enable ip routing all the vlan's are pinking each other. but i want to restrict the access of vlan 10 &amp;amp; 100 to vlan 200 &amp;amp; 300. i need only 200 &amp;amp; 300 to communicate each other.how is it possible? is it possible by creating ACL and how to do ACL in this case?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 21 Feb 2011 12:34:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274481#M30032</guid>
      <dc:creator>ACL</dc:creator>
      <dc:date>2011-02-21T12:34:07Z</dc:date>
    </item>
    <item>
      <title>Re: restrict vlan routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274482#M30033</link>
      <description>your config&lt;BR /&gt;your vlan unable between routing &lt;BR /&gt;because unasign ip address on vlan interface &lt;BR /&gt;&lt;BR /&gt;if you want use acl fristly assign vlan ip address&lt;BR /&gt;&lt;BR /&gt;for example configuration sperate vlan 100 between vlan 1 acl&lt;BR /&gt;****************************************&lt;BR /&gt;ip access-list standard "10"&lt;BR /&gt;   10 deny 192.168.2.0 0.0.0.255&lt;BR /&gt;   20 permit 0.0.0.0 255.255.255.255&lt;BR /&gt;   exit&lt;BR /&gt;vlan 1 &lt;BR /&gt;   name "DEFAULT_VLAN" &lt;BR /&gt;   ip address 192.168.2.50 255.255.255.0&lt;BR /&gt;   untagged B21-B24,C1-C24 &lt;BR /&gt;   no untagged A1-A24,B1-B20 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 100 &lt;BR /&gt;   name "Guest" &lt;BR /&gt;   ip address 192.168.3.50 255.255.255.0&lt;BR /&gt;   untagged A19-A20,B3-B4 &lt;BR /&gt;   tagged B21-B24,C1-C20 &lt;BR /&gt;   ip access-group "10" out&lt;BR /&gt;   exit &lt;BR /&gt;vlan 10 &lt;BR /&gt;   name "Voice" &lt;BR /&gt;   ip address 192.168.4.50 255.255.255.0&lt;BR /&gt;   untagged A17-A18,B1-B2 &lt;BR /&gt;   tagged B21-B24,C1-C20  &lt;BR /&gt;   exit &lt;BR /&gt;vlan 200&lt;BR /&gt;   name "Admin" &lt;BR /&gt;   ip address 192.168.5.50 255.255.255.0&lt;BR /&gt;   untagged A1-A16,B5-B20 &lt;BR /&gt;   tagged B21-B24,C1-C20&lt;BR /&gt;   exit&lt;BR /&gt;vlan 300&lt;BR /&gt;   name "Admin_Mgmt" &lt;BR /&gt;   untagged A21-A24 &lt;BR /&gt;   ip address 192.168.6.50 255.255.255.0&lt;BR /&gt;   tagged B21-B24,C1-C20&lt;BR /&gt;   exit &lt;BR /&gt;</description>
      <pubDate>Tue, 22 Feb 2011 00:42:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274482#M30033</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2011-02-22T00:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: restrict vlan routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274483#M30034</link>
      <description>Thank you..&lt;BR /&gt;can you give me a brief about how the ACL in the your example works? will it blocks all the traffic from vlan-100 to the default-vlan_1. also confirm if I have to enable IP routing or not.</description>
      <pubDate>Tue, 22 Feb 2011 05:06:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274483#M30034</guid>
      <dc:creator>ACL</dc:creator>
      <dc:date>2011-02-22T05:06:35Z</dc:date>
    </item>
    <item>
      <title>Re: restrict vlan routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274484#M30035</link>
      <description>yes ip routing must be enable</description>
      <pubDate>Tue, 22 Feb 2011 08:31:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274484#M30035</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2011-02-22T08:31:19Z</dc:date>
    </item>
    <item>
      <title>Re: restrict vlan routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274485#M30036</link>
      <description>thank you so much</description>
      <pubDate>Sun, 27 Feb 2011 04:36:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274485#M30036</guid>
      <dc:creator>ACL</dc:creator>
      <dc:date>2011-02-27T04:36:37Z</dc:date>
    </item>
    <item>
      <title>Re: restrict vlan routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274486#M30037</link>
      <description>thanks</description>
      <pubDate>Sun, 27 Feb 2011 04:39:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/restrict-vlan-routing/m-p/5274486#M30037</guid>
      <dc:creator>ACL</dc:creator>
      <dc:date>2011-02-27T04:39:23Z</dc:date>
    </item>
  </channel>
</rss>

