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

Add IDs to client tunnel workers, more tunnel features. #606

Closed
davidnewhall opened this issue Sep 20, 2023 · 2 comments · Fixed by #654 or #712
Closed

Add IDs to client tunnel workers, more tunnel features. #606

davidnewhall opened this issue Sep 20, 2023 · 2 comments · Fixed by #654 or #712
Labels
enhancement New feature or application improvement

Comments

@davidnewhall
Copy link
Contributor

davidnewhall commented Sep 20, 2023

When a client makes multiple connections to a tunnel, the connections are indistinguishable in logs. Add IDs and print them.

Other features to look into:

  • Make sure a client tunnel can be reloaded instantly through an api hit.
  • If a tunnel stays down for more than N minutes, re-check client info for a new tunnel.
@davidnewhall
Copy link
Contributor Author

Do the last two bullet points.

@davidnewhall davidnewhall reopened this Mar 11, 2024
@davidnewhall davidnewhall added the enhancement New feature or application improvement label Apr 14, 2024
@davidnewhall
Copy link
Contributor Author

Okay here's the idea. If a tunnel becomes unreachable for some amount of time, or retry-count, then hit another tunnel, begin moving through the entire list of tunnels until one of them works. Once a tunnel works, send an api request to the website to update the active tunnel. This api endpoint needs to be created.

Nice to have:

  • Client UI may show all tunnels.
  • UI may provide an interface to ping all tunnels and pick a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or application improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant