So everyone is talking about cloudflare tunnels and I decided to give it a shot.

However, I find the learning curve quite hard and would really appreciate a short introduction into how they work and how do I set them up…

In my current infrastructure I am running a reverse proxy with SSL and Authentik, but nothing is exposed outside. I access my network via a VPN but would like to try out and consider CF. Might be easier for the family.

How does authentication work? Is it really a secure way to expose internal services?

Thanks!

  • operator@kbin.socialOP
    1·
    1 年前

    What I’m doing is using a dedicated VPN Gateway container. The instances running delicate services have a static default route to the GW-container.

    This is an extra step, but allows me add easily route other services or clients or even whole networks through my VPN without additional setup or specialized containers bundling both.

    Wanna use it on the phone? Change the gateway address. Wanna use it from my Linux machine? Add a static default route. Etc…

    Works flawlessly!

    • CodaBool@lemmy.world
      2·
      1 年前

      That sounds better since it doesn’t have any kind of bundling of images. Do you have a link to anything public I can look at to try out a similar setup?

      • operator@kbin.socialOP
        1·
        1 年前

        Unfortunately not at the moment, as all is kinda fiddled and setup manually, but I’m redoing my home lab in a couple of weeks. Send me a message and I’ll send you the docker image or script!

        But basically I did the following:

        • enable ipv4 forwarding
        • configure and start VPN tunnel
        • set the default route to the tunnel
        • set the gw for reaching the remote vpn server to the local gw
        • sets routes for the local network to the local gw

        If your vpn goes down, the default route shall still point to the remote gw, but as it isn’t there you also have a kill switch. Voila!

        I am looking into gluetun but haven’t tried it yet.

        Edit: this doesn’t protect you from someone snooping the traffic inside your local net, but protects it starting from the point where it leaves the local vpngw. The traffic is unencrypted between that and your client.