ipns-link VS awesome-tunneling

I saw this project, IPNS-Link, that seems promising, but I wasn't able to make it work yet and seems to require specialised IPNS-Link gateways, they can't use just any IPFS gateway, and their freely available gateways seem to be all down rn, so I'd probably have to host my own gateway anyways.

You might wanna take a look at ipns-link.

Install and run a free and open-source app on your local server (the Pi in your case), following this easy tutorial.

We welcome you to implement the IPNS-Link project, especially the Gateway, in a proper server-side language - be it Go, JS, Rust, Ruby, Python - whatever you are good at. The existing prototype, in the spirit of playful experimentation, has been rather hurriedly hacked in Bash 🙈. Thankfully, it works! But of course, we need to evolve.

Loading an ipns-link-exposed website for the first time might take a while. This is because the Gateway has to locate your site and peer with its host node. Subsequent requests for the site, however, are served faster because the Gateway maintains persistent peering with the site's host node.

Here's an overview and a quick-start tutorial. And here's a prototype gateway.

The static blue background is missing. This might happen due to the following. The background is embedded in the html and sourced from a root-relative URL. Now, being a path-gateway, ipns-link.herokuapp.com requires the Referer header (with absolute URL) in the http request, so that it can resolve the PeerID when requested a relative path without the /ipns/PeerID prefix. Although the Gateway wants a complete referrer URL, the embedded tags may override it with a different ReferrerPolicy. If overridden in this way, the Gateway can't resolve the PeerID and fails. NOTE: this problem WILL GO AWAY once the IPNS-Link-GATEWAY supports wildcard subdomains, hopefully in the near future. Then, there wouldn't be any dependence on the Referer or cookie or server-side cache for resolving root-relative URLs, and everything would work as intended. Subdomain Gateway has always been the end-goal, but due to the lack of a domain I went with a path-gateway for prototyping.

https://github.com/anderspitman/awesome-tunneling

awesome-tunneling lists a number of ngrok alternatives: https://github.com/anderspitman/awesome-tunneling

- https://news.ycombinator.com/item?id=39754786

- FWIU headscale works with the tailscale client and supports MagicDNS

There are a whole bunch of alternatives too - https://github.com/anderspitman/awesome-tunneling. I will advocate for zrok.io as I work on its parent project, OpenZiti. zrok is open source and has a free SaaS as well as more built in security.

https://github.com/anderspitman/awesome-tunneling. Seems similar to zrok.io, ngrok, cloudflare tunnels, tailscale funnels and zrok although you're using http/3 explicitly.

Personally I work on two similar projects you might want to check out: zrok and OpenZiti. Similar projects, but zrok is closest to what you did here.

Thanks for the history. I maintain this list[0], and wasn't aware of OG localtunnel, likely because there's a somewhat newer and now more popular project with the same name[1]. You appear to be correct on timing. Here's the earliest commits on GitHub for each of the projects:

OG localtunnel (2010): https://github.com/progrium/localtunnel/tree/fb82920d9d3e538...

Other localtunnel (2012): https://github.com/localtunnel/localtunnel/tree/93d62b9dbb9f...

ngrok (2012): https://github.com/inconshreveable/ngrok/tree/8f4795ecac7f92...

I'll see that OG localtunnel gets added to the list for posterity.

[0]: https://github.com/anderspitman/awesome-tunneling

[1]: https://github.com/localtunnel/localtunnel

I haven't tried vscode forwarding. What features does it have that are missing from most of the options on the list[0]?

If you want a nice GUI for remote managing maybe check out one of my tools, boringproxy

[0]: https://github.com/anderspitman/awesome-tunneling

I maintain this list:

https://github.com/anderspitman/awesome-tunneling

Your use case sounds interesting and there may be a tool out there that will do it, but I can't quite wrap my head around your description of how everything is connected and what runs where with your current setup.

I agree with sibling that my main question is what prevents you from using SSHFS or similar?

I'm starting to try to get into Cloudflare tunnel, Tailscale funnel and other alternatives. What I need is my services to be accessible without any installation client-side, and I'm unsure what services provide this. I also looked at solutions like BoringProxy, TunnelMole from this page : https://github.com/anderspitman/awesome-tunneling My goal is to have my current domain rented at OVH pointing to my server to make it as much like before as possible.

Here's a list of options to get around CGNAT: https://github.com/anderspitman/awesome-tunneling

We have a section for overlay networks on the tunneling list[0] I maintain. This is a very interesting space with some excellent software.

I certainly have my gripes about the closed nature of Slack itself, in particular using a closed protocol when the model is clearly "federated" between multiple servers internally. That said, the contribution of something on the scale and quality of Nebula back to the open source community is hard to argue with.

[0]: https://github.com/anderspitman/awesome-tunneling#overlay-ne...