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

Feature request on more tunneling options #340

Open
KasRoudra opened this issue Jan 25, 2022 · 3 comments
Open

Feature request on more tunneling options #340

KasRoudra opened this issue Jan 25, 2022 · 3 comments

Comments

@KasRoudra
Copy link

Feature Request

A clear description of what the feature request is

Currently seeker has only one tunneler serveo which is buggy. So, are you planning to add some new tunnelers like cloudflared or ngrok as built in support? You can keep this simple version of seeker in main branch and open a new branch where seeker contains three or more tunnelers. If you agree I will start working on this extended seeker


@thewhiteh4t
Copy link
Owner

@KasRoudra serveo will be removed in a future update which is coming soon, I dont plan on adding any tunnel options in the tool itself, seeker is for advanced users who can easily open a second terminal and use a service of their choice. The approach of adding inbuilt support for tunnel services is not a good way forward as it is difficult to cover all device architectures for example in the case of ngrok, and most tools which are using this approach are buggy as well. I think opening a second terminal and running a tunnel service isnt hard at all and if someone is struggling with this then they should not be using the tool in the first place, it clearly shows that they lack basic linux knowledge and are directly jumping to tools which is not a good approach

@thewhiteh4t
Copy link
Owner

i can add usage instructions for various tunnel services though that should be useful. Other than that if a tunnel service does not require binaries then maybe I will think about adding built in support for them

@KasRoudra
Copy link
Author

@thewhiteh4t Thank you for fast response. I agree that those who can't use ngrok or cloudflared in second terminal, shouldn't use seeker. But still we can keep a seeker which can handle everything alone without any second terminal. Current seeker is lightweight and do not contain any binaries. We mustn't change it. Rather, I was suggesting for a new branch where the experimental seeker will remain. Currently, tunnelers have support for common 3-4 architectures. Only one or two might be missing. Although not completely free from bug, cloudflared showed less error than ngrok.

Here is a demo

Screenshot_2022-01-24-20-50-41

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

2 participants