ssh-punchhole VS frp

At home, just a bunch of AlmaLinux VMs with K3s, using MetalLB for LoadBalancerIPs in my LAN and ssh-punchhole to forward ports from an externally hosted VPS to my local ingress-nginx and other things, so my stuff is externally available.

Get yourself a cheap VPS and then try something like https://github.com/TamCore/ssh-punchhole (which i hacked together, because everything else just looked too bloated for my taste). That way you can host everything at home and don't have to forward any ports, as the tunnel is established from within your network :)

I've published my setup for that case as a container image: https://github.com/TamCore/ssh-punchhole.

I've published my setup on Github: https://github.com/TamCore/ssh-punchhole Even if you don't use Docker, you could still basically use the script as standalone. I just wanted to have everything neatly packaged :)

I use a VPS as my public endpoint, but the tunnel is established from my network, as it's based on reverse SSH port forwarding. So no port forwarding in my router required and would even work with CGNAT and whatsoever. Sample configs I've published under https://github.com/TamCore/ssh-punchhole

If you don't want to mess around with port forwarding, I'd recommend just getting a cheap VPS somewhere close to you, and hosting Traefik and something like my ssh-punchhole (see https://github.com/TamCore/ssh-punchhole) for tunneling inbound traffic to your service.

Using haproxy (lightweight and quickly configured) was an easy fix for that issue. I've included the relevant parts from my configs in https://github.com/TamCore/ssh-punchhole/blob/main/README.md :)

If you want to self-host, there are many options. For something production ready frp is probably what you want. If you're a developer, I'd recommend starting with my own SirTunnel project and modifying it for your needs. For non-developers and those wanting more of a GUI experience, I created boringproxy. 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.

Seems to be the exact opposite of https://github.com/fatedier/frp which is a reverse tunnel over a variety of protocols (including HTTP).

I've been self-hosting https://github.com/fatedier/frp on my little box, and it feels insane to think of the times where I didn't have it set up. There are many choices in the space as others pointed out, but frp's capabilities and lightweight packaging blows all other setups out of the water. I placed mine behind nginx with Let's Encrypt for SSL support. Hella fresh!

My setup to do the same:

- small Hetzner instance

- my domain's dns pointing to that instance

- frps[1] running on that instance

- frpc running on my local machine and connected to the cloud frps

[1] https://github.com/fatedier/frp

An easy service to use is FRP, recently found it and it basically handles making the connection out of the network and is really easy to setup. https://github.com/fatedier/frp I personally having it running on a VPS and the client then running on my local network pointing at a reverse proxy which then handles sending it to the diffrent clients.

No, FRP - https://github.com/fatedier/frp

Another way around is to use reverse proxy like frp but since you need SSH anyway, all you need is already comes with SSH (reverse SSH)

Take a look also onto popular, similar to yours project: frp