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

Dynamic Server Port HA #405

Open
vegalou opened this issue Mar 4, 2025 · 0 comments
Open

Dynamic Server Port HA #405

vegalou opened this issue Mar 4, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@vegalou
Copy link

vegalou commented Mar 4, 2025

Feature Proposed
Replacement of HotReload configuration. Server create work port by
Token validation & client config.

Use Case
Server Cluster provides 100,000+ Traverse-NAT easily.

eg: A server side only need a simple config like:

# server.toml
[server]
bind_addr = "0.0.0.0:2333" # `2333` specifies the port that rathole listens for clients
default_token = "use_a_secret_that_only_you_know" 
dynamic_port = 1

Each client was told to use specific avaliable server host, work port after hashatged.

[client]
remote_addr = "example1.com:2333"
default_token = "use_a_secret_that_only_you_know"

[client.services.service1]
dynamic_port = 1
local_addr = "127.0.0.1:554"
server_addr = "8551"

via token validation, server could serve

  • example1.com:8551, example1.com:8552, example1.com:8553.....
  • example2.com:8551, example2.com:8552, example2.com:8553.....

Each Client get indivdual server & work port for Traverse-NAT,

@vegalou vegalou added the enhancement New feature or request label Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant