Feature to support mixed access and vlan interfaces in a switch #573
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Minimalist implementation of the possibility to add access interfaces and vlan tagged interfaces into the same switch. Eg.: ``` pasztor@host:~ $ sudo vm switch list NAME TYPE IFACE ADDRESS PRIVATE MTU VLAN PORTS test standard vm-test - no - - vxlan42 epair0b.1042 ``` vxlan42 is created using rc.conf's cloned interfaces and it doesn't need .1q tagging, but the other member port on epair0b it ineed needs it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minimalist implementation of the possibility to add access interfaces and vlan tagged interfaces into the same switch.
Eg.:
vxlan42 is created using rc.conf's cloned interfaces and it doesn't need .1q tagging, but the other member port on epair0b it ineed needs it.
Thoroughly tested and proven to work.