4 ms·
I have left ngrok for cloudflared. It is really nice if you are already a cloudflare customer and is cheaper last I looked. https://developers.cloudflare.com/
by leetrout 5y ago
I have left ngrok for cloudflared.
It is really nice if you are already a cloudflare customer and is cheaper last I looked.
https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide/ https://developers.cloudflare.com/cloudflare-one/connections...
- MuffinFlavored 5y agoNot sure what this is called but, does this support when the server needs to connect to the client (server has ports open but the client doesn't), so the client connects to the server and then the connection is like... flipped? flippable? basically when I try to connect to 127.0.0.1:4500 as the server, I want it to go to the client (which has a bound server listening on a socket, but is closed port/firewall wise). Is this what "reverse tunneling" is?
- gunapologist99 5y agoI think you want something like the -R switch for the standard openssh client (that is, the ssh command in most Linux distributions -- read man ssh) for this; it allows you to have the remote client connect to your server running on your localhost. While you're reading the man page, also check out -L, which allows you to connect to a remote server through the encrypted tunnel. This is the most common usage. For example, let's say that you have a webserver running remotely that is only listening on localhost. Why would you do this? Let's say that you are running some sort of server management dashboard, but you're not sure how secure it is and you want to only connect to it yourself. Even though it is only listening on localhost, you can still connect to it remotely. From your workstation, ssh -L 9000:localhost:8000 remoteserver This will allow you to open up http://localhost:9000 http://localhost:9000 in your browser and access the remote web server that's listening only on its localhost on port 8000.
- ignoramous 5y agoNot sure if it has a name, but I've seen it called "reverse dialing" (which apparently golang's official build servers use to bust nat & firewalls): https://github.com/inetaf/tcpproxy/issues/8 https://github.com/inetaf/tcpproxy/issues/8