Comment on Replacing Cloudflare Tunnel with a Selfhosted Towonel Tunnel
K3can@lemmy.radio 1 week agoThat’s exactly the use case for “tunnels”: allowing public, incoming connections behind CGNAT.
Wireguard requires a public IP on at least one side of the connection and only allows private access. If you want to host a blog or website AND you’re behind CGNAT, then a “tunnel” service is a very easy solution.
Undaunted@feddit.org 1 week ago
But going with a self-hosted approach like Towonel, you need a server with a public IP too. And I think what the commenter meant is, if you already have that, you can just setup a WireGuard connection to that public server, so that it can route the traffic to your local network.
K3can@lemmy.radio 1 week ago
Oh, maybe I misunderstood? It sounded like he didn’t understand what advantage a “tunnel” could provide.
If your server is behind CGNAT, you need a TURN-style “tunnel” to allow incoming connections. If you have your own remote server with a public IP, then you can absolutely use that and create the tunnel using wireguard (or openvpn, ssh, etc).
I just mentioned CF because it’s probably the most popular solution.
The point is, if you have CGNAT, you need to create that “tunnel” somehow if you want to allow incoming connections.