How the **** do you decline cookies on this site??!!!
Cloudflare has made it too easy to access your homelab on the internet
11–20 of 26 posts
Re: Cloudflare has made it too easy to access your homelab on the internet
#12Call me crazy, but I don't think "tunnel all your traffic through a third party corporation's service" is the correct solution to "my IP changes sometimes." Maybe just set up DDNS instead? If you really are trying to run a server behind a CGNAT, then I guess you have no other options, but I'd consider this kind of thing to be a last resort.
CGNAT is pretty common unfortunately and sure makes things harder.
Re: Cloudflare has made it too easy to access your homelab on the internet
#13I've opted to do this myself by buying a VPS for ~$5/month with Digital Ocean. It runs a Wireguard server and nginx, and then my home lab router connects via Wireguard. Nginx acts as a reverse proxy to serve content from my home lab. I have (relatively speaking) complete control over the entire path. When running Cloudflare tunnels, opening a port on your router, or having a VPS+Wireguard, it's important to think abo…
If you're not serving HTTP/S you may also opt to use iptables to blanket port forward through wireguard.
Re: Cloudflare has made it too easy to access your homelab on the internet
#14Brother, wait until you hear about Tailscale...
Which is also point to point for the traffic.
Re: Cloudflare has made it too easy to access your homelab on the internet
#15I've opted to do this myself by buying a VPS for ~$5/month with Digital Ocean. It runs a Wireguard server and nginx, and then my home lab router connects via Wireguard. Nginx acts as a reverse proxy to serve content from my home lab. I have (relatively speaking) complete control over the entire path. When running Cloudflare tunnels, opening a port on your router, or having a VPS+Wireguard, it's important to think abo…
I have a VPS running BGP, along with my own ASN and a /24 block. My home network is tunneling out to the VPS from a VM and routing the /24 over wireguard. The /24 is then made available on its own VLAN. No doubt all this stuff is a violation of residential TOS agreements.
How did you acquire an ASN, how much did it cost you, and how much ongoing maintenance/cost is it?
Re: Cloudflare has made it too easy to access your homelab on the internet
#16Cloudflare tunnels is a nightmare to work with. I had the famous experience of "it worked fine at my home, I don't know why it's not working in the lab" and couldn't ever resolve the problem, running on Ubuntu. As of March 2024, Cloudflare tunnels was very, very unrefined (on Ubuntu). QUIC doesn't work and you have to read through forums to find how to change protocol to http2. The logs are insufficient to pinpoint issues. Remote administration workflow seems broken. I should also mention that I used my own domain, not the free one, and used Cloudflare for dns.
I am very interested in Tailscale SSH as an alternative to CloudflareTunnel + SSH. If anyone has experiences with Tailscale SSH, please share (https://tailscale.com/tailscale-ssh)
Re: Cloudflare has made it too easy to access your homelab on the internet
#17How the **** do you decline cookies on this site??!!!
Hey, earlier it was going into Manage and unchecking the Google Analytics. I realized that was a bad design and have it updated now. Now, you can simply reject the cookies :)
Re: Cloudflare has made it too easy to access your homelab on the internet
#18Brother, wait until you hear about Tailscale... Which is also point to point for the traffic.
I wasn't aware of Tailscale Funnel, but I'll give it a try. It was easy to set up since I already have a lot of things on Cloudflare.
Re: Cloudflare has made it too easy to access your homelab on the internet
#19I once had a project where I had more than one person trying to play an emulated game online through a custom Dolphin Emulator build on the same LAN segment. Due to the nature of how the client was trying to use ports, port forwarding was not helping due to overlap (clients wanted the exact same ports open and could not be distributed). I eventually gave up trying to do port forwarding and instead had each person get a VM with an extra IP assigned to it in a local data center. Linux supports different network configs per application and I managed to use TincVPN as an Ethernet bridge between the VM's Ethernet and each local machine, where I assigned the 2nd IP from the VM to the end of the tunnel and created a custom routing table only for Dolphin to be started with that used the VMs routing configuration. Effectively, it looked like they were playing their games from inside the data center.
Re: Cloudflare has made it too easy to access your homelab on the internet
#20I've opted to do this myself by buying a VPS for ~$5/month with Digital Ocean. It runs a Wireguard server and nginx, and then my home lab router connects via Wireguard. Nginx acts as a reverse proxy to serve content from my home lab. I have (relatively speaking) complete control over the entire path. When running Cloudflare tunnels, opening a port on your router, or having a VPS+Wireguard, it's important to think abo…
I have a VPS running BGP, along with my own ASN and a /24 block. My home network is tunneling out to the VPS from a VM and routing the /24 over wireguard. The /24 is then made available on its own VLAN. No doubt all this stuff is a violation of residential TOS agreements.
How does someone go about doing something like this? Do you have a blog? I would love to read more.