6 pointsby ebourgess15 hours ago2 comments
  • 15 hours ago
    undefined
  • palata15 hours ago
    > The classic approach [Internet -> Router -> Server] is a recipe for disaster

    I never really get that. If my router gets updates and the only thing I do to it is forward one port to the server, I don't really see how wrong it can go?

    The Cloudflare tunnel doesn't change the fact that there is a server exposed to the Internet. And adding a reverse proxy in front of the server does not necessarily make it more secure, does it?

    I mean, if I cannot update my router and open a single port properly, should I trust myself to setup a reverse proxy?

    • grim_io4 hours ago
      I also expose some of my homelab through the cloudflare tunnel.

      Every IP, except a choice few, are banned before any request reaches my router.

      I don't need to worry about filtering using my limited bandwidth and resources, cloudflare firewall does it for me.

      • palata3 hours ago
        > I don't need to worry about filtering using my limited bandwidth and resources

        But your router is exposed to the Internet anyway, isn't it? Even if you keep all ports closed, random IPs on the Internet can send packages to your router.

        • grim_io2 hours ago
          Sure, but they can't connect the domain names to my IP or infer what services I run.

          The ports are closed, the only way to reach the services is to go through the domain name, the firewall and the tunnel, in probably that order.

          • palataan hour ago
            > they can't connect the domain names to my IP

            They can't, but does it matter? They can connect the domain name to your server (through the tunnel).

            > or infer what services I run

            Why not? The port is open on Cloudflare's side, it's exactly the same.

            The one thing you get from Cloudflare is that probably Cloudflare has a list of blocked IPs and they will prevent them from reaching your server. Though I'm sure there are public lists of "bad IPs" and it shouldn't be too hard to have a firewall that uses them. And anyway in your case you have a list of allowed IPs, so it's not a concern at all.

    • ebourgess15 hours ago
      My main issue is that I didn't want to expose the ports to the internet. The only port now exposed on my server is the SSH port only. Everything else is just handled through the connection between the cloudflared daemon and cloudflare itself.