I'm trying to get wake-on-wireless working across a LAN behind a non-Airport router, but having trouble. Wondering if anyone here has gotten something like this to work. (Apologies in advance for the lengthy question.)
1) Setup -- Router is a WRT54G with DHCP enabled on the LAN side. -- Bonjour sleep proxy is running on a 2nd-gen AppleTV that is hard-wired to the router. -- Target (machine to be woken) is an iMac running 10.9.5 and connects via wireless only. -- Client (machine doing the waking) runs Ubuntu 12.04 LTS and is hard-wired to the router. It has the avahi suite running, as well as ssh and both etherwake and wakeonlan. 2) Steps taken so far -- Followed tutorial at <http://stuartcheshire.org/SleepProxy/index.html>. But the tutorial contemplates using an always-on Mac as the SleepProxy provider, so I can't see how to do any of part one ("Setting up the Sleep Proxy Mac"). -- Verified (via both "avahi-browse -tva" from the Ubuntu box and "dns-sd -B _sleep-proxy._udp local" from one of the target Macs, when they are awake) that the SleepProxy is running on the ATV. However, dns-sd shows its Instance Name as "70-35-60-63.1 My Apple TV", which I think means its priority = 70. I'm not sure how to change it to priority = 10, as per the tutorial, nor whether or not this matters. -- Verified that "Wake for network access" is checked in System Prefs>Energy Saver (according to <support.apple.com/kb/ht3774>, this means the machine supports both wired and wireless WOL). -- Verified that remote login is enabled in System Prefs>Sharing, and that I can connect via ssh when the Mac is awake. -- Applied the "-UseInternalSleepProxy 0" tweak to com.apple.mDNSResponder.plist (as described in Part Two of the tutorial). -- Set both PrioritizeNetworkReachabilityOverSleep and DarkWake (as described at http://mactips.dwhoard.com/mactips/system/wake-on-demand). But would strongly prefer to avoid setting computer sleep = "Never," as described in "Test #6" et seq. -- Verified that the WRT54G _does_ allow pings to the broadcast address from the LAN side. 3) Where this fails -- When the target machine is left alone overnight, it goes into "full" sleep (presumably display _and_ hard drive). When this happens, it disappears from the network altogether (i.e. not visible to avahi-browse) and does not wake in response to etherwake, wakeonlan, or ssh connection attempts. It remains this way until someone physically wakes up the machine (via keypress or mouse), after which everything works as expected. My goal is to be able to wake the Mac via the network, rather than having to do so manually. One or two folks suggested that this won't work at all without an Airport, though the KB article above seems to suggest that this shouldn't be the case. Can anyone spot something I've overlooked? Thanks very much in advance, -HJ _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
