kopia lustrzana https://github.com/anderspitman/awesome-tunneling
Merge branch 'master' into master
Anders Pitman
GitHub
commit
a12ff84223
79
README.md
79
README.md
|
|
@ -3,6 +3,9 @@ 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
|
||||
|
|
@ -21,62 +24,57 @@ 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:** Since starting this list I found most of the other solutions to be
|
||||
either too complicated or making different tradeoffs than I would want. I have
|
||||
two of my own projects in this space:
|
||||
**UPDATE 2022-09-23:**
|
||||
|
||||
1. [SirTunnel](https://github.com/anderspitman/SirTunnel) is I believe the
|
||||
minimal way of getting auto-HTTPS tunneled through to a private network.
|
||||
It's just a 50-line Python script that leverages Caddy and OpenSSH, but you
|
||||
need to understand how it works to use it. This one is good for developers.
|
||||
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.
|
||||
|
||||
2. [boringproxy](https://boringproxy.io/) is my take on a comprehensive tunnel
|
||||
proxy solution. It's in beta but currently solves almost everything I want except
|
||||
auto DNS management, and that's planned. Once the server is running this is a very
|
||||
easy tool to use, and is targeted at non-developers.
|
||||
# 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. Note that it's technically against their ToS to host anything other than basic HTML pages on the free plan, including photos, audio, and video. In practice I'm not aware of many instances of this being enforced.
|
||||
* 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.
|
||||
|
||||
# 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. I believe it uses a custom TCP protocol for multiplexing, which can either run over a single TCP connection or a connection pool.
|
||||
* [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.
|
||||
* [kcptun](https://github.com/xtaci/kcptun)[](https://github.com/xtaci/kcptun/stargazers) - A Stable & Secure Tunnel based on KCP with N:M multiplexing and FEC. Available for ARM, MIPS, 386 and AMD64. Written in Go.
|
||||
* [Teleport](https://goteleport.com/) [](https://github.com/gravitational/teleport) - Comprehesive 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++.
|
||||
* [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) - SSH under the hood, but still uses a custom client binary. Supports auto certs from LetsEncrypt. Written in Go.
|
||||
* [expose](https://github.com/beyondcode/expose) [](https://github.com/beyondcode/expose/stargazers) - ngrok alternative written in PHP.
|
||||
* [Pritunl](https://pritunl.com/) [](https://github.com/pritunl/pritunl/stargazers) - Seems quite comprehensive and complicated. OpenVPN, WireGuard, and IPSec support.
|
||||
* [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.
|
||||
* [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.
|
||||
* [expose](https://github.com/beyondcode/expose) [](https://github.com/beyondcode/expose/stargazers) - ngrok alternative written in PHP.
|
||||
* [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.
|
||||
* [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.
|
||||
* [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.
|
||||
* [PageKite](https://pagekite.net/) [](https://github.com/pagekite/PyPagekite/stargazers) - Comprehensive open source solution with hosted options.
|
||||
* [Crowbar](https://github.com/q3k/crowbar) [](https://github.com/q3k/crowbar/stargazers) - Tunnels TCP connections over HTTP GET and POST requests.
|
||||
* [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.
|
||||
* [tunneller](https://github.com/skx/tunneller) [](https://github.com/skx/tunneller/stargazers) - Open source. Written in Go.
|
||||
* [jprq](https://github.com/azimjohn/jprq) [](https://github.com/azimjohn/jprq/stargazers) - Proxies over WebSockets. Written in Python.
|
||||
* [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.
|
||||
* [pgrok](https://www.proxy.jetzt/) [](https://github.com/jerson/pgrok/stargazers) - Fork of ngrok 1.0, with more recent commits.
|
||||
* [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.
|
||||
* [PageKite](https://pagekite.net/) [](https://github.com/pagekite/PyPagekite/stargazers) - Comprehensive open source solution with hosted options.
|
||||
* [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.
|
||||
* [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.
|
||||
* [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.
|
||||
* [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.
|
||||
* [docker-tunnel](https://github.com/vitobotta/docker-tunnel) [](https://github.com/vitobotta/docker-tunnel/stargazers) - Simple Docker-based nginx+SSH solution.
|
||||
* [hypertunnel](https://github.com/berstend/hypertunnel) [](https://github.com//berstend/hypertunnel/stargazers) - Public server appears to be down. MIT Licensed. Written in JavaScript.
|
||||
* [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.
|
||||
* [holepunch.io](https://holepunch.io) [](https://github.com/CypherpunkArmory/holepunch/stargazers) - Has nice hosted solution. Uses SSH for muxing.
|
||||
* [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.
|
||||
* [Telebit](https://telebit.cloud/) - Written in JS. [Code](https://git.coolaj86.com/coolaj86/telebit.js).
|
||||
* [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.
|
||||
* [Ngrok-operator](https://github.com/zufardhiyaulhaq/ngrok-operator) - Ngrok but integrated with Kubernetes, allows developers on private kubernetes to easily access their services via Ngrok.
|
||||
|
||||
|
||||
# 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 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.
|
||||
* [Tailscale](https://www.tailscale.com/) [](https://github.com/tailscale/tailscale/stargazers) - Built on WireGuard. Easy to use. Doesn't include an HTTPS proxy on the public side, but could be combined with nginx/Caddy/etc. Client [code](https://github.com/tailscale) available with a BSD3 license + separate patents file.
|
||||
* [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.
|
||||
|
|
@ -86,6 +84,25 @@ easy tool to use, and is targeted at non-developers.
|
|||
* [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.
|
||||
|
||||
|
||||
# Overlay networks and other advanced tools
|
||||
|
||||
* [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++.
|
||||
* [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. Doesn't include an HTTPS proxy on the public side, but could be combined with nginx/Caddy/etc. Control server is closed source. Client [code](https://github.com/tailscale) available with a BSD3 license + separate patents file.
|
||||
* [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.
|
||||
* [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.
|
||||
* [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.
|
||||
* [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.
|
||||
|
||||
|
||||
# Reference
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue