First steps in the BSD world!
1) OpenBSD on VPS (Amsterdam)
2) FreeBSD on Raspberry Pi 4 (home)
I'm running a Wireguard connection between the two.
Next step is setting up relayd on the VPS to point at services on the Raspberry Pi server.
First steps in the BSD world!
1) OpenBSD on VPS (Amsterdam)
2) FreeBSD on Raspberry Pi 4 (home)
I'm running a Wireguard connection between the two.
Next step is setting up relayd on the VPS to point at services on the Raspberry Pi server.
feld
in reply to Michael Jack • • •if you want to get crazy you can mimic this and get a VPS public IP onto that Raspberry Pi
blog.feld.me/posts/2025/03/staβ¦
Static IPs From The Cloud To Your Homelab β Makefile.feld
blog.feld.meMichael Jack
in reply to feld • • •@feld
Interesting! I see we've tried to circumvent the same problem, missing static IP at home.
feld
in reply to Michael Jack • • •yes, so with the simple method of getting your VPS provider to assign additional static IPs to your VPS and Proxy ARP, you can "teleport" the static IP to your home over the WireGuard tunnel. The IP is not actually assigned to any interfaces on the VPS and you get to avoid NAT, needing X-Forwarded-For, etc. All your server logs will have the real public IPs π€
Plus you can leverage the VPS provider's DDoS protection π (you also gain that with NAT or reverse proxying, but it's another good reason to not use your home ISP's public IP directly)
Another advantage of either design is that you could have multiple internet connections at home for redundancy. The WireGuard tunnel is perfect for this. I do this with a hotspot that has unlimited data. I'll be moving next week and changing ISPs but none of my network configuration for my servers needs to change. I'll keep the same IPs because they're ~in the cloud~ π