<?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: Procurve 1800-24 VLAN Routing in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-1800-24-vlan-routing/m-p/4085683#M12635</link>
    <description>the firewall connects with 1 UTP cable to your 1800?&lt;BR /&gt;&lt;BR /&gt;you could use 2 UTPs, and do the routing on the firewall, if it knows how to handle more than 1 IP subnet.</description>
    <pubDate>Tue, 30 Oct 2007 05:12:27 GMT</pubDate>
    <dc:creator>OLARU Dan</dc:creator>
    <dc:date>2007-10-30T05:12:27Z</dc:date>
    <item>
      <title>Procurve 1800-24 VLAN Routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-1800-24-vlan-routing/m-p/4085680#M12632</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Bought this for home use as it supported VLANS. I was hoping to hook this switch up to my firewall at home and then be able to create VLANs on the 1800. Once I create VLANS on the 1800 I can't route between them. Do I need a smarter switch or have I not configured the 1800 properly?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Sun, 14 Oct 2007 02:24:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-1800-24-vlan-routing/m-p/4085680#M12632</guid>
      <dc:creator>doubleH</dc:creator>
      <dc:date>2007-10-14T02:24:57Z</dc:date>
    </item>
    <item>
      <title>Re: Procurve 1800-24 VLAN Routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-1800-24-vlan-routing/m-p/4085681#M12633</link>
      <description>The 1800 is a pure layer 2 switch without any routing functionality. &lt;BR /&gt;You'd need at least a 26xx or 2800 if you want  layer 3 (routing) functionality.</description>
      <pubDate>Sun, 14 Oct 2007 03:24:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-1800-24-vlan-routing/m-p/4085681#M12633</guid>
      <dc:creator>Thomas Joebstl</dc:creator>
      <dc:date>2007-10-14T03:24:34Z</dc:date>
    </item>
    <item>
      <title>Re: Procurve 1800-24 VLAN Routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-1800-24-vlan-routing/m-p/4085682#M12634</link>
      <description>Don't get the point.&lt;BR /&gt;&lt;BR /&gt;If you use Vlans, then your goal is to keep the two lans seperated.&lt;BR /&gt;&lt;BR /&gt;I think you want to create two range and route between them.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;B.Lagace</description>
      <pubDate>Mon, 29 Oct 2007 07:08:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-1800-24-vlan-routing/m-p/4085682#M12634</guid>
      <dc:creator>Lagace Bjorn</dc:creator>
      <dc:date>2007-10-29T07:08:01Z</dc:date>
    </item>
    <item>
      <title>Re: Procurve 1800-24 VLAN Routing</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-1800-24-vlan-routing/m-p/4085683#M12635</link>
      <description>the firewall connects with 1 UTP cable to your 1800?&lt;BR /&gt;&lt;BR /&gt;you could use 2 UTPs, and do the routing on the firewall, if it knows how to handle more than 1 IP subnet.</description>
      <pubDate>Tue, 30 Oct 2007 05:12:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-1800-24-vlan-routing/m-p/4085683#M12635</guid>
      <dc:creator>OLARU Dan</dc:creator>
      <dc:date>2007-10-30T05:12:27Z</dc:date>
    </item>
  </channel>
</rss>

