Wake-on-LAN (WoL) is an Ethernet or token ring computer networking standard that allows a computer to be turned on or awakened by a network message. The message is usually sent to the target computer by a program executed on a device connected to the same local area network, such as a smartphone.It is also possible to initiate the message from another network by using subnet directed. Wake-on-LAN is a hardware/software solution allowing a computer to be woken up remotely. A computer that has an Internet connection and is Advanced Configuration Power Interface (ACPI) compliant can be turned on remotely from anywhere in the world. Wake-on-LAN must be enabled in the desktop board BIOS and then configured in the operating system.
- Wake On Lan Bios Settings Dell
- Setting Up Wake On Lan Windows 10
- Wake On Lan Bios Settings Asus
- Wake On Lan Bios Setting
- How To Setup Wake On Lan
The following are my notes for setting up my unRAID server to sleep to S3 state and then wake up to Magic Packet. This is a 'For Beginners, By Beginners' effort - there's very little original work here. I just tried to piece together whatever I needed from various threads on the unRAID forums. My server uses a Foxconn A7GM-S AMD 780G/SB700 based motherboard, and I am running unRAID 4.4.2. In general, I think the below is procedurally correct - although different motherboards will have different capabilities and driver concerns. Also - all computers with access to my unRAID server are Windows machines, I do not know how any of this would change if accessing from a machine with a different OS. The following assumes the use of a Windows machine.
1. BIOS settings for S1 / S3 sleep state
- Review BIOS settings on unRAID server for allowable sleep states.
- On my motherboard, the setting is “ACPI Suspend Type” and provides option to either suspend to S1 or S3 sleep state. Select S3.
2. BIOS settings for WOL
- Review BIOS settings on unRAID server for “Resume by” options.
- My motherboard has a setting for “Resume by LAN”. It can be enabled or disabled. You need to enable “Resume by LAN”.
3. Double check NIC WOL settings
- Boot unRAID server.
- Use the Terminal on the WebUI (present in v6, one of the buttons in the upper right corner, or fall-back to SSH or if absolutely neccesary Telnet) and type ethtool eth0 from the command line
- You're looking to confirm that the setting for “Wake-on” includes 'g' . . . which is the option for allowing Wake on Magic Packet. We’re essentially confirming the BIOS settings from Step 2 above.
- The results of my ethtool eth0 command are as follows:
- If the wake-on setting does not include 'g', you can set it manually by typing the following at the server command line:
- If necessary, you can add the above line to your 'go' script, but I've not had a problem with my machine keeping the setting once it is set and the appropriate Wake on LAN setting is enabled in BIOS.
4. Download wolcmd executable
![Wake Wake](https://i.stack.imgur.com/WA1ZA.jpg)
- Go to Depicus 'Wake on Lan' page, select Download button near the bottom
- I placed the file in C:Program FilesWOLcmd (location becomes important in next step)
- There are other Magic Packet tools available, this is just one that I found simple to deal with.
5. Generate Wakeup.bat batch file (or download mine from here)
- My batch file is simply two lines
- Change folder directory as necessary depending on where you saved wolcmd.exe.
- Enter the MAC address of your unRAID server in the second line instead of 'MAC'
- Place the batch file on your desktop for easy access.
- Copy of my batch file attached to this unRAID forum post
6. Manually test sleep and WOL
- Spin-down drives (I'm not certain that this is required. I did force sleep from the active state (spinning) once before and got a parity check on wake-up. I'll test some more.)
- Telnet to server and enter echo 3 >/proc/acpi/sleep
- Ensure server sleeps
- Execute Wakeup.bat file
- Ensure server wakes up
- Repeat / test until comfortable
Note: Some people have reported that their system misbehaves on the second or later sleep, so you should test sleep and wake-up for a while and make sure everything is correct. In fact, I just noticed that waking up from S3 sleep, my system does not negotiate a gigabit connection and I go from 1000Mb/s to 100Mb/s after the initial sleep. So I have a little more work to do – I’m guessing a Linux driver issue?
7. Record hard drive references (sda, sdb, etc)
- From unRAID ‘Devices’ page, make note of the hard drive references in your system. You’re building a list of hard drives in the system for use in the sleep script.
- I am currently only using two SATA drives, so my drive references are: sda and sdb
Phonerescue 3 4 4 download free.
8. Generate sleep script, or download mine from here
8. Generate sleep script, or download mine from here
- I copied OMV's sleep script verbatim from this unRAID forum thread, and then edited the lines shown below in bold:
- timeout=5 and count=5 are programmable timers to set the delay from spin-down until sleep. This sets the delay to five minutes after spin down, OMV's original script was 15 minutes.
- drives= line needs to be edited to reflect the drives that you want to be checked for status (idle or spinning). Again, my server only has two drives (sda and sdb), so I edited accordingly. Be aware that this drive list can change when upgrading unRAID or modifying your hardware. It can even change from one boot to the next. For example, your flash drive may be assigned sdc on one boot, but sdd on the next boot, with one of your hard drives assigned to sdd the first time, and sdc the next time.
- Copy of my s3.sh sleep script attached to this unRAID forum post
9. Save script onto flash drive in specified location
- I titled my sleep script s3.sh and saved in /boot/custom/bin
IMPORTANT: 'boot' is already the name of the root directory of your flash device. So, if you save your script as per this example, do not create another 'boot' directory. Doing so will cause unRAID to lose track of your config directory and your entire configuration will be lost (unless previously backed up elsewhere.)
10. Edit ‘go’ file to call script
- I added the following lines to my go script to initiate the sleep script during boot:
- Make sure you adjust file directory structure as necessary depending upon where you saved your s3.sh script.
Rightfont 3 1 0 download free. 11. Re-boot / test
Good luck!
Additional Information
- See the Wake On LAN topic for many links to related discussions
Wake On Lan Bios Settings Dell
Retrieved from 'https://wiki.unraid.net/index.php?title=Setup_Sleep_(S3)_and_Wake_on_Lan_(WOL)&oldid=10107'
HELP FILE
Wake Sleeping Computers (Wake-on-LAN)
You can use Wake-on-LAN (WoL) to attempt to wake up sleeping (Windows and Mac) or powered-off (Windows) computers from your Unattended Remote Support Computers Inventory. This allows you to then connect to computers that would otherwise have been offline and unreachable.
Note: In order for you to successfully wake up (PC and Mac) or power on (PC) a computer, Wake-on-LAN must first be enabled.
Wake-on-LAN Requirements
In order for you to wake up a sleeping or off (i.e., 'target') computer, all of the following must be true:
- The target computer has the GoToAssist Customer desktop application installed with unattended access set up.
- The target computer’s status is 'Offline' (i.e., not 'Online', 'In Session', 'Blocked' or 'Removed').
- The target computer is connected to the local area network (LAN).
- The target computer has WoL enabled (see Enable Wake-on-LAN for more information).
- At least 1 other unattended support computer within the target computer’s network is already “awake” (i.e., 'Online', 'In Session' or 'Blocked') in order to send the “wake up/power on” request.
- The target computer is connected to the network by ethernet rather than WiFi (highly recommended).
- The target computer is plugged in to its power adapter rather than running on battery alone (Mac only).
Note: Even if all of the following is true, the computer may still not wake up if it encounters another error.
Enable Wake-on-LAN
Setting Up Wake On Lan Windows 10
Complete all of the following steps on the target computer:
- Enable WoL in the computer’s Basic Input/Output System (BIOS) (Windows only). Note: Check the computer’s user guide for instructions; if there is no option in the computer’s BIOS to enable WoL, then it may already be enabled by default.
- Enable WoL in the computer’s network adapter (Windows and Mac).Example: In a Windows 7 for Intel(R) 82567LM-3 Gigabit network adapter/connection, this can be done by going to the Control Panel > System and Security > Device Manager, and right-clicking the Network Adapter. Then select Properties > Power Management tab > “Allow this device to wake the computer” check box. In OS X 10.11 (El Capitan), this can be done by going to System Preferences > Energy Saver > 'Wake for network access' check box.
Attempt to wake a computer via the GoToAssist Expert desktop application
- Ensure that the computer meets all of the requirements listed above.
- Open the Unattended Support Computers window.
- If the application is already open and running in the background, right-click the GoToAssist Expert icon in the system tray select View Unattended Support Computers(Windows) or use the Application menu and click Window > My Unattended Computers (Mac).
Windows
Mac
- If the application is not already running in the background, open it and log in. Then click Unattended Support in the Viewer toolbar and select View Unattended Computers.
- Use the Groups in the left-navigation to locate the target computer (which will be marked as “ Offline”) and click the Power On button.
Note: Although the Power On button appears for all unavailable computers (i.e., Offline), the WoL feature does not work for computers that do not meet the requirements listed above (i.e., if the computer is offline because it is not connected to the network).
- One of the following dialogs will appear to confirm whether or not the “power on” request was successfully sent. Click OK to close it.
- Successful – If at least 1 Unattended Support Computer within the computer’s network is Online, In Session or Blocked, then the following message appears: “[Computer] may power on momentarily. We were able to send a power on request to [computer], but it may not power on because it’s offline. Please wait a moment before refreshing the unattended computers list and trying again.”
Wake On Lan Bios Settings Asus
Note: Although the request was successfully sent, the computer may still not wake up if it does not meet all of the requirements listed above, or if you encounter another error.
- Unsuccessful – If no other Unattended Support Computers within the target computer’s network are online, the following message appears: “To power on [computer], you must have another online unattended computer on the same network.”
- If the “Successful” dialog appears, then wait a few moments and click Refresh at the bottom of the Unattended Support Computers list.
- If the “Power On” request was sent and successful, the Unattended Support Computer’s status will change to “ Online” with a Connect button (instead of the Power On button). Click Connect to start an Unattended Support Session with the computer.
Wake On Lan Bios Setting
- If the “Power On” request was sent but was not successful, the Unattended Support Computer will remain unchanged (with the “ Offline” status and Power On button), but there will be no other indication that it did not work.
- If the “Unsuccessful” dialog appears, then another Unattended Support Computer on the target computer’s network must be turned on and connected to a network before a “power on” request may be successfully sent to the target computer.