<?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 Separating VLANS on Procurve 4208 in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493946#M19707</link>
    <description>I am unable to prevent Vlan 4 from seeing Vlan 3.&lt;BR /&gt;Vlan 4 is the wireless vlan that I want to prevent from seeing the office network vlan 3&lt;BR /&gt;&lt;BR /&gt;Vlan 3 and Vlan 4 both use the same port to the router, A1.&lt;BR /&gt;I have even gone so far as to tell all the ports on vlan 3 to drop anything from ports E19 and E20 which are part of vlan 4 via:&lt;BR /&gt;&lt;BR /&gt;filter source-port A2 drop E19-E20&lt;BR /&gt;&lt;BR /&gt;I have done this for every single port on the switch, except port A1 which connects to the router. I have done the reverse for ports E19-E20 on Vlan 4 to prevent them from communicating with anything but each other and port A1, the trunk port.&lt;BR /&gt;&lt;BR /&gt;yet I can still very easily get to the DB server by it's first name with out any trouble.&lt;BR /&gt;so if I go "run -&amp;gt; //mystorage"&lt;BR /&gt;It comes up with the login screen to access the server with no hitch. I do not want this to happen at all. I have tried everything, including using "forbid" on each Vlan interface.&lt;BR /&gt;Any help would be greatly appreciated. It's seems that everything that the manual say's to do does absolutely nothing to prevent the wireless vlan from being able to access the office vlan.&lt;BR /&gt;&lt;BR /&gt;Thank you in advance.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 09 Sep 2009 00:00:26 GMT</pubDate>
    <dc:creator>James M. Dougherty</dc:creator>
    <dc:date>2009-09-09T00:00:26Z</dc:date>
    <item>
      <title>Separating VLANS on Procurve 4208</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493946#M19707</link>
      <description>I am unable to prevent Vlan 4 from seeing Vlan 3.&lt;BR /&gt;Vlan 4 is the wireless vlan that I want to prevent from seeing the office network vlan 3&lt;BR /&gt;&lt;BR /&gt;Vlan 3 and Vlan 4 both use the same port to the router, A1.&lt;BR /&gt;I have even gone so far as to tell all the ports on vlan 3 to drop anything from ports E19 and E20 which are part of vlan 4 via:&lt;BR /&gt;&lt;BR /&gt;filter source-port A2 drop E19-E20&lt;BR /&gt;&lt;BR /&gt;I have done this for every single port on the switch, except port A1 which connects to the router. I have done the reverse for ports E19-E20 on Vlan 4 to prevent them from communicating with anything but each other and port A1, the trunk port.&lt;BR /&gt;&lt;BR /&gt;yet I can still very easily get to the DB server by it's first name with out any trouble.&lt;BR /&gt;so if I go "run -&amp;gt; //mystorage"&lt;BR /&gt;It comes up with the login screen to access the server with no hitch. I do not want this to happen at all. I have tried everything, including using "forbid" on each Vlan interface.&lt;BR /&gt;Any help would be greatly appreciated. It's seems that everything that the manual say's to do does absolutely nothing to prevent the wireless vlan from being able to access the office vlan.&lt;BR /&gt;&lt;BR /&gt;Thank you in advance.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Sep 2009 00:00:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493946#M19707</guid>
      <dc:creator>James M. Dougherty</dc:creator>
      <dc:date>2009-09-09T00:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: Separating VLANS on Procurve 4208</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493947#M19708</link>
      <description>Hello James,&lt;BR /&gt;&lt;BR /&gt;please post a "show running-config" from you switch.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Patrick</description>
      <pubDate>Wed, 09 Sep 2009 05:15:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493947#M19708</guid>
      <dc:creator>Patrick Terlisten</dc:creator>
      <dc:date>2009-09-09T05:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: Separating VLANS on Procurve 4208</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493948#M19709</link>
      <description>I'll get that on here in the am, seems that the config I emailed myself to my home account has gone missing. Tomorrow can only be a better day.</description>
      <pubDate>Wed, 09 Sep 2009 05:35:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493948#M19709</guid>
      <dc:creator>James M. Dougherty</dc:creator>
      <dc:date>2009-09-09T05:35:59Z</dc:date>
    </item>
    <item>
      <title>Re: Separating VLANS on Procurve 4208</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493949#M19710</link>
      <description>Finally had time to get the switch config to you.&lt;BR /&gt;Here it is.&lt;BR /&gt;Thank you again for any help.&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Sep 2009 15:37:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493949#M19710</guid>
      <dc:creator>James M. Dougherty</dc:creator>
      <dc:date>2009-09-09T15:37:59Z</dc:date>
    </item>
    <item>
      <title>Re: Separating VLANS on Procurve 4208</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493950#M19711</link>
      <description>I think your vlan4 connects to vlan3 via the router on A1.&lt;BR /&gt;&lt;BR /&gt;So all filter rules will have no effect as the ports do not communicate to E19/E20 directly (only through A1).&lt;BR /&gt;&lt;BR /&gt;Look into this router config, maybe you can creat an ACL there.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;Pieter</description>
      <pubDate>Thu, 10 Sep 2009 07:12:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/separating-vlans-on-procurve-4208/m-p/4493950#M19711</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2009-09-10T07:12:20Z</dc:date>
    </item>
  </channel>
</rss>

