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

Allow replacing tuns.sh tunnels with an optional? flag #168

Open
tionis opened this issue Dec 4, 2024 · 0 comments
Open

Allow replacing tuns.sh tunnels with an optional? flag #168

tionis opened this issue Dec 4, 2024 · 0 comments

Comments

@tionis
Copy link

tionis commented Dec 4, 2024

Currently it can happen that a tunnel is broken due to a network error but does not time out fast enough. In such cases the node might try to reestablish the tunnel and get redirected to a random other one.

It would be nice to be able to specify a flag that kills the old/other connection and takes over the tunnel.

This might also be somewhat related to the load-balancing feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant