Is the project named spinup or rallyup? The HN post title differs from the GitHub repo
Thanks for catching that! Updated to match. The names I liked was already taken on crates.io but never got it out of my head
Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
11–20 of 28 posts
Re: Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
#12Would love to see exactly this but running on an ESP style board (with Ethernet). As well as an API or web interface to trigger manual WoL calls.
Nice project, thanks for sharing!
Re: Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
#13One thing that might be useful is to allow a given server in the chain to fail. For example, if you had a Proxmox (or other hypervisor) cluster, in the event that a single node fails to come up, you'd probably want everything else to still boot. Or maybe it would be easier if there was a separate category for VM vs. hypervisor? Either way, neat project, and thank you for sharing.
Thanks for the feedback! So would a tagging system be useful? Right now you can declare dependencies on a single server, but maybe we can have it depend on at least one of the machines in a tagged group booting up?
I could see a group being useful, yeah. Must have one of [server0, server1, server2] to continue. Though there is a lot of bleed-over when talking about hypervisors and the boot order of VMs, since hypervisors generally can handle that, at least on their own node.
Re: Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
#14Very nice, just FYI for home assistant fans: WoL is also supported in there :)
Re: Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
#15Is wake on LAN any good these days? I remember it being flaky in the late 90s early 00s...
I only had one problem with it, and that was that it isn't enough to enable it in the BIOS, but I needed to flip a switch on Windows and set up a systemd service on Linux (I dual boot). For Linux set it to "g": https://wiki.archlinux.org/title/Wake-on-LAN#Make_it_persist... For Windows you need to enable "Wake on Magic Packet": https://www.windowscentral.com/how-enable-and-use-wake-lan-w...
"set it to 'g'". Awesome.
G for maGic, I presume?
Re: Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
#16Equip your machines with whack-on-LAN so you can remotely reset them by the same mechanism, and you've got a reasonably complete remote management setup!
https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&d...
https://www.i3detroit.org/reset-on-lan-an-ethernet-aware-rem...
Re: Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
#17Is wake on LAN any good these days? I remember it being flaky in the late 90s early 00s...
I only had one problem with it, and that was that it isn't enough to enable it in the BIOS, but I needed to flip a switch on Windows and set up a systemd service on Linux (I dual boot). For Linux set it to "g": https://wiki.archlinux.org/title/Wake-on-LAN#Make_it_persist... For Windows you need to enable "Wake on Magic Packet": https://www.windowscentral.com/how-enable-and-use-wake-lan-w...
I always wondered: why make it so difficult to turn on? Is it a security issue? I mean, an off-by-default OS setting and an off-by-default BIOS setting? How dangerous is this thing??
Re: Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
#18Is wake on LAN any good these days? I remember it being flaky in the late 90s early 00s...
In my experience it depends a lot on your hardware. For some versions my msi consumer Mainboard just would not respond to wol packets. No matter what I tried.
Re: Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
#19Is wake on LAN any good these days? I remember it being flaky in the late 90s early 00s...
I still have a lot of weirdness when it comes to making things actually stay asleep and wake up again when wanted. There's a lot of hardware that often boots up, or always boots but only if it's been switched on once before, or keeps trying to wake itself up for no good reason.
The absolute most consistent way I've found is using cheap zigbee smart switches or even second hand smart PDUs. Set the machine to boot when power is restored and actually switch the thing on and off from the wall. It saves a whole lot of messing around, you can force the reboot issue and for a tiny amount more in upfront costs you can have power monitoring as well. It also works for network gear that doesn't sleep or anything else that had a physical switch.
edit: Ideally give me hardware with proper out-of-band management (ipmi or AMT at a pinch), but for everything else having control of the power is as good as it gets.
Re: Show HN: rallyup – Lightweight Wake-on-LAN Scheduler
#20Equip your machines with whack-on-LAN so you can remotely reset them by the same mechanism, and you've got a reasonably complete remote management setup! https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&d... https://www.i3detroit.org/reset-on-lan-an-ethernet-aware-rem...
[deleted]