<?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: Intervlan connection with 4204vl in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/intervlan-connection-with-4204vl/m-p/4394017#M18101</link>
    <description>Thank you for your reply, on tagged A1 i have 9 procurve 2810-24g. to the different vlan. So event i if i use a router like 2003 server and trunk all my vlan on a port can't i control the trafic with that ? like using ospf or rip to route all the vlan on vlan 3 and vlan 99 ?&lt;BR /&gt;&lt;BR /&gt;Or if you have an other solution iam open :) THANKS you  &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 03 Apr 2009 09:32:18 GMT</pubDate>
    <dc:creator>jamalator</dc:creator>
    <dc:date>2009-04-03T09:32:18Z</dc:date>
    <item>
      <title>Intervlan connection with 4204vl</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/intervlan-connection-with-4204vl/m-p/4394015#M18099</link>
      <description>Hello iam trying to connect all my vlan to vlan3 exept vlan 110 and vlan 110 to vlan 99 i have 9 swith L2 and a 4204vl: this is the config witjh the dhcp:&lt;BR /&gt;=============================================&lt;BR /&gt; ; J8770A Configuration Editor; Created on release #L.10.23&lt;BR /&gt;&lt;BR /&gt;hostname "ProCurve Switch 4204vl" &lt;BR /&gt;max-vlans 25 &lt;BR /&gt;module 1 type J8768A &lt;BR /&gt;module 2 type J9033A &lt;BR /&gt;trunk B2 Trk1 Trunk &lt;BR /&gt;ip default-gateway 172.16.1.253 &lt;BR /&gt;ip routing &lt;BR /&gt;snmp-server community "public" Unrestricted &lt;BR /&gt;vlan 1 &lt;BR /&gt;   name "services" &lt;BR /&gt;   untagged A2-A20,B9-B17,B19-B24,Trk1 &lt;BR /&gt;   ip address 172.16.1.1 255.255.255.0 &lt;BR /&gt;   no untagged A1,A21-A24,B1,B3-B8,B18 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 60 &lt;BR /&gt;   name "adaris_data" &lt;BR /&gt;   ip address 172.16.60.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 61 &lt;BR /&gt;   name "adaris_voip" &lt;BR /&gt;   ip address 172.16.61.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 90 &lt;BR /&gt;   name "tarik_data" &lt;BR /&gt;   ip address 172.16.90.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 91 &lt;BR /&gt;   name "tarik_voip" &lt;BR /&gt;   ip address 172.16.91.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 70 &lt;BR /&gt;   name "douka_data" &lt;BR /&gt;   ip address 172.16.70.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 71 &lt;BR /&gt;   name "douka_voip" &lt;BR /&gt;   ip address 172.16.71.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 80 &lt;BR /&gt;   name "atlas_data" &lt;BR /&gt;   ip address 172.16.80.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 81 &lt;BR /&gt;   name "atlas_voip" &lt;BR /&gt;   ip address 172.16.81.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 100 &lt;BR /&gt;   name "sbrahim_data" &lt;BR /&gt;   ip address 172.16.100.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 101 &lt;BR /&gt;   name "sbrahim_voip" &lt;BR /&gt;   ip address 172.16.101.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 50 &lt;BR /&gt;   name "agdal_data" &lt;BR /&gt;   ip address 172.16.50.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 51 &lt;BR /&gt;   name "agdal_voip" &lt;BR /&gt;   ip address 172.16.51.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 110 &lt;BR /&gt;   name "wifi_data" &lt;BR /&gt;   untagged B18 &lt;BR /&gt;   ip address 172.16.110.3 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 120 &lt;BR /&gt;   name "wilaya_data" &lt;BR /&gt;   ip address 172.16.120.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 121 &lt;BR /&gt;   name "wilaya_voip" &lt;BR /&gt;   ip address 172.16.121.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 3 &lt;BR /&gt;   name "internet" &lt;BR /&gt;   untagged B1,B3-B8 &lt;BR /&gt;   ip address 172.16.3.1 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 99 &lt;BR /&gt;   name "test" &lt;BR /&gt;   untagged A21-A24 &lt;BR /&gt;   ip address 172.16.99.1 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 20 &lt;BR /&gt;   name "aragdal_data" &lt;BR /&gt;   ip address 172.16.20.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 21 &lt;BR /&gt;   name "aragdal_voip" &lt;BR /&gt;   ip address 172.16.21.2 255.255.255.0 &lt;BR /&gt;   ip helper-address 172.16.1.254 &lt;BR /&gt;   tagged A1 &lt;BR /&gt;   exit &lt;BR /&gt;ip route 172.16.0.0 255.255.0.0 172.16.1.254 &lt;BR /&gt;dhcp-snooping&lt;BR /&gt;dhcp-snooping authorized-server 172.16.1.254&lt;BR /&gt;dhcp-snooping vlan 1-121 &lt;BR /&gt;interface B16&lt;BR /&gt;   dhcp-snooping trust&lt;BR /&gt;   exit&lt;BR /&gt;spanning-tree Trk1 priority 4&lt;BR /&gt;password manager&lt;BR /&gt;password operator&lt;BR /&gt;&lt;BR /&gt;============================================&lt;BR /&gt;&lt;BR /&gt;I am stuck please HELP</description>
      <pubDate>Thu, 02 Apr 2009 19:37:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/intervlan-connection-with-4204vl/m-p/4394015#M18099</guid>
      <dc:creator>jamalator</dc:creator>
      <dc:date>2009-04-02T19:37:56Z</dc:date>
    </item>
    <item>
      <title>Re: Intervlan connection with 4204vl</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/intervlan-connection-with-4204vl/m-p/4394016#M18100</link>
      <description>better post config in attachment.&lt;BR /&gt;&lt;BR /&gt;with "ip routing" active, "ip default-gateway 172.16.1.253" in the switch config will be ignored , you must use "ip route 0.0.0.0 0.0.0.0 &lt;DESTINATION&gt;" instead.&lt;BR /&gt;(not configure default-gateway but default-route wich does the same thing).&lt;BR /&gt;&lt;BR /&gt;then you have "ip route 172.16.0.0 255.255.0.0 172.16.1.254" &lt;BR /&gt;but many adresses from 172.16.0.0 are local&lt;BR /&gt;vlan 60  ip address 172.16.60.2 255.255.255.0 &lt;BR /&gt;vlan 61  ip address 172.16.61.2 255.255.255.0 &lt;BR /&gt;vlan 90  ip address 172.16.90.2 255.255.255.0 &lt;BR /&gt;vlan 91  ip address 172.16.91.2 255.255.255.0 &lt;BR /&gt;vlan 70  ip address 172.16.70.2 255.255.255.0 &lt;BR /&gt;vlan 71  ip address 172.16.71.2 255.255.255.0 &lt;BR /&gt;&lt;BR /&gt;you may want to change "ip route 172.16.0.0 255.255.0.0 172.16.1.254" &lt;BR /&gt;to "ip route 0.0.0.0 0.0.0.0 172.16.1.254" &lt;BR /&gt;&lt;BR /&gt;many vlan's are only "tagged A1" and no other ports (untagged or tagged).&lt;BR /&gt;what's connected to A1?&lt;BR /&gt;&lt;BR /&gt;but then all vlan's will be able to route.&lt;BR /&gt;As the 4202 does not support ACL's you cannot limit access between vlan's.&lt;BR /&gt;So what you want cannot be done with the 4202&lt;/DESTINATION&gt;</description>
      <pubDate>Fri, 03 Apr 2009 08:54:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/intervlan-connection-with-4204vl/m-p/4394016#M18100</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2009-04-03T08:54:38Z</dc:date>
    </item>
    <item>
      <title>Re: Intervlan connection with 4204vl</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/intervlan-connection-with-4204vl/m-p/4394017#M18101</link>
      <description>Thank you for your reply, on tagged A1 i have 9 procurve 2810-24g. to the different vlan. So event i if i use a router like 2003 server and trunk all my vlan on a port can't i control the trafic with that ? like using ospf or rip to route all the vlan on vlan 3 and vlan 99 ?&lt;BR /&gt;&lt;BR /&gt;Or if you have an other solution iam open :) THANKS you  &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Apr 2009 09:32:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/intervlan-connection-with-4204vl/m-p/4394017#M18101</guid>
      <dc:creator>jamalator</dc:creator>
      <dc:date>2009-04-03T09:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: Intervlan connection with 4204vl</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/intervlan-connection-with-4204vl/m-p/4394018#M18102</link>
      <description>If you use a router (or switch) that CAN use ACL's, then you can control trafic to allow only traffic between given vlan's.&lt;BR /&gt;with the current switch it's all or nothing.&lt;BR /&gt;&lt;BR /&gt;The switch can do port-based acces-control&lt;BR /&gt;If you put different ports in a different vlan than you can configure if this port may communicate with the trunk (A1).&lt;BR /&gt;Wich may do almost what you want.&lt;BR /&gt;&lt;BR /&gt;I've no knowledge about w2k3 routing to answer if it's capable of using ACL's</description>
      <pubDate>Fri, 03 Apr 2009 09:40:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/intervlan-connection-with-4204vl/m-p/4394018#M18102</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2009-04-03T09:40:02Z</dc:date>
    </item>
  </channel>
</rss>

