VLAN encap: none #23
Merged
VLAN encap: none #23
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
Per the BPF program gtp_fwd.bpf encap VLAN is optional. If 0, it means no VLAN header. So let's support the same from the CLI. For debugging, let's dump all the content of the BPF map. TODO: write terminal keep dumping 1 single gtpu-ipip tunnel for the latest traffic-selector. Since the map could have many traffic-selector, the write terminal should vty_out all the entries. re-issuing the same CLI gtpu-ipip traffic-select N command does lead to an error since it is processed as an ADD rule instead of an UPDATE rule. add `no gtpu-ipip traffic-selector` in order to drop some.
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.
Add the support for no incoming VLAN.
TBD: should we have a CLI command for the egress VLAN ?