cmd/tailscaled: add ip-rule-pref-base argument that can override the priority of ip rule. #12035
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.
The current IP rule priority setting method is suitable for routing from mwan3 to tailscale, but conversely, it is not suitable for routing tailscale traffic using mwan3. For these cases, we make it possible for users to manually change IP rule priority.
In other words, it makes tailscale capable of operating in a multi-wan environment.
example:
tailscaled --ip-rule-pref-base=5200
(This forces the ip rule priority to be set to 5200 even if mwan3 is set.)