Skip to content

Extend VLAN documentation (drop policy, etc) #779

Description

@jovatn

We could add more info on VLAN behavior, for instance regarding isolation.

E.g., consider a VLAN bridge where e0 has PVID 0 and is configured untagged to VLAN 10.

  • Incoming packet with VID 20: Thrown away
  • Incoming packet with VID 0: Priority tagged. Accepted and mapped to VID 10, using packet PCP
  • Incoming packet with VID 10: Accepted. Treated just as the priority tagged packet

Are there differences between SW bridges and bridges with HW offloaded? I believe the behavior above apply both for SW bridges and when offloaded on Marvell Linkstreet.

Activity

  1. converted this from a draft issue on Oct 29, 2024
  2. added
    documentationImprovements or additions to documentation
    triagePending investigation & classification (CCB)
    on Oct 29, 2024
  3. removed
    triagePending investigation & classification (CCB)
    on Oct 31, 2024
  4. added this to the Infix v24.11 milestone on Oct 31, 2024
  5. changed the title [-]Extend VLAN documenation[/-] [+]Extend VLAN documentation (drop policy, etc)[/+] on Nov 4, 2024
  6. modified the milestones: Infix v25.03, FUTURE on Mar 3, 2025
  7. self-assigned this
    on Oct 5, 2026
  8. linked a pull request that will close this issueDoc fixes and more #1690on Oct 6, 2026
  9. added a commit that references this issue on Oct 6, 2026
    1ae6a82
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

cn:dreamCommon Name: Dream Projectcn:styxCommon Name: Styx ProjectdocumentationImprovements or additions to documentation

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions