Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend VLAN documentation (drop policy, etc) #779

Open
jovatn opened this issue Oct 29, 2024 · 0 comments
Open

Extend VLAN documentation (drop policy, etc) #779

jovatn opened this issue Oct 29, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@jovatn
Copy link
Contributor

jovatn commented Oct 29, 2024

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.

@jovatn jovatn converted this from a draft issue Oct 29, 2024
@jovatn jovatn added documentation Improvements or additions to documentation triage Pending investigation & classification (CCB) labels Oct 29, 2024
@troglobit troglobit removed the triage Pending investigation & classification (CCB) label Oct 31, 2024
@troglobit troglobit added this to the Infix v24.11 milestone Oct 31, 2024
@jovatn jovatn changed the title Extend VLAN documenation Extend VLAN documentation (drop policy, etc) Nov 4, 2024
@troglobit troglobit modified the milestones: Infix v24.11, Infix v24.12 Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: No status
Development

No branches or pull requests

2 participants