- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- ProCurve 1800 - what does "Ingress filtering" opti...
Switches, Hubs, and Modems
1819802
Members
3316
Online
109607
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
- Report Inappropriate Content
09-24-2009 06:59 AM
09-24-2009 06:59 AM
ProCurve 1800 - what does "Ingress filtering" option do?
Could you please explain the functionality of the "Ingress filtering" option on the ProCurve 1800 switch.
According to the Management and Configuration Guide(p.38):
'Ingress Filtering Enabled – If enabled, incoming frames for VLANs
which do not include this ingress port in their member set will be
discarded. (Default: Disabled)'
This would imply that when "Disabled", which is the default setting, tagged frames received on the port would be accepted no matter what VLAN id they contained, even if the port were not a member of that VLAN.
However, the next paragraphs in the same Management and Configuration Guide describing the "Packet Type" option clearly state that in the case of Packet Type "All":
'Tagged packets will be dropped unless the port is a member of the VLAN identified by the VLAN tag in the packet.'
and in the case of Packet Type "Tagged Only":
'Tagged packets will be dropped unless the port is a member of the VLAN identified by the VLAN tag in the packet.'
According to the Management and Configuration Guide(p.38):
'Ingress Filtering Enabled – If enabled, incoming frames for VLANs
which do not include this ingress port in their member set will be
discarded. (Default: Disabled)'
This would imply that when "Disabled", which is the default setting, tagged frames received on the port would be accepted no matter what VLAN id they contained, even if the port were not a member of that VLAN.
However, the next paragraphs in the same Management and Configuration Guide describing the "Packet Type" option clearly state that in the case of Packet Type "All":
'Tagged packets will be dropped unless the port is a member of the VLAN identified by the VLAN tag in the packet.'
and in the case of Packet Type "Tagged Only":
'Tagged packets will be dropped unless the port is a member of the VLAN identified by the VLAN tag in the packet.'
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2009 03:09 PM
10-06-2009 03:09 PM
Re: ProCurve 1800 - what does "Ingress filtering" option do?
I've been wondering this myself. I even looked into it a bit, and when I tested it the switch correctly dropped frames tagged with the wrong vlan in most cases with the setting not making much of a difference.
I say most cases, because the switch did forward broadcast frames (dst ff:ff:ff:ff:ff:ff) with the wrong vlan tag to other vlans (which it should not, of course). I tested this a long time ago though, things may have changed in the mean time.
I say most cases, because the switch did forward broadcast frames (dst ff:ff:ff:ff:ff:ff) with the wrong vlan tag to other vlans (which it should not, of course). I tested this a long time ago though, things may have changed in the mean time.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP