awesome-tor VS awesome-tunneling

The internet is no longer as peer-to-peer friendly as it once was. Hence the existence of commercially-motivated hacks run by third parties such as hosting, e.g., Cloudflare, etc., including tunneling, e.g., ngrok, etc. Alternatively, Tor relies on third parties but AFAIK it's not so centralised and it's not commercially-motivated.

That is what differentiates it from all the other options. There is no company behind it trying to make money by exploiting internet subscribers trying to connect with each other (not the so-called "tech" company).

Tor can have uses other than the ones normally discussed such as anonymity and evading censorship. Tor can provide reachability without use of commercial eavesdropping third party intermediaries.

For example, one can use Onion Services for advertising open IP:port information that is needed for peer-to-peer connections over other, faster peer-to-peer overlay networks, not the Tor network. The Onion Service can function as the "rendezvous" server for making peer-to-peer connection outside of Tor. Tor's Onion Services can be used to exchange IP:port information for making direct connections over the internet without using Tor. No need to use commercial third parties. Ngrok, Tailscale, etc. all require use of servers run by a commercial third party. Tor does not. There is ample free software that can establish peer-to-peer connections over the internet but in every case it requires some reachable server running this software on the internet, and for most users that means they have to run a server and pay a commercial third party for hosting. Tor has no such requirement.

Imagine being able to share content with family, friends, colleagues without the need for so-called "tech" companies^1 acting as intermediaries ("middlemen"). With a reachable IPv4 address this becomes possible. It would be nice if every home internet access subscriber received a reachable IPv4 address from their ISP. No doubt, some do. But on today's internet most do not. The so-called "tech" companies all have reachable IPv4 addresses. Hence they assume the roles of middlemen and use this position to exploit internet subscribers for profit.

Something like Tor provides a solution. Again, it is not always necessary to route all traffic over Tor. Tor can have other uses. When the goal is simply peer-to-peer connections, Onion Services can be used to bootstrap peer-to-peer overlay connections using the user's choice of software by providing a secure, reliable way to exchange IP:port information. Goal here when using Tor is not anonymity nor censorship evasion, it's reachability. Similarly, goal of peer-to-peer is not necessarily anonymity nor evading censorship either, it's bypassing commercially-motivated, eavesdropping middlemen known as "tech" companies, and avoiding the annoyances of advertising. A possible additional benefot of using Tor in this way is elevated privacy. Google, for example, cannot easily discover Onion Services. No one can discover Onion Services using ICANN DNS.

1. The term "tech" as in "tech company" means a company, usually a website, that collects data from and about people to support the sale of advertising services because advertising services are the only services the company can sell on a scale large enough to sustain a profitable business.

More reading/viewing:

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

Tor Hidden Services (now called "Onion Services")

https://jamielittle.org/2016/08/28/hidden.html

As one author wrote on Github:

"onion-expose is a utility that allows one to easily create and control temporary Tor onion services.

onion-expose can be used for any sort of TCP traffic, from simple HTTP to Internet radio to Minecraft to SSH servers. It can also be used to expose individual files and allow you to request them from another computer.

Why not just use ngrok?

ngrok is nice. But it requires everything to go through a central authority (a potential security issue), and imposes artificial restrictions, such as a limit of one TCP tunnel per user. It also doesn't allow you to expose files easily (you have to set it up yourself)."

https://github.com/ethan2-0/onion-expose

As another Github contributor put it:

"With onionpipe, that service doesn't need a public IPv4 or IPv6 ingress. You can publish services with a globally-unique persistent onion address, and share access securely and privately to your own allowlist of authorized keys.

You don't need to rely on, and share your personal data with for-profit services (like Tailscale, ZeroTier, etc.) to get to it."

https://github.com/cmars/onionpipe

https://news.ycombinator.com/item?id=36734956

https://news.ycombinator.com/item?id=30445421

https://news.ycombinator.com/item?id=29929399

"Finally, onion services are private by default, meaning that users must discover these sites organically, rather than with a search engine." [Small websites with small audiences get buried by advertising-supported search engines anyway.]

https://nymity.ch/onion-services/pdf/sec18-onion-services.pd...

https://media.ccc.de/v/31c3_-_6112_-_en_-_saal_2_-_201412301...

https://wiki.termux.com/wiki/Bypassing_NAT (Termux recommends Tor over Ngrok)

https://github.com/ajvb/awesome-tor

See also awesome-tor.

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...