- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Separating VLANS on Procurve 4208
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-08-2009 05:00 PM
09-08-2009 05:00 PM
Vlan 4 is the wireless vlan that I want to prevent from seeing the office network vlan 3
Vlan 3 and Vlan 4 both use the same port to the router, A1.
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:
filter source-port A2 drop E19-E20
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.
yet I can still very easily get to the DB server by it's first name with out any trouble.
so if I go "run -> //mystorage"
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.
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.
Thank you in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-08-2009 10:15 PM
09-08-2009 10:15 PM
Re: Separating VLANS on Procurve 4208
please post a "show running-config" from you switch.
Best regards,
Patrick
Patrick
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-08-2009 10:35 PM
09-08-2009 10:35 PM
Re: Separating VLANS on Procurve 4208
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-09-2009 08:37 AM
09-09-2009 08:37 AM
Re: Separating VLANS on Procurve 4208
Here it is.
Thank you again for any help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-10-2009 12:12 AM
09-10-2009 12:12 AM
SolutionSo all filter rules will have no effect as the ports do not communicate to E19/E20 directly (only through A1).
Look into this router config, maybe you can creat an ACL there.
regards,
Pieter
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP