Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tunnelmole, an ngrok alternative (open source)

softwareengineeringstandard.com

Post reply on HN
Print view View original

81–87 of 87 posts

Re: Tunnelmole, an ngrok alternative (open source)

#81

Post by russorat »

aussieguy1234 wrote: post #22
lxe wrote: post #11

Does it have the same spam prevention policies as ngrok?

In the early days there where several attempts to use Tunnelmole for phishing. When you think about it, a service that hides your IP under a domain that is not yours means you can do whatever you want without risking your own server or domain being taken down for abuse, instead risking my server. So I added code to forward an X-Forwarded-For header, which contains the real IP address of the client. Also random URLs h…

PM from ngrok here. First, awesome project! Love to see new projects and ideas in the space. Fighting phishing (and other abuse) is a constant battle for us. As you may know, we do similar things to publish IP addresses, but we've had to add a bunch of other stuff to combat this over the years. I'm happy to share ideas and collaborate if you want to reach out. russ at ngrok dot com.

Again, super awesome project and great work!

Re: Tunnelmole, an ngrok alternative (open source)

#82

Post by vishalontheline »

aussieguy1234 wrote: post #20
vishalontheline wrote: post #2

Also, Local Tunnel: https://localtunnel.github.io/www/

I tried to test this out. But got blocked when I visited my Public URL by some security warning page around phishing? Which is fair enough, but it wasn't clear to me how I could remove that and get the URL to point to my local server like I wanted. Also, their GitHub project has not been maintained for some time.

Ah that's right!

My apologies - I faced this same issue and completely forgot about it. My use-case was to host a dev server that I can ssh into from anywhere, and host things when needed.

What I eventually ended up doing was:

1. Switched to Cloudflare to manage my DNS.

2. Added a subdomain and pointed my IP address to it.

3. Ran a Cron job that checks my ip address, and if it has changed, I update Cloudflare with the new ip address using the following script: https://gist.github.com/vishaldpatel/fc25ebfc236af43f8453b90...

Re: Tunnelmole, an ngrok alternative (open source)

#83

Post by damacio20 »

winash83 wrote: post #78

I made one too, https://webrelay.dev it’s a fun little project, I added TCP tunnels and a lightweight overlay network as well , basically you can start a port on a remote machine and map it to a local port instead of exposing it publicly.

[flagged]

Re: Tunnelmole, an ngrok alternative (open source)

#84

Post by mrbluecoat »

winash83 wrote: post #78

I made one too, https://webrelay.dev it’s a fun little project, I added TCP tunnels and a lightweight overlay network as well , basically you can start a port on a remote machine and map it to a local port instead of exposing it publicly.

Interesting. Reminds me of https://github.com/hackerschoice/gsocket

Re: Tunnelmole, an ngrok alternative (open source)

#85

Post by willemh »

ctrw wrote: post #36

Or hire a static ip and expose whatever ports you feel like. Its amazing how far we've fallen from the internet of the 90s when you could get this done on most ISPs with all of a phone call.

I’ve been wondering this too. My biggest hesitation is that I don’t want to compromise the security of my local network; especially because it’s not just me using it.

Do you know of any resources that cover how to do the security necessary for hosting at home?

Re: Tunnelmole, an ngrok alternative (open source)

#86

Post by SparkyMcUnicorn »

CGamesPlay wrote: post #47
SparkyMcUnicorn wrote: post #44

Earlier quoted context omitted.

Using tailscale can solve this problem, and that's what I've opted to do since I was using tailscale already.

A (potentially minor) problem with this use case for Tailscale is that we do actually want the forwarded services listening on localhost and not on a different IP address, because browsers treat these as secure contexts without having to fuss with https. I briefly checked the Tailscale userspace docs just now and it seems to expose a SOCKS proxy, meaning that we'd need an extra piece to listen on the desired localhos…

You could also use MagicDNS with https[0], although that might not solve it the way you'd prefer.

[0] https://tailscale.com/kb/1153/enabling-https

Post reply on HN