feat: scope vless flow with flow_inbound_tags
#908
Conversation
This file contains hidden or 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
This commit refines the handling of the VLESS `flow` setting. - The `flow` parameter is now selectively removed from VLESS configurations when TLS is not enabled. - For subscriptions, `flow` is now applied only to the specific inbound it's configured for, by checking against `flow_inbound_tags`. - Shared links will now correctly include the `flow` parameter only when the inbound tag matches. - Updated the frontend submodule to include related UI changes.
Author
|
It may fix the limitation in issue #529. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem:
flowwas specified, all of that user'svlessoutbounds that use TLS would inherit and use the sameflow. This made it impossible to scopeflowto specific inbounds and could causeflowto appear on unintended inbounds.Solution:
flow_inbound_tagsto allow admins to scope a user'sflowto specific inbound tags. Behavior rules:flowis non-empty andflow_inbound_tagsis empty, behavior is unchanged: all of the user's TLSvlessoutbounds will useflow.flowis non-empty andflow_inbound_tagscontains tags, only TLSvlessoutbounds whose inbound tag matches one of the listed tags will haveflowapplied.