Apologies accepted, seems like I missed something:)

Thanks for the great sarcasm mate

Using Pi’s to run services in my homelab which I want to keep separate from my server (to have some sort of failover in case the server goes down). Status/Monitoring, VPN server and so on

deleted by creator

Looks smooth, I am running Homer (different to Homerr or others). Super easy to configure in yml and looks clean. No fancy features as weather however… or maybe haven’t found it ^^

I do think I’ll give Homarr another try after looking at yours

Interesting project! I’ll spin it up in the next couple of days and check it out

The domain x.com, which Musk bought ages ago, also redirects to twitter

Also interested

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.

That’s becoming interesting once I’m setting up a slaves for failover & local proximity ^^ looking forward to deep diving into it

Appreciate it!

That be amazing! I am currently not using anything (took down my homelab a while back) and planning on completely starting over fresh now.

I am most likely going with unbound! So if you could, that be great!

Thanks! That was really insightful. I guess I’ll give it a try some day, for now everything runs in ipv4 and that runs well haha!

What were the biggest pains? What was surprisingly easier than expected?

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!

Of course! So in order to get maximum speed on your services, you wanna use a direct internal route when you’re inside your net. My understanding is, that when using an external cloud VPS with a proxy, local clients go through unnecessary routing…

Local request --out--> external VPS (proxy) --request data from internal--> receive data on external proxy --send back--> local client

So what I am saying, all requests are unnecessarily routed through the external VPS. So one would have to create an exact duplicate reverse proxy internally to avoid leaving the net. When accessing domain.com, the internal DNS returns the local proxy IP, when outside you receive the cloud VPS IP.

Or am I missing something?

Thank you for taking the time!

One of my considerations is the privacy side… VPN or self hosted solution seems to be the waay better choice in that case.

Haha! Explaining for dummies, I like it.

Thanks! How do you handle that with internal DNS? I suppose you’d need to setup the exact same proxies on the internal and external server, and local DNS handles which one my domain it’s being resolved to?

Thank you for the detailed explanation. I am running Tailscale as a temporary solution to access some services, but I dislike that you have to set firewall rules basically twice (once in your local network and once in Tailscale). I suppose it would be similar for CF?