Extend stats reporting to support custom load-balanced configs with several outbounds #5225
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
…lanced outbounds in them, with tags starting with "proxy" e.g. proxy1, proxy2 (fully compatible with existing configs)
|
Thanks for merging. |
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.
Hello
This pull request makes simple modifications (to a single file) to allow correct stats reporting and display for custom (json) configs with several outbounds (matches any outbound tags starting with
proxyinstead of exact match).Custom (json) configs with several outbounds are used in load-balanced configs. Because now there are several outbounds, a single
proxytag will not suffice and the outbounds might have to be be tagged asproxy1,proxy2,proxy_1,proxy_2, etc. The current v2rayN version cannot handle these cases and reports nothing for their traffic.This pull request remedies the situation by simply aggregating traffic for all such matching outbounds (separately, of course, for uplink and down-link). It was tested and confirmed to work with existing normal configs, custom configs and new load-balanced (multi-outbound) configs.
Thank you.