Slashdot Mirror
Microsoft's Sleep Proxy Lowers PC Energy Use
alphadogg writes "Microsoft researchers have slashed desktop energy use with a sleep proxy system that maintains a PC's network presence even when it is turned off or put into standby mode. Microsoft has deployed the sleep proxy system to more than 50 active users in the Building 99 research facility in Redmond, Wash., according to the Microsoft Research Web site and a paper that will be presented at the Usenix technical conference in Boston later this month. ... Sleep proxies allow machines to be turned off while keeping them connected to the network, waking the machines when a user or IT administrator attempts to access them remotely."
This sounds awfully familiar... http://en.wikipedia.org/wiki/Sleep_Proxy_Service
I guess they're claiming it's smart wake on lan. WoL requres sending a specific packet to the machine. Most people don't know to do this (an admin should, but otherwise...) and the network resources will be unavailable in the meantime. This system keeps the resources available and wakes the computer if they are actually needed. It does not rely on someone being smart enough to wake up the system themselves.
Macs have the option to Wake on Demand which requires the use of an Airport base station but seems to follow the same basic concept.
It probably is, but for instance I can't use WOL because it requires a packet that can't propagate through a router.
There is the possibility of having a smart router that allow WOL packets; some of them have a "act as a WOL proxy" option built-in, for examples.
So, basically it's a wake on lan, but that which works everytime some moron is doing a portscan or ssh-breakin attempt on your system? Why would such a system even have a off mode?
"SleepNotifier alerts SleepServer just before the client goes to sleep, and SleepServer ensures that all incoming traffic meant for the client comes to the proxy instead," Microsoft writes in another article titled "Trying to cure PC insomnia." "The proxy server's role is to monitor traffic and respond accordingly. For some requests, it responds on behalf of the client so the client can continue sleeping, and others it ignores. Some traffic, such as a user access request, causes the SleepServer proxy to awaken the client and present the user with apparently seamless remote access."
So basically we have a system that uses Wake On Lan to wake the remote machine automatically for user requests, but also avoids waking it for stupid shit like pings.
This is, in effect, what other researchers are trying to solve in a decent manner. Wake On Lan requires the waker to know a thing or two about the sleeping system (for example, that its sleeping) and simple frontend devices that have solved this in the past wake the system for everything and are also permanent proxies (proxying even when the system ISNT sleeping, for example)
"His name was James Damore."
It's also OpenSource: Note: see mDNSResponder source code at www.macosforge.org, which includes a full implementation of the DNS-SD/mDNS Sleep Proxy Service, available under the Apache 2.0 Open Source license. AND written up as a specification http://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns-11
Meaning if Linux or *BSD wanted to they too could also have it too. In fact, I'm really hoping that they do because I'd love to not have to send a WOL to my HTPC or Server when I want it to download something. I can just have my sheevaplug wget an address and have it wake itself.
It's also OpenSource [...] Meaning if Linux or *BSD wanted to they too could also have it too.
They could, if it weren't patented.