<?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 L3 routing in gbe2c in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548714#M20760</link>
    <description>Hi all, can anybody pls explain me why, in a gbe2c switch (the "plain" model, NOT the "l2/l3" model) it is possible to create IP interfaces on different vlans, but it's not possible to activate ip forwarding/ routing on them? I'd like to put up a vlan and use one of those interfaces as default gateway, but how? I must be missing something otherwise why would it allow interface creation if they can't be used?&lt;BR /&gt;&lt;BR /&gt;Thank you for any help</description>
    <pubDate>Fri, 11 Dec 2009 20:45:44 GMT</pubDate>
    <dc:creator>Rob_69_1</dc:creator>
    <dc:date>2009-12-11T20:45:44Z</dc:date>
    <item>
      <title>L3 routing in gbe2c</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548714#M20760</link>
      <description>Hi all, can anybody pls explain me why, in a gbe2c switch (the "plain" model, NOT the "l2/l3" model) it is possible to create IP interfaces on different vlans, but it's not possible to activate ip forwarding/ routing on them? I'd like to put up a vlan and use one of those interfaces as default gateway, but how? I must be missing something otherwise why would it allow interface creation if they can't be used?&lt;BR /&gt;&lt;BR /&gt;Thank you for any help</description>
      <pubDate>Fri, 11 Dec 2009 20:45:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548714#M20760</guid>
      <dc:creator>Rob_69_1</dc:creator>
      <dc:date>2009-12-11T20:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: L3 routing in gbe2c</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548715#M20761</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I think this is for management purposes. With IP interfaces in different vlans you will be able to manage the switch from different vlans.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Patrick</description>
      <pubDate>Sat, 12 Dec 2009 15:01:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548715#M20761</guid>
      <dc:creator>Patrick Terlisten</dc:creator>
      <dc:date>2009-12-12T15:01:50Z</dc:date>
    </item>
    <item>
      <title>Re: L3 routing in gbe2c</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548716#M20762</link>
      <description>Hi Patrick, thanks for your reply. That makes sense,nevertheless do you think it's possible to put up a simple IP forwarding mechanism in those interfaces? E.g. using a static ARP table, or adding a default gateway? I'm insisting on this because being able to do so would solve a big problem for me. I hope I'll be able to make it without having to buy a L2/L3 model. Unfortunately I have been recommended to buy the base model, and now I have those switches lacking a functionality that I need, and I'm struggling to put up at least a workaround...</description>
      <pubDate>Sun, 13 Dec 2009 15:38:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548716#M20762</guid>
      <dc:creator>Rob_69_1</dc:creator>
      <dc:date>2009-12-13T15:38:56Z</dc:date>
    </item>
    <item>
      <title>Re: L3 routing in gbe2c</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548717#M20763</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;this won't work. The switch can't do layer 3 routing, regardless of a static arp table etc.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Patrick</description>
      <pubDate>Mon, 14 Dec 2009 09:12:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548717#M20763</guid>
      <dc:creator>Patrick Terlisten</dc:creator>
      <dc:date>2009-12-14T09:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: L3 routing in gbe2c</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548718#M20764</link>
      <description>Thanks. I was hoping that at least for a few vlans I'd have been able to work around the problem, e.g. adding a default gw in the same range of addresses as the IPs in that vlan, but it seems that I have to make up my mind and rely on additional external hardware to do the routing.</description>
      <pubDate>Mon, 14 Dec 2009 10:07:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/l3-routing-in-gbe2c/m-p/4548718#M20764</guid>
      <dc:creator>Rob_69_1</dc:creator>
      <dc:date>2009-12-14T10:07:48Z</dc:date>
    </item>
  </channel>
</rss>

