Extend VLAN documentation (drop policy, etc) #779
Copy link
Copy link
Closed
Labels
cn:dreamCommon Name: Dream ProjectCommon Name: Dream Projectcn:styxCommon Name: Styx ProjectCommon Name: Styx ProjectdocumentationImprovements or additions to documentationImprovements or additions to documentation
Milestone
Description
Activity
- converted this from a draft issue
on Oct 29, 2024 - addeddocumentationImprovements or additions to documentationImprovements or additions to documentationtriagePending investigation & classification (CCB)Pending investigation & classification (CCB)
on Oct 29, 2024 - removedtriagePending investigation & classification (CCB)Pending investigation & classification (CCB)
on Oct 31, 2024 - changed the title
[-]Extend VLAN documenation[/-][+]Extend VLAN documentation (drop policy, etc)[/+]on Nov 4, 2024 - added a commit that references this issue
on Oct 6, 2026
Metadata
Metadata
Assignees
Labels
cn:dreamCommon Name: Dream ProjectCommon Name: Dream Projectcn:styxCommon Name: Styx ProjectCommon Name: Styx ProjectdocumentationImprovements or additions to documentationImprovements or additions to documentation
Type
Projects
- StatusShow more project fieldsDone
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.
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.