The user manuals can be found here:

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=125&prodTypeId=12883&prodSeriesId=329892

There are actually about 5 different manuals for each switch, getting started, advance config, etc..

I always thought that this was one of the primary features of VLANs; separating and grouping logic, rather than physical, connections.

With that in mind, if I wish to stop two VLANs talking to each other, I would just make sure they were on separate subnets, if I wanted to allow them to talk I would simply setup routes etc.

Thanks for all of your help.


My running config for the switch is as follows:


Running configuration:

; J4899A Configuration Editor; Created on release #H.10.50

hostname "ProCurve Switch 2650"
ip routing
snmp-server community "public" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   no ip address
   no untagged 1-50
   exit
vlan 2
   name "INTERNET"
   untagged 1
   ip address 10.1.201.2 255.255.255.0
   tagged 49-50
   exit
vlan 3
   name "RESIDENTS"
   untagged 2-24
   ip address 10.1.202.1 255.255.255.0
   tagged 1
   exit
vlan 4
   name "TEST"
   untagged 25-48
   ip address 10.1.205.1 255.255.255.0
   tagged 1,49-50
   exit




On 12/20/2011 03:49 PM, James Courtier-Dutton wrote:
On 20 December 2011 14:17, Steven Swann<[email protected]>  wrote:
Hello all,

Does anybody here have any experience in setting up VLANs on a HP ProCurve
switch? I am able to set up three different VLANs, one for internet, one for
users and one for development. The problem is that I want to allow both the
users and developers access to the internet VLAN since this is connected to
the ISP router.

I have the core of it set up as required, the problem seems to be the
routing between VLANs...

Any ideas?

Best Regards,

Steven Swann

I don't think they can do what you want.
Give a link to an online manual for your particular switch and I could
answer with 100% functionallity.

The feature you need is a "firewall" feature, or access control lists.
Routing and Switching will not help you.

So, you start by having everyone able to ping each other, and then you
add packet filters.

--
Please post to: [email protected]
Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL: http://www.hantslug.org.uk
--------------------------------------------------------------


--
Please post to: [email protected]
Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL: http://www.hantslug.org.uk
--------------------------------------------------------------

Reply via email to