spaghettiwestern

I had the same setup and the same problems with VPN (in my case Wireguard) server availability. While looking for a solution I realized I was trying to dealing with an architecture problem with software.

Instead of trying to find a software solution to work around my WG server uptime issues, I moved the Wireguard endpoint to an OpenWRT router. Now if my router is up, my WG endpoint is up and my network is accessible. I’ve been running this configuration for years and it has been 100% accessible.

I’m comfortable with the security of WG - open ports for WG endpoints are invisible to network scanners because they do not respond at all and appear closed unless they are sent the the correct key. Even if an attacker has some way of knowinf a WG peer is listening on a specific port, cracking a 256-bit key would take trillions of years. I was then free to choose a remote access application without worrying about remote attackers gaining access to my servers because of some company’s failed security.

FOSS VNC server apps work OK, but I found them somewhat limited so I added NoMachine as my primary option and run both. It’s a commercial app but it’s free, and is one of the only closed source app I use. It can be run 100% locally (although they have a paid option that uses their servers). It iallows full control over your servers including file transfer and audio.

Doesn’t check all your boxes, but it comes close.

I did this for about a year between sites 240 miles apart. The only downside was it used a lot of bandwidth.

If your MIL’s router supports Openwrt or you can replace it with one that does, you can use a VPN and PBR (Policy Based Routing) to your home router or server and do exactly what you want with any camera that supports RSTP (Real Time Streaming Protocol). That includes most cheap wired TP-Link cameras and plenty of others. PBR on the router at your MIL’s home would be used to route all traffic from camera IP addresses to your server.

I used Frigate software and Home Assistant for occupancy detection/alerts and Wireguard for transport. It worked perfectly but I eventually got around to adding 2nd server.

I use AI for the CLI stuff I down have memorized. Linux is still frustrating

I had the same experience when I switched and it’s funny how things change. Now I think there’s a level of hell where people are forced to use Windows 11 all day long.

You can also run it on your Linux box and check external IP via web page. Sites like myip.wtf/text provide it in plain text that can easily be used without accessing your router’s UI.

Instead of connecting via your external IP, consider setting up DDNS (Dynamic DNS). Most routers support it out of the box, it’s free (using a DDNS service like DuckDNS) and easy to set up. Once working you’ll connect via a static URL rather than an IP and when you’re external IP address changes, that URL will update automatically within a few minutes and direct you to the new IP.

The anti li-ion crowd here is really strange.

Dell bios settings often include battery charge limit settings. I have mine set to a 70% limit which provides hours of backup with the display off.

Modern laptop batteries when kept cool and undamaged are extremely safe despite what you might read in these comments. Parking your car in your garage is hundreds of times more hazardous.

DDNS (Dynamic DNS), one 3rd party service I do use.

My network is reached by URL, not IP (although IP still works). When my IP changes the router updates the DDNS service in minutes. Lots of providers out there and it’s easy to switch if needed. I like DuckDNS. It’s free or you can choose to donate a bit to cover their expenses.

Nomachine with local & Wireguard access only.

When I was running a mesh topology I often had the same issue. Switching to a star topology fixed pretty much everything.

I’ve been using Syncthing and it’s been almost flawless but was going to switch to Nextcloud for everything. Looks like I’ll be sticking with Syncthing for the foreseeable future.

Thanks for posting this.