3 ms·
> In fact this is a nice place to ask: how would you build a "something" that monitors the network for packets sent to powered-off machines, then somehow caches
by vbezhenar 5y ago
> In fact this is a nice place to ask: how would you build a "something" that monitors the network for packets sent to powered-off machines, then somehow caches the request, powers the destination machine On, and finally lets the request continue to its target? Has this been tackled anywhere? There must be tons of people wanting a homeserver but living in places where electricity has a considerable cost...
IP protocol does not guarantee delivery. So you don't have to cache request. Just power on the machine, client will retry sending the packets until the machine is powered on and can respond. Just make sure that there's no gap between networking available and http server is still starting on.
- secure 5y agoI have built such a gateway for SSH: it accepts the connection, powers on the target machine if needed, then forwards traffic. https://github.com/stapelberg/zkj-nas-tools/blob/master/wolgw/wolgw.go https://github.com/stapelberg/zkj-nas-tools/blob/master/wolg... The advantage over just catching any packets is that an SSH connection is authorized, so less noisy in terms of undesired wakeups.
- secabeen 5y agoApple has this. It's called Boujour sleep proxy, and it allows a always-on device like a Airport or AppleTV to claim the IP address of a sleeping Mac, waking it with a WoL packet when traffic for that device comes in. It's probably pretty useful, but is annoying on a managed network, as it spams my arpwatch system every time the IP is transferred between devices.