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

documentation seems a bit unclear #958

Closed
nathanaelle opened this issue Oct 21, 2023 · 2 comments
Closed

documentation seems a bit unclear #958

nathanaelle opened this issue Oct 21, 2023 · 2 comments

Comments

@nathanaelle
Copy link

hi,

this part of the documentation seems unclear for https://www.cni.dev/plugins/current/main/bridge/

vlan (int, optional): assign VLAN tag. Defaults to none.
preserveDefaultVlan (boolean, optional): indicates whether the default vlan must be preserved on the veth end connected to the bridge. Defaults to true.
vlanTrunk (list, optional): assign VLAN trunk tag. Defaults to none.

how to :
– allow packets for/from a vlan and keep incoming tagged aka bridge vlan add vid x dev x ?
– allow packets for/from a vlan and untag incoming aka bridge vlan add vid x dev x untagged ?
– force outgoing untagged packet to be tagged aka bridge vlan add vid x dev x pvid ?
– allow packets for/from a vlan and untag incoming and force outgoing untaged aka bridge vlan add vid x dev x pvid untagged ?

I hope you will understand my issue is not about understanding vlans or linux, but about understanding the doc for transposing a wellknown standard linux command to manage bridges and vlans to a cni configuration

@mlguerrero12
Copy link
Member

mlguerrero12 commented Oct 23, 2023

@nathanaelle, please have a look at containernetworking/cni.dev#134

there is also another issue about the same. #939

@nathanaelle
Copy link
Author

thank you :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants