- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Web and Unmanaged
- >
- VLAN ingress filtering
-
-
Forums
- Products
- Servers and Operating Systems
- Storage
- Software
- Services
- HPE GreenLake
- Company
- Events
- Webinars
- Partner Solutions and Certifications
- Local Language
- China - 简体中文
- Japan - 日本語
- Korea - 한국어
- Taiwan - 繁體中文
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Blog, Poland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Forums
-
Blogs
-
Information
-
English
- 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
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-07-2021 09:44 AM - edited 11-07-2021 09:50 AM
11-07-2021 09:44 AM - edited 11-07-2021 09:50 AM
VLAN ingress filtering
In VLAN port config of Procurve 1700-24 (but also in other models, it seems to be a more generic question) I find an "ingress filtering" option that can be enabled for each port. Help says::
Ingress Filtering Enabled - If enabled, incoming frames for VLANs which do not include this ingress port as a member will be discarded. (Default: Disabled)
This would suggest that, with option disabled, these frames are accepted.
But I did some test and it seems not to happen.
I configured ports 1-10 belonging only to VLAN A, and 11-20 belonging only to VLAN B, and leave ingress filtering disabled. Then I connected to port 5 a PC, setting its ethernet card with VLAN B id.
The result is that I cannot reach VLAN B. This is fair to me, by itself: if I set port 5 not belonging to VLAN B it means that I don't want it in VLAN B. But I cannot see the point of "ingress filtering", I'm not able to create a scenario in which results are different with filtering on or off.
A condition where with filtering on I cannot reach something that I can reach with filtering off.
Somewhere I read (it's not my first research on this matter) that this filter acts at ingress, and that frames are filtered on egress anyway.
In this case, I cannot see the point of leaving a frame "go in" and then blocking it. Why should I give hope to that frame and then soon delude it?
If we change point of view, I cannot neither find a positive scenario for "filtering off". Some condition in which filtering on disrupts something legitimate.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2022 Hewlett Packard Enterprise Development LP