• 0 Posts
  • 215 Comments
Joined 2 years ago
cake
Cake day: February 1st, 2024

help-circle
  • Maybe not a service in the typical sense, but setting up your router+server to route your home network traffic through a VPN is a fun project.

    My router (MikroTik) supports WireGuard, so I can use it with Mullvad for the whole house—but wg is demanding and it’s a slow router, so while it can NAT at ~1Gbps, it can’t do WireGuard at more than ~90Mbps. So, I set up WireGuard/Mullvad on a little SBC with a fast processor, and have my router use that instead. Using policy based routing and/or mangling, I can have different VLANs/subnets/individual hosts selectively routed through the VPN.

    It’s a fun exercise, not sure I implemented it in a smart way, but it works :)







  • This is actually the one that I would agree with (edit: see below), if the difference is “professional” vs. “academic.” I certainly wouldn’t call a natural science degree professional, and if you’re in a research institution studying some form of engineering I’d probably put you in the same category. Just my experience/opinion though (and the rest of the exclusions are super stupid, I agree).

    Edit: from the replies, this is referring to Professional Engineering; in my corner of the world, “Engineer” is an overloaded term that generally means electrical, mechanical, software, and sometimes computer engineer. My comment was referring to these engineers, who are rarely licensed and study alongside scientists in school. I completely agree with parent in the context of “professional engineering” (I mean…it’s right there in the name…).




  • VPS+VPN, this is what I do.

    VPS has public IP and runs WireGuard “server”* and a reverse proxy (and fail2ban…). Reverse proxy points to my home computer over the WireGuard link. No open ports on my home router.

    For private facing/LAN-only services I just don’t have an entry in the VPS reverse proxy. DNS on the router points everything to my local server, so if at home I access everything directly. To access internal services remotely requires VPN (i.e., WireGuard to the VPS).

    Works well; I have a tiny free tier VPS but even so, no complaints.

    *Yes I know there are no wg clients or servers, only peers, but it plays a server-likr role.






  • Especially after adding in all the power draw of the automation requires…

    What exactly is the incremental power draw for automation? My network gear and server (a little nuc) are sunk power costs as I self host other services.

    Idling, my home uses around 100W with the fridge off. One 10W light is an additional 10% of my power budget, and I have a lot more than one light in my house. I also pay about $0.40/kWh.


  • I can be a bit neurotic about turning off lights when I leave a room, so Home Assistant was a nice way to free up brain space for me. A few motion sensors here and there + some simple automations, and the lights mostly handle themselves. Zigbee sensors and Zigbee or Matter-over-WiFi bulbs, so everything is local. A free VPS+WireGuard setup means I can access them remotely should I need to, with TailScale as a backup.

    Cloud failures mean I can’t access remotely, but local control is unaffected—if my smart devices stop working it’s almost certainly my fault :)