Compare commits
180 commits
add-teleco
...
master
| Author | SHA1 | Date | |
|---|---|---|---|
|
414af75985 | ||
|
a00f7987c8 | ||
|
|
28c9206b65 | ||
|
|
0d8c3cacd1 | ||
|
|
90c1ea87b7 | ||
|
|
0a2f9464ea | ||
|
|
8f495c47e1 | ||
|
cc7696879c | ||
|
73bdf90452 | ||
|
|
d80f3db407 | ||
|
|
f9c00ae003 | ||
|
14dc706c62 | ||
|
|
a73f7b1496 | ||
|
7c39beb74b | ||
|
|
17a41fc781 | ||
|
|
3f710dd56f | ||
|
|
9c78777d88 | ||
|
|
733d7fe189 | ||
|
38cc9e8af0 | ||
|
|
4b1c765753 | ||
|
72e56d663b | ||
|
f1a46a2aee | ||
|
679cea363a | ||
|
|
a8722897c8 | ||
|
|
f619cecb49 | ||
|
|
a95f7f98b7 | ||
|
|
77ea89b786 | ||
|
|
9418047c96 | ||
|
|
a12ff84223 | ||
|
|
da22185b02 | ||
|
|
ac86cd48a8 | ||
|
|
ba36c80a90 | ||
|
|
c214326d0a | ||
|
|
66511fd23c | ||
|
|
df1df04bf7 | ||
|
|
91cfcd1b21 | ||
|
|
6e7fc26e10 | ||
|
5f6e551434 | ||
|
|
b7908362e9 | ||
|
|
bb9e0c2932 | ||
|
|
706bdedfa9 | ||
|
ab4f39a79c | ||
|
|
2d6f10c7cd | ||
|
|
9dad64945b | ||
|
|
18483572c9 | ||
|
|
62006a86f2 | ||
|
|
679be61729 | ||
|
e29caea3a4 | ||
|
48cdfcf0c2 | ||
|
17a507a87f | ||
|
|
d4e76ecc0a | ||
|
|
4f275cbc4d | ||
|
|
90705bd225 | ||
|
|
0c044612b9 | ||
|
52b302d234 | ||
|
|
5dbd1a558e | ||
|
|
d8576c6e91 | ||
|
dd4aba892e | ||
|
0dccabe113 | ||
|
|
1d28f7f0d8 | ||
|
cc0dc1fc72 | ||
|
410e4a0491 | ||
|
1813a1c9eb | ||
|
|
292688ab10 | ||
|
|
977ea96fb6 | ||
|
|
98f78f2b91 | ||
|
|
23ed96db85 | ||
|
|
0e7bd5fa11 | ||
|
|
118eaf60e6 | ||
|
|
bd5d7bd11e | ||
|
|
36c0a0eaf8 | ||
|
|
300808c767 | ||
|
|
c586a031f2 | ||
|
|
cbce4f8838 | ||
|
|
391197c4f4 | ||
|
|
48ff00f44b | ||
|
72ecf887cc | ||
|
|
7ed3da6f1f | ||
|
|
9982440f06 | ||
|
|
c60a2961de | ||
|
|
3bb1c2b7b7 | ||
|
|
46b76e44fc | ||
|
|
519dfdb7d0 | ||
|
|
9bc26aa0fa | ||
|
|
d5a58192dd | ||
|
|
089ec503a9 | ||
|
|
28a74ddf46 | ||
|
|
3d0472264e | ||
|
|
694abdd857 | ||
|
|
70e8500475 | ||
|
|
de37ff5e23 | ||
|
|
6b7fb71b14 | ||
|
|
eee461693c | ||
|
d6dfbc736c | ||
|
|
7dff72735d | ||
|
c3a7951594 | ||
|
c8ed7d31c9 | ||
|
|
710bf1e051 | ||
|
01833efdc7 | ||
|
|
17aad50fd0 | ||
|
95f1d0aa90 | ||
|
|
988f009433 | ||
|
|
0a9be49b4c | ||
|
|
54dd42dd9f | ||
|
|
5e2e619989 | ||
|
|
ff1016847b | ||
|
|
1ce6309e05 | ||
|
|
c12a67a827 | ||
|
|
013e79c342 | ||
|
|
891244c767 | ||
|
|
e059960042 | ||
|
|
f82c28b287 | ||
|
|
03fa43cbe9 | ||
|
|
573cfebf3b | ||
|
|
2dfaedfbba | ||
|
|
97eb26b87b | ||
|
|
30eba7d2a0 | ||
|
|
db2be4dbe0 | ||
|
|
3b674b978e | ||
|
|
29673e0512 | ||
|
|
40b16dd18d | ||
|
|
35b0926b8e | ||
|
|
b6548dfa97 | ||
|
|
03cb824ed3 | ||
|
|
1eff24fe54 | ||
|
a822851424 | ||
|
|
5502b6ef0c | ||
|
|
b07b2384e7 | ||
|
|
6cc5b2c8f5 | ||
|
|
d6e945d236 | ||
|
|
3fef1ed1ee | ||
|
57a5934a5f | ||
|
477b30fa74 | ||
|
|
89a1f28f79 | ||
|
|
777c39d889 | ||
|
|
0671e12d78 | ||
|
|
c2ff3b8415 | ||
|
|
08769b8ed6 | ||
|
|
fd3fb28e6a | ||
|
|
6fbb1a861b | ||
|
|
8953e465ad | ||
|
|
4a64621922 | ||
|
|
95f1e6b005 | ||
|
528e322f84 | ||
|
|
9773ff8209 | ||
|
|
77ca188abc | ||
|
|
98896db4c9 | ||
|
7ef6a1ec63 | ||
|
|
4b505d7d70 | ||
|
|
8160115d06 | ||
|
|
a8bb18cc84 | ||
|
|
f31fad77ee | ||
|
|
26aab940b5 | ||
|
|
b4683ceb33 | ||
|
|
19871265fc | ||
|
|
31b73cddd2 | ||
|
|
85a39fc9cf | ||
|
|
974aaf788f | ||
|
|
4e58848e6b | ||
|
|
9b58e95b86 | ||
|
|
630f975eb9 | ||
|
|
cc8939464c | ||
|
|
5652e9015b | ||
|
|
ba4a6e31fd | ||
|
|
dd43d49511 | ||
|
|
50643f1274 | ||
|
|
63ae46f4d3 | ||
|
|
4345e7aacb | ||
|
|
b2580700a6 | ||
|
|
f8ab8a0ac6 | ||
|
ca6d35c1ac | ||
|
|
257da79388 | ||
|
|
0ef4c926dc | ||
|
|
1942856c09 | ||
|
|
fd4c9c6c68 | ||
|
|
955a09b3ce | ||
|
|
f000a2087d | ||
|
|
5dd80624ee | ||
|
|
bc6c280850 | ||
|
|
025e375000 |
1 changed files with 95 additions and 36 deletions
129
README.md
129
README.md
|
|
@ -1,66 +1,125 @@
|
|||
The purpose of this list is to track and compare tunneling solutions. This is
|
||||
primarily targeting toward developers and self-hosters who want to do things
|
||||
like exposing a local webserver via a public address.
|
||||
primarily targeted toward self-hosters and developers who want to do things
|
||||
like exposing a local webserver via a public domain name, with automatic HTTPS,
|
||||
even if behind a NAT or other restricted network.
|
||||
|
||||
**NOTE:** We're building a community around self-hosting, data ownership, and decentralization in general.
|
||||
Join us over at [IndieBits.io](https://forum.indiebits.io).
|
||||
|
||||
# The dream
|
||||
|
||||
I started this list because I'm looking for a simple tool/service that does the
|
||||
following:
|
||||
|
||||
* Allows me to register a domain name.
|
||||
* Automatically sets up HTTPS (apex and wildcard) for the domain.
|
||||
* Provides a client tool that tunnels TCP connects through the server without
|
||||
requiring root on the client.
|
||||
* Provides a web interface to allow me to map X domain/subdomain to Y port on
|
||||
Z client, and proxy all connections to that domain.
|
||||
* Allows me to register a domain name and automatically points the records at
|
||||
the server running the tunnels.
|
||||
* Automatically sets up and manages HTTPS certificates (apex and subdomains)
|
||||
for the domain.
|
||||
* Provides a client tool that tunnels HTTP/TCP connections through the server
|
||||
without requiring root on the client.
|
||||
* Provides a simple GUI interface to allow me to map X domain/subdomain to Y port
|
||||
on Z client, and proxy all connections to that domain.
|
||||
|
||||
So far I haven't found it so I've started building it myself.
|
||||
So far I haven't found a tool that does all of this. In particular, while some
|
||||
of them can do automatic certs through Lets's Encrypt, none of them integrate
|
||||
the domain registration and DNS management.
|
||||
|
||||
**UPDATE 2022-09-23:**
|
||||
|
||||
# Things to look out for when comparing solutions
|
||||
A lot of new tools have been developed since the list started, and many tools have been submitted for addition to the list. It's great to see so much interest in tunneling. That said, I want to make sure this remains a useful resource for not just listing all the possible options, but helping people pick one that will solve their problem. With that goal in mind, I've moved some of the items to a separate section at the bottom. This is dedicated to more complicated tools like overlay networks which can support tunneling and similar use cases, but aren't focused exclusively on tunneling. Please let me know if you think something is in the wrong section.
|
||||
|
||||
* Underlying multiplexing technology. In particular, if a solution uses
|
||||
TCP-over-TCP (ie any of them that are built on SSH), it'll be subject to
|
||||
rather severe [issues](http://sites.inka.de/bigred/devel/tcp-tcp.html).
|
||||
* Source code availability. Some of the best options are closed source only.
|
||||
* Does it require root to run the client? For example, anything built on
|
||||
WireGuard will likely have great performance (on systems where it's built
|
||||
into the kernel at least), but typically requires elevated permissions to
|
||||
create the tun devices.
|
||||
# Recommendations
|
||||
|
||||
* For most people, I currently recommend [CloudFlare Tunnel](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/). Although it's closed source, this is the production-quality service that gets the closest to achieving the dream. It's also a loss-leader for CloudFlare's other products which means they can offer it for free.
|
||||
* If you want to self-host, there are many options. For something production ready [frp](https://github.com/fatedier/frp) is probably what you want. If you're a developer, I'd recommend starting with my own [SirTunnel](https://github.com/anderspitman/SirTunnel) project and modifying it for your needs. For non-developers and those wanting more of a GUI experience, I created [boringproxy](https://boringproxy.io/). It's my take on a comprehensive tunnel proxy solution. It's in beta but currently solves almost everything I want. Once the server is running this is a very easy tool to use and has some nice features.
|
||||
|
||||
# The list
|
||||
|
||||
# Open source
|
||||
|
||||
* [frp](https://github.com/fatedier/frp) [](https://github.com/fatedier/frp/stargazers) - Seems to be a pretty comprehensive open alternative to ngrok.
|
||||
# Open source (at least with a reasonably permissive license)
|
||||
* [Tunnelmole](https://github.com/robbie-cahill/tunnelmole-client/) - Open source and optionally self hostable. The client and server are both written in TypeScript.
|
||||
* [Telebit](https://telebit.cloud/) - Written in JS. [Code](https://git.coolaj86.com/coolaj86/telebit.js).
|
||||
* [tunnel.pyjam.as](https://tunnel.pyjam.as/) - No custom client; uses WireGuard directly instead. Written in Python. [source code](https://gitlab.com/pyjam.as/tunnel)
|
||||
* [SSH-J.com](https://bitbucket.org/ValdikSS/dropbear-sshj/) - Public SSH Jump & Port Forwarding server. No software, no registration, just an anonymous SSH server for forwarding. Users are encouraged to use it for SSH exposure only, to preserve end-to-end encryption. No public ports, only in-SSH connectivity. Run `ssh ssh-j.com` and it will display usage information.
|
||||
* [frp](https://github.com/fatedier/frp) [](https://github.com/fatedier/frp/stargazers) - Comprehensive open alternative to ngrok. Supports UDP, and has a P2P mode. Supports multiplexing over TCP (single connection or pool), QUIC, and KCP.
|
||||
* [ngrok 1.0](https://github.com/inconshreveable/ngrok) [](https://github.com/inconshreveable/ngrok/stargazers) - Original version of ngrok. No longer developed in favor of the commercial 2.0 version.
|
||||
* [localtunnel](https://github.com/localtunnel) [](https://github.com/localtunnel/localtunnel/stargazers) - Written in node. Popular suggestion.
|
||||
* [inlets](https://github.com/inlets) [](https://github.com/inlets/inlets/stargazers) - Open source ngrok alternative. Has pro option.
|
||||
* [sshuttle](https://github.com/sshuttle/sshuttle) [](https://github.com/sshuttle/sshuttle/stargazers) - Open source project originally from one of the founders of Tailscale. Server doesn't require root; client does. Explicitly designed to avoid TCP-over-TCP issues.
|
||||
* [chisel](https://github.com/jpillora/chisel) [](https://github.com/jpillora/chisel/stargazers) - Another HTTPS+SSH option.
|
||||
* [chisel](https://github.com/jpillora/chisel) [](https://github.com/jpillora/chisel/stargazers) - SSH under the hood, but still uses a custom client binary. Supports auto certs from LetsEncrypt. Written in Go.
|
||||
* [bore](https://github.com/ekzhang/bore) [](https://github.com/ekzhang/bore/stargazers) - Minimal tunneling solution. MIT Licensed. Written in Rust.
|
||||
* [rathole](https://github.com/rapiz1/rathole) [](https://github.com/rapiz1/rathole/stargazers) - Similar to frp, including the config format, but with improved performance. Low resource consumption. Hot reload. Written in Rust.
|
||||
* [expose](https://github.com/beyondcode/expose) [](https://github.com/beyondcode/expose/stargazers) - ngrok alternative written in PHP.
|
||||
* [teleconsole](https://www.teleconsole.com/) [](https://github.com/gravitational/teleconsole/stargazers) - SSH-based, but uses special client script. Focused on forwarding SSH console sessions, but can also forward ports.
|
||||
* [go-http-tunnel](https://github.com/mmatczuk/go-http-tunnel) [](https://github.com/mmatczuk/go-http-tunnel/stargazers) - Uses a single HTTP/2 connection for muxing, so likely avoids TCP-over-TCP issues. Need to manually generate certs for server and clients.
|
||||
* [sish](https://github.com/antoniomika/sish) [](https://github.com/antoniomika/sish/stargazers) - Open source ngrok/serveo alternative. SSH-based but uses a custom server written in Go. Supports WebSocket tunneling.
|
||||
* [go-http-tunnel](https://github.com/mmatczuk/go-http-tunnel) [](https://github.com/mmatczuk/go-http-tunnel/stargazers) - Uses a single HTTP/2 connection for muxing. Need to manually generate certs for server and clients.
|
||||
* [pgrok/pgrok](https://github.com/pgrok/pgrok) [](https://github.com/pgrok/pgrok/stargazers) - A multi-tenant HTTP reverse tunnel solution through SSH remote port forwarding.
|
||||
* [tunnelto](https://tunnelto.dev/) [](https://github.com/agrinman/tunnelto/stargazers) - Open source (MIT). Written in Rust.
|
||||
* [wstunnel](https://github.com/erebe/wstunnel) [](https://github.com/erebe/wstunnel/stargazers) - Proxies over WebSockets. Focus on proxying from behind networks that block certain protocols. Written in Haskell with executables provided.
|
||||
* [zrok](https://zrok.io/) [](https://github.com/openziti/zrok/stargazers) - Aims for effortless sharing both publicly and privately. Supports multiple types of resources, including HTTP endpoints and files. Built on OpenZiti (see overlay section below). Apache 2 License. Written in Go.
|
||||
* [boringproxy](https://boringproxy.io/) [](https://github.com/boringproxy/boringproxy/stargazers) - Designed to be very easy to use. No config files. Clients can be remote-controlled through a simple WebUI and/or REST API on the server.
|
||||
* [SirTunnel](https://github.com/anderspitman/SirTunnel) [](https://github.com/anderspitman/SirTunnel/stargazers) - Minimal, self-hosted, 0-config alternative to ngrok. Similar to sish but leverages Caddy+OpenSSH rather than custom server code.
|
||||
* [jprq](https://github.com/azimjohn/jprq) [](https://github.com/azimjohn/jprq/stargazers) - Proxies over WebSockets. Written in Python.
|
||||
* [PageKite](https://pagekite.net/) [](https://github.com/pagekite/PyPagekite/stargazers) - Comprehensive open source solution with hosted options.
|
||||
* [slt](https://github.com/inconshreveable/slt) [](https://github.com/inconshreveable/slt/stargazers) - Open source TLS proxy from the creator of ngrok. Supports SNI.
|
||||
* [Wiretap](https://github.com/sandialabs/wiretap) [](https://github.com/sandialabs/wiretap/stargazers) - Transparent tunneling over WireGuard (UDP) using userspace network stack. Root not required on server. Supports multiple clients and servers. Written in Go.
|
||||
* [Crowbar](https://github.com/q3k/crowbar) [](https://github.com/q3k/crowbar/stargazers) - Tunnels TCP connections over HTTP GET and POST requests.
|
||||
* [tunneller](https://github.com/skx/tunneller) [](https://github.com/skx/tunneller/stargazers) - Open source. Written in Go.
|
||||
* [onionpipe](https://github.com/cmars/onionpipe) [](https://github.com/cmars/onionpipe/stargazers) - Onion addresses for anything. `onionpipe` forwards ports on the local host to remote Onion addresses as Tor hidden services and vice-versa. Written in Go.
|
||||
* [tunnel](https://github.com/koding/tunnel) [](https://github.com/koding/tunnel/stargazers) - This one is a Golang library, not a program you can just run. However, it looks easy to use for creating custom solutions. Uses a single TCP socket, and [yamux](https://github.com/hashicorp/yamux) for multiplexing.
|
||||
* [jerson/pgrok](https://www.proxy.jetzt/) [](https://github.com/jerson/pgrok/stargazers) - Fork of ngrok 1.0, with more recent commits. Archived.
|
||||
* [docker-tunnel](https://github.com/vitobotta/docker-tunnel) [](https://github.com/vitobotta/docker-tunnel/stargazers) - Simple Docker-based nginx+SSH solution.
|
||||
* [holepunch.io](https://holepunch.io) [](https://github.com/CypherpunkArmory/holepunch/stargazers) - Has nice hosted solution. Uses SSH for muxing.
|
||||
* [Telebit](https://telebit.cloud/) - Written in JS. [Code](https://git.coolaj86.com/coolaj86/telebit.js).
|
||||
* [remotemoe](https://github.com/fasmide/remotemoe) [](https://github.com/fasmide/remotemoe/stargazers) - SSH-based, with custom golang server. Does some cool unique things. Instead of just plain tunnels, it drops you into a basic CLI UI that offers several useful commands interactively, such as adding a custom hostname. Also allows end-to-end encryption for both HTTPS and upstream SSH. Doesn't appear to offer non-e2e HTTPS, ie no auto Let's Encrypt support.
|
||||
* [hypertunnel](https://github.com/berstend/hypertunnel) [](https://github.com//berstend/hypertunnel/stargazers) - Public server appears to be down. MIT Licensed. Written in JavaScript.
|
||||
* [tunwg](https://github.com/ntnj/tunwg) [](https://github.com/ntnj/tunwg/stargazers) - Wireguard in userspace based. Offers end to end encrypted TLS with LetsEncrypt certificates generated automatically by clients, with support for custom domains. Server can be self-hosted and doesn't require storing any data.
|
||||
* [gt](https://github.com/ao-space/gt)[](https://github.com/ao-space/gt/stargazers) - Supports peer-to-peer direct connection (P2P) and Internet relay. Focus on performance. Written in Go.
|
||||
* [holepunch](https://github.com/CypherpunkArmory/holepunch) [](https://github.com/CypherpunkArmory/holepunch/stargazers) - Has nice hosted solution. Uses SSH for muxing.
|
||||
* [StaqLab Tunnel](https://tunnel.staqlab.com/) [](https://github.com/abhishekq61/tunnel-client/stargazers) - SSH-based. Client is open source. Server doesn't appear to be.
|
||||
* [tnnlink](https://github.com/LiljebergXYZ/tnnlink) [](https://github.com/LiljebergXYZ/tnnlink/stargazers) - SSH-based. Golang. Not maintained.
|
||||
* [docker-wireguard-tunnel](https://github.com/DigitallyRefined/docker-wireguard-tunnel) [](https://github.com/DigitallyRefined/docker-wireguard-tunnel/stargazers) - Connect two or more Docker servers together sharing container ports between them via a WireGuard tunnel.
|
||||
* [ngtor](https://github.com/theborakompanioni/ngtor) [](https://github.com/theborakompanioni/ngtor/stargazers) - Easily expose local services via Tor. Written in Java.
|
||||
* [Punchmole](https://github.com/Degola/punchmole/) [](https://github.com/Degola/punchmole/stargazers) - Can be integrated directly into an existing Node.js project. Written in JavaScript.
|
||||
|
||||
# Commerical/Closed source
|
||||
|
||||
# Commercial/Closed source
|
||||
|
||||
* [ngrok 2.0](https://ngrok.com/) - Probably the gold standard and most popular. Closed source. Lots of features, including TLS and TCP tunnels. Doesn't require root to run client.
|
||||
* [CloudFlare Argo Tunnel](https://www.cloudflare.com/products/argo-tunnel/) - $5/mo + $0.1/GB. Integrates with Argo smart routing. Client source code is [available](https://github.com/cloudflare/cloudflared).
|
||||
* [serveo](https://serveo.net) - Mentioned quite a bit the last couple years, but appears to be down currently. Simply uses SSH for tunneling.
|
||||
* [Tailscale](https://www.tailscale.com/) - Built on WireGuard. Closed source. Easy to use. Doesn't include an HTTPS proxy on the public side, but could be combined with nginx/Caddy/etc.
|
||||
* [CloudFlare Tunnel](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup) - Excellent free option. Nicely integrates tunneling with the rest of Cloudflare's products, which include DNS and auto HTTPS. Client [source code](https://github.com/cloudflare/cloudflared) is Apache 2.0 licensed and written in Golang.
|
||||
* [Beeceptor](https://beeceptor.com/) - Goes beyond tunneling. Rest API mocking and intercepting tool. You can view the live requests and send mocked response. Written in JavaScript.
|
||||
* [Pinggy](https://pinggy.io/) - SSH based single command HTTPS / TCP / TLS tunnels, no downloads required. Rich terminal interface and a web debugger. Free tier - 60 min timeout. Paid tier allows custom domains with built-in Let's Encrypt certificates.
|
||||
* [Loophole](https://loophole.cloud/) - Offers end-to-end TLS encryption with the client automatically getting certs from Let's Encrypt. QR codes for URL sharing. Client is open source. Can serve a local directory over WebDAV. MIT License. Written in Go.
|
||||
* [localhost.run](https://localhost.run/) - Simple hosted SSH option. Supports custom domains for a cost.
|
||||
* [Packetriot](https://packetriot.com) - Comprehensive alternative to ngrok. HTTP Inspector, Let's Encrypt integration, doesn't require root and Linux repos for apt, yum and dnf. Enterprise licenses and self-hosted option.
|
||||
* [Hoppy](https://hoppy.network/) - WireGuard-based. Provides static IPv4 and IPv6 addresses for your machines, which is a simple and useful level of abstraction. Targeted towards self-hosters and people behind NATs.
|
||||
* [gw.run](https://gw.run/) - Specifically focusing on securely exposing internal web apps to a group of people; not for publicly facing apps. Share access via email address then allow users to log in with common login providers like Google.
|
||||
* [SSHReach.me](https://sshreach.me/) - Paid SSH-based option. Uses a simple python script.
|
||||
* [KubeSail](https://kubesail.com/) - Company offering tunneling, dynamic DNS, and other services for self-hosting with Kubernetes.
|
||||
* [inlets](https://inlets.dev/) - Used to be [open source](https://github.com/inlets/inlets-archived); now focused on a polished commercial offering. Designed to work well with Kubernetes.
|
||||
* [LocalToNet](https://localtonet.com/) - Supports UDP. Free for a single tunnel. Paid supports custom domains.
|
||||
* [LocalXpose](https://localxpose.io) - Looks like a solid paid option, with a limited free tier.
|
||||
* [Tabserve.dev](https://tabserve.dev) - Web UI that runs entirely in the browser and uses a Cloudflare Worker for https.
|
||||
* [Serveo](https://serveo.net) - SSH-based, signup optional, offering HTTP(S) and TCP tunneling and SSH jump host forwarding capabilities.
|
||||
|
||||
# Overlay networks and other advanced tools
|
||||
|
||||
* [headscale](https://github.com/juanfont/headscale) [](https://github.com/juanfont/headscale/stargazers) - Open source implementation of Tailscale control server. Can be used with Tailscale's official open source client. Written in Go.
|
||||
* [Tailscale](https://www.tailscale.com/) [](https://github.com/tailscale/tailscale/stargazers) - Built on WireGuard. Easy to use. Control server is closed source. Client [code](https://github.com/tailscale) available with a BSD3 license + separate patents file.
|
||||
* [Teleport](https://goteleport.com/) [](https://github.com/gravitational/teleport) - Comprehensive control plane tool, but also supports [accessing apps](https://goteleport.com/docs/application-access/introduction/) behind NATs. Written in Go.
|
||||
* [Nebula](https://github.com/slackhq/nebula) - [](https://github.com/zerotier/slackhq/nebula) Peer-to-peer overlay network. Developed and used internally by Slack. Similar to Tailscale but completely open source. Doesn't use WireGuard. Written in Go.
|
||||
* [ZeroTier](https://www.zerotier.com/) - [](https://github.com/zerotier/ZeroTierOne/stargazers) Layer 2 overlay network. They take decentralization seriously, and like to say "decentralize until it hurts, then centralize until it works." Written in C++.
|
||||
* [Netmaker](https://github.com/gravitl/netmaker) [](https://github.com/gravitl/netmaker/stargazers) - Layer 3 peer-to-peer overlay network and private DNS. Similar to Tailscale, but with a self-hosted server/admin UI. Runs kernel WireGuard so very fast. Not FOSS, but source is available. Written in Go.
|
||||
* [NetBird](https://github.com/netbirdio/netbird) [](https://github.com/netbirdio/netbird/stargazers) - NetBird is an open-source VPN management platform built on top of WireGuard® making it easy to create secure private networks for your organization or home.
|
||||
* [Firezone](https://www.firezone.dev/) [](https://github.com/firezone/firezone) - Layer 3/4 overlay network. Runs on kernel WireGuard® and supports SSO using generic OIDC/SAML connectors. Distributed under apache 2.0 license and written in Elixir/Rust.
|
||||
* [innernet](https://github.com/tonarino/innernet) [](https://github.com/tonarino/innernet/stargazers) - Similar to Netmaker, nebula, and Tailscale. Takes advantage of existing networking concepts like CIDRs and the security properties of WireGuard to turn your computer's basic IP networking into more powerful ACL primitives. Written in Rust.
|
||||
* [Pritunl](https://pritunl.com/) [](https://github.com/pritunl/pritunl/stargazers) - Seems quite comprehensive and complicated. OpenVPN, WireGuard, and IPSec support.
|
||||
* [Tinc](https://github.com/gsliepen/tinc) [](https://github.com/gsliepen/tinc/stargazers) - Tinc is a peer-to-peer VPN daemon that supports VPNs with an arbitrary number of nodes. Instead of configuring tunnels, you give tinc the location and public key of a few nodes in the VPN. After making the initial connections to those nodes, tinc will learn about all other nodes on the VPN, and will make connections automatically. When direct connections are not possible, data will be forwarded by intermediate nodes. Written in C.
|
||||
* [OpenZiti](https://openziti.github.io) - [](https://github.com/openziti/ziti/stargazers) - Overlay network. The goal of OpenZiti is to extend zero trust all the way into your application, not just to your network. Apache 2.0 license. Written in Go.
|
||||
* [Ngrok-operator](https://github.com/zufardhiyaulhaq/ngrok-operator) [](https://github.com/zufardhiyaulhaq/ngrok-operator/stargazers) - Ngrok but integrated with Kubernetes, allows developers on private kubernetes to easily access their services via Ngrok.
|
||||
* [chisel-operator](https://github.com/FyraLabs/chisel-operator/) [](https://github.com/FyraLabs/chisel-operator/stargazers) - Kubernetes integration for Chisel. Similar functionality to inlets. MIT License. Written in Rust.
|
||||
|
||||
|
||||
# Blog posts
|
||||
# Reference
|
||||
|
||||
* [Roll your own Ngrok with Nginx, Letsencrypt, and SSH reverse tunnelling](https://jerrington.me/posts/2019-01-29-self-hosted-ngrok.html)
|
||||
* [Poor man's ngrok with tcp proxy and ssh reverse tunnel](https://dev.to/k4ml/poor-man-ngrok-with-tcp-proxy-and-ssh-reverse-tunnel-1fm)
|
||||
* [How I built Ngrok Alternative (jprq)](https://dev.to/azimjohn/how-i-built-ngrok-alternative-3n0g)
|
||||
* [Great SO answer by AJ ONeal about how these things work](https://stackoverflow.com/a/52614266/943814)
|
||||
* [Talk by AJ ONeal about tunneling tech](https://youtu.be/E1Q2MWGCADo)
|
||||
* [ngrok alternative: localtunnel + Caddy + Lets Encrypt](https://morph027.gitlab.io/blog/localtunnel-ngrok/)
|
||||
|
||||
|
||||
# Discussions
|
||||
|
|
|
|||
Loading…
Reference in a new issue