Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat/refactor: support the node-level proxy chain #235

Merged
merged 6 commits into from
Jul 23, 2023
Merged

Conversation

mzz2017
Copy link
Contributor

@mzz2017 mzz2017 commented Jul 23, 2023

Background

This PR implements node-level proxy chain.

See #236

Scheme:

node {
  new_node_name: 'node link 1 (endpoint) -> node link 2 (relay)'
}

Example:

node {
  # case 1: tuic over vless (different nodes)
  chains: 'tuic://my.endpoint.com:18364/xxxxx -> vless://ohmy.relay.com:12212/xxxxx'

  # case 2: socks5 over wss (same server port, so wss is the transport layer)
  chains2: 'socks5://yeeeah.v2raya.org:6999 -> wss://yeeeah.v2raya.org:6999/7cadf625-171c-4002-7abc-257f6485fcc2'
}

Moreover, if you are a subscription maker, you can also use such expressions in your subscription content. And then encode them with base64:

tuic://my_tuic_link -> vmess://my_vmess_link
ss://my_ss_link -> vmess://my_vmess_link

Checklist

Full changelogs

  • [Implement ...]

Test Result

image

Future Work

We need to support the group-level proxy chains:

group1 -> group2

@mzz2017 mzz2017 changed the title feat/refactor: support the chains node feat/refactor: support the node level proxy chains Jul 23, 2023
@mzz2017 mzz2017 changed the title feat/refactor: support the node level proxy chains feat/refactor: support the node-level proxy chains Jul 23, 2023
@mzz2017
Copy link
Contributor Author

mzz2017 commented Jul 23, 2023

Test Result (socks5 + wss):
image

@mzz2017 mzz2017 changed the title feat/refactor: support the node-level proxy chains feat/refactor: support the node-level proxy chain Jul 23, 2023
@mzz2017 mzz2017 added the tested label Jul 23, 2023
dae-prow[bot]
dae-prow bot previously approved these changes Jul 23, 2023
Copy link
Contributor

@dae-prow dae-prow bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧪 Since the PR has been fully tested, please consider merging it.

@piyoki
Copy link
Contributor

piyoki commented Jul 23, 2023

Link to #236

piyoki
piyoki previously approved these changes Jul 23, 2023
Copy link
Contributor

@piyoki piyoki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Working as expected, thanks for the efforts 💪

@mzz2017 mzz2017 dismissed stale reviews from piyoki and dae-prow[bot] via dba272d July 23, 2023 11:58
@mzz2017 mzz2017 requested a review from a team as a code owner July 23, 2023 11:58
@dae-prow
Copy link
Contributor

dae-prow bot commented Jul 23, 2023

❌ Your branch is currently out-of-sync to main. No worry, I will fix it for you.

@mzz2017
Copy link
Contributor Author

mzz2017 commented Jul 23, 2023

Test Result (from CTO):
image

@mzz2017 mzz2017 merged commit a2f7c37 into main Jul 23, 2023
22 checks passed
@mzz2017 mzz2017 deleted the feat_chainproxy_node branch July 23, 2023 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants