So I want to setup a remote backup location at my parents house although they are very mindful about there electricity usage and environmental impact (and so am I) so I don’t want to have to have a pc always on when it doesn’t need to be.
Is it possible to setup remote Wake-on-lan so I can schedule my homelab at my place to wake up the server at my parents house and start a backup like once a week, I want to do this in a secure fashion as well so ideally no port forwarding, I currently use cloudflare tunnels for my home network.
Are there any other options or do you have a similar setup at your place?
You must log in or register to comment.
I’ve been mentally experimenting with an ESP32 hooked up to my desktop’s PWR header with a switch. I’ve done worse than that before, so I know it’ll work. I just haven’t gotten my ass around to it. I can send commands to it through my domain via Apache acting as a reverse proxy.
That actually seams pretty awsome, just using a really low powered device to send WOL commands.
Home Assistant can send wake on lan commands.
If you have a remotely accessible Home Assistant Server on your LAN it can send the commands for you on the LAN while you access it remotely.
I don’t have home assistant setup in my parents place, that is a nice feature though I might use that for other things.
I do backups with a Raspberry Pi with a 1TB SD card and leave it on all the time. The power draw is very small and I think reasonable for the value of offsite backups.
My personal experience with WOL (or anything related to power state of computers) is that it’s not reliable enough for something offsite. If you can set something up that’s stable, awesome, but if your backup server is down and you need to travel to it, that suuuucks.
I already have 2x2tb hard drives, a singular sd card is not enough for me I need some level of redundancy even for my backups.
You could use a very low power computer that’s always on like a Raspberry PI Zero W to send the WoL packet to the backup computer. It only uses about 1 watt. Some routers have the ability to send a WoL packet as well.
And how do you communicate with the Pi0?
Wireguard between you and remote device like a pi. Set pi to portfowarding and masquerading on. It will then let you be on say a 10.x.x x network remotely but will send info on the remote LAN like it came from that pi local IP
Use SSH. Ether open a port in the firewall or connect it to a VPN. If the backups are done on a schedule, you could also setup a cron job on the Pi to send the WoL packet a few minutes ahead of time.
Use a VPN; don’t open up SSH to the internet.
Or just be cautious, thoughtful and sensible if you do. Only a Sith deals in absolutes.
Ssh over Internet is fine as long as it’s properly setup (no password auth, root not allowed, etc.). Obviously a VPN is even better.
If timers on the bios aren’t an option, look for the settings to power on after power outage. If you turn it on, you can use a standard timer plug to turn the power on and off.
I use Upsnap on a low-power SBC behind a reverse proxy: https://github.com/seriousm4x/UpSnap
Before that I used the WoL feature on my Asus router.
Can you set the BIOS to wake up at a certain time? Many have that option.
I didn’t realise the bios could do that I will look into that.
Arch wiki strikes again! That’s pretty cool I just checked and the bios on my pc does indeed have this feature.
it ain’t pretty, and may not quite suit what you’re looking for. other comments recommending a pi or similar are likely better taste. but here’s what I’ve done:
I have a cheap Android tablet that stays home and is connected to our home network. if needed, I connect to the tablet with TeamViewer and use a WoL app to send the packet to my computer on that same network.
Booting on a schedule as others have suggested would be the simplest by far.
To answer as asked though, it’s not something I’ve needed to do but it sounds like a VPN + IGMP proxy (I’m assuming you have a separate subnet for your VPN) might fit the bill.
Alternatively some kind of low power device (a Pi or something) that lives in the same subnet could make the WOL call locally, and you just need to find a way to trigger it. Could do it via a http call for example.
Wake on LAN is a LAN feature, not WAN, so you’d need to issue that over the local LAN there at the house. You’re going to have a hard time trying to get that working over the WAN (if that’s even possible).
The other comments mentioning a scheduled boot would be a much easier/simple solution if it works for you.
But I’ll throw this in, the super basic least tech solution to this is to open a port forward to the house’s network router. Yes, I know you don’t want to do that, but it’s probably the only network device at that house that’s actually on 24/7 right? And by all means lock it down however you like. My simple method is to open the router login to a non-standard port number, with a IP whitelist, add my own home IP address to that IP whitelist, and bam you now have access to that remote home’s router for just your IP address. Log in remotely, issue a wake on LAN via the router’s own web ui, done.
It’s perfectly reasonable to make this a bit more secure if you wanted but it gets slightly more complicated - open a non-standard port for SSH access to the remote router’s SSH port that only allows SSH login with key. Generate a SSH key and share that key with yourself, then you can log in remotely to that remote house via non-standard SSH port using the SSH key (no user/passwords). From there you’d have to see if you can issue Wake on LAN on the SSH command line, or set up a SSH tunnel from that remote LAN to yours so you can proxy into the router login page and do your Wake on LAN from there. … yes I realize this got complicated :/ But you’ve got a few things to explore given your patience for tinkering with this stuff :)
Of course much of this relies on that house’s router having any of these features to enable and configure. The main takeaway here is that Wake on LAN requires something on 24/7 at that remote LAN for you to enable remote access into and issue a Wake on LAN command within that LAN. How to actually accomplish that is the tricky bit.
You’re going to have a hard time trying to get that working over the WAN (if that’s even possible).
Wake on LAN is still encapsulated in an IP packet, so you can send it over the internet, and most WOL clients let you specify an IP. However your router will need to DNAT it to a broadcast address. Some routers have a check box for this (e.g. An ISP provided Technicolor router I have), some let you port forward to broadcast (e.g. Many routers, sometimes with workarounds), and some let you manually configure NAT (e.g. MikroTik routers).
So it is possible, but forwarding public internet traffic to a broadcast address seems like a bad idea, and I wouldn’t recommend it. Why I know this: I used to do this in middle school, and it does work quite well.
you can configure bios for self power on at certain time and then turn the server off after finishing backup
Second that. I don’t have another node that I can use for WoL at my backup location so I opted for the node to turn on every morning, run the backup and turn off using cron at a given time. Works perfectly!
Just ask Ian to start your computer when he goes on it
Lan is not the name of my parent 💀
