Just to make sure I'm understanding this correctly: all clients that want to wake it up need to be running this special code, right? You mean wake on ethernet doesn't simply wake on any device on the LAN trying to access that IP, but requires a specific application to be running on each client machine that hopes to wake it up? If so, then I had the wrong idea of what wake on ethernet was I thought it would wake up to any IP packets being sent to it as per normal access (not requiring a special application). Pwilson wrote:You can use Wake-On-LAN to wake up your NAS from an " off" state.
On the NAS I simply ran the following command: To wake up my NAS, I simply need to determine the MAC address of the gateway device on the NAS, so that I can wake it from other devices on my network. Use '-u' to see the complete set of options. Specify the Ethernet address as etherwake -helpĮtherwake: option requires an argument - 'p' Selecting previously unselected package wakeonlan. 382710 files and directories currently installed.) Selecting previously unselected package etherwake. The following NEW packages will be installed:Ġ upgraded, 2 newly installed, 0 to remove and 56 not upgraded.Īfter this operation, 119 kB of additional disk space will be used. The following extra packages will be installed: Libmozjs22d libsvga1 python-apsw python-utidylib xulrunner-22.0 The following packages were automatically installed and are no longer required:
REMOTE WAKE UP QNAP INSTALL
Code: Select all apt-get install etherwake
0 kommentar(er)
