Now I just need to get enough momentum to set up the process of waking up my desktop as needed and set up radical caldav server in the mobile.
Or login into the router and send WoL from there?
Or have Raspberry always on with ssh?
Or set a power-on timer in BIOS/UEFI once a day and a shutdown/sleep in cron? (This is also a good failsafe if WoL doesn't work.)
Hm, so never tried something like that before actually, I think for OpenWrt I need to install arp packages. I do not have public IP any more though, was getting hammered by bot network and found Tailscale to do what I need.
> Or login into the router and send WoL from there?
Restricted outside access to the router management panel, only port forwarded to the desktop.
> Or have Raspberry always on with ssh? I do not have one, which is why used a mobile, thought to be next best thing. As, power outages happen regularly, I need something that would be able to keep on running.
> Or set a power-on timer in BIOS/UEFI once a day and a shutdown/sleep in cron? (This is also a good failsafe if WoL doesn't work.)
That's easily workable for my setup, actually!
Thank you for giving me the ideas!
> Hm, so never tried something like that before actually, I think for OpenWrt I need to install arp packages.
No, you don't. Put this in /etc/firewall.user or /etc/rc.local (you can do it from UI) and forward a UDP port to 192.168.0.254 or whaterver subnet you're using:
ip neigh add 192.168.0.254 lladdr ff:ff:ff:ff:ff:ff nud permanent dev br-lan extern_learn
The incoming packet will be broadcasted (ff:ff...) on the br-lan interface. 192.168.0.254 doesn't need to exist - the sleeping computer doesn't care.The version in the OpenWrt didn't support the full command. Had to update to `ip-full`.
After the command was successful, I can see the entry in the `ip neigh` table.
Now digging around
Correction! /etc/rc.local isn't OK. The ARP record needs to be reloaded if br-lan interface is restarted, such as when changing other network settings in WebUI. So only /etc/firewall.user will do.
For failsafe, KVM might be the ultimate solution in case boot got stuck.
I for one just leave the beast on, I understand that spin-ups and downs are the main thing that wreck harddrives (and my beast has a lot.)
My Desktop, WoL on, tested to be working Android Phone, always on
All have SyncThing installed. Mobile had Tasker installed.
So, the idea was to have Tasker monitor a folder inside SyncThing, When I need my computer, I put a file inside that folder, when Tasker finds that folder, it sends WoL to my desktop, and deletes the file, Computer wakes up. When I see the file deleted I know, the beast is now awakens ....
When I actually did try that from Thailand, the file did not got deleted, nor the beast woke up.
What happened? Turns out, my mobile restarts automatically after some time of inactivity. Which, locks Tasker out, and the whole process fails.
So, operation wake the beast was busted.