It doesn't work with dropbear ssh client or the golang standard ssh library https://matt.ucc.asn.au/dropbear/dropbear.html https://pkg.go.dev/golang.org/x/crypto/ssh ./dbclient -R 0.0.0.0:0:localhost:5000 b.pinggy.io -p 7878 ./dbclient: Remote TCP forward request failed (port 0 -> localhost:5000) I wanted to try and build a simple golang library for users to add tunnel functionality to their apps while testing, pleas…
Show HN: Quick tunnels to localhost with one command and no binary download
41–46 of 46 posts
Re: Show HN: Quick tunnels to localhost with one command and no binary download
#42Could you consider allowing for ports other than 7878? Would be nice in restricted network environments. Like that of my company; it's allowing only the more common ports to WAN.
Re: Show HN: Quick tunnels to localhost with one command and no binary download
#43One of the ways to extend the functionality of the service without requiring a binary client is to present a text UI over ssh.
Thank a lot for this pointer. We are trying to find out a safe way of enabling a text UI through ssh.
Re: Show HN: Quick tunnels to localhost with one command and no binary download
#44Great service! Could you consider allowing for ports other than 7878? Would be nice in restricted network environments. Like that of my company; it's allowing only the more common ports to WAN.
https://join.slack.com/t/pinggycommunity/shared_invite/zt-1n...
Re: Show HN: Quick tunnels to localhost with one command and no binary download
#45Great service! Could you consider allowing for ports other than 7878? Would be nice in restricted network environments. Like that of my company; it's allowing only the more common ports to WAN.
Would port 443 work for you. Feel free to join our slack to discuss. https://join.slack.com/t/pinggycommunity/shared_invite/zt-1n...
Re: Show HN: Quick tunnels to localhost with one command and no binary download
#46Earlier quoted context omitted.
This is not a SSH server. Yes, you can run your own SSH server at a persistent domain. But if you could run a SSH server with a persistent domain then you would not use Ngrok also right? The value is in getting public URLs for sharing your localhost instantly without any infrastructure or software setup.
You can run the same command against any default configured ssh server. I have never heard of ngrok, and have used ssh tunnels for over a decade. I must be missing something.
So, for example, if you are hosting a web server locally on port 8080, you could ssh to a service like this, and then it would give you back a link such as h59dke4.example.com.
All traffic that goes to h59dke4.example.com:80 will actually be routed to your 127.0.0.1:8080