Add shadowsocks fields to relay list response from the API #7096
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
buggmagnet
approved these changes
Oct 29, 2024
There was a problem hiding this comment.
Reviewed 6 of 8 files at r1, all commit messages.
Reviewable status: 6 of 8 files reviewed, all discussions resolved
buggmagnet
force-pushed
the
add-shadowsocks-fields-to-relay-list-response-from-the-api-ios-713
branch
from
67cfb68
to
dc72b5d
Compare
buggmagnet
deleted the
add-shadowsocks-fields-to-relay-list-response-from-the-api-ios-713
branch
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.
The relay list should contain a couple of new fields for shadowsocks proxying:
shadowsocks_extra_addr_in- a list of additional IP addresses that can be used to reach a specific relay over shadowsocks. This field will be added to a relay struct (wireguard.relays.[*].shadowsocks_extra_addr_in). These IP addresess will have shadowsocks listening on literally every port. These addresses will all be backed by the same relay.shadowsocks_port_ranges- a field in the toplevel wireguard object that represents all the port ranges that shadowsocks will be listening on the default entry IPs for relays.This change is