Write down the Mac Address of the device you’d like to wake up – miniWOL does not need this, but most other applications do. Enable Wake On Lan on te device which you’d like to wake up. That’s why a standard was defined with data of a specific format – the so called “Magic Packet”.The Magic Packet ( UDP) is typically send to port 9, some systems default to port 7, and some systems allow you to define your own port number.Normally just one single packet should do the trick, but most Wake On Lan applications actually send more than one packet – just to make sure.To get started with Wake On Lan, you’ll need to follow these steps: While the NIC (network interface controller) is listening, a lot of traffic might pass that might not even be intended for this network connection, so just listening to network traffic would keep your network device awake even when you don’t want it to be awake. There can be several motivations to do this save on power, save on the environment, save on wear-and-tear of your equipment, etc.To be able to use Wake On Lan, yoru computer requires the network card of this device to be semi-awake, and still listen to traffic when the computer is in standby, just in case a “ magic packet” is being send to the device.Just enable it in one spot. Others (Windows and Linux for example) can make it a little bit more of a challenge, sometimes you will need to set the option in the BIOS/UEFI, sometimes in the drivers, or sometimes both. So be aware and not surprised to run out of juice before you can use your laptop for example.Obviously, this also means that you device (computer) needs to support going to standby, and have BIOS and/or driver support to handle a “power on” signal when the network card sees a correct Magic Packet.You can already guess that there is no simple “one-fits-all” description on how to do this.Some Operating Systems (mostly NAS devices, and MacOS X devices) make it easy for the user. The network card needs to be powered by your computer, even when the computer is in standby, and should be able to monitor network traffic on a defined port, so it can catch an incoming Magic Packet and see if it’s intended for this computer (MAC address).Since Wifi is often used in mobile devices, then this would mean that your battery keeps being drained, for those devices that support Wake On Lan over WiFi. Test the tool by sending the Wake On Lan Packet and verify that your device fires up.To enable Wake on Lan, your network card (or WiFi card) needs to be Wake On Lan compatible – and not all of them are (especially very cheap or “older” network cards).
![]() ![]() ![]() BIOS settingsSome systems, typically Windows or Linux based, require you to do some BIOS settings to enable Wake On Lan on a BIOS level.For some of these systems, this would be enough. Not every device supports Wake On Lan. Other systems require 3rd party applications or hackery to get the server to fall a sleep again.It goes a little beyond this article to describe how to get your computer to go into standby based on your criteria, but most often these settings are found under the power management settings of your operating system.Enabling Wake on Lan on your server, computer, NAS or other device, very much depends on the capabilities of that device. Unless you’re happy with pressing the “go to standby” button on your device of course.Power Management is on some systems very well implemented, which makes it easy to enable “falling a sleep”. Best way to protect my mac for free macIf Wake On Lan still doesn’t work, time to check the Operating System settings.Below a few screenshots of different BIOS variants.Check out my article (look for Example 3) which explains how to login to SSH securely without a password, and wake up a MacBook Pro without even using a Wake On LAN application.Note: You’ll still need to do the settings listed below, and your MacBook needs to be powered by a power brick, and the lid (potentially) must be open. Please mention the type of hardware/PC you’re using, others will tank you for helping out.Doing the settings in the BIOS might be enough to get things going. If not explicitly called “Wake On Lan”, look for something like “ Power On by PCI device” or “ Wake up by PCI device“.If you found different settings, then please help us out, and post your settings in the comments. Look for “ Wake On Lan“, “ Remote Wake Up“, “ WOL“, etc. For a good list of BIOS Hotkeys, see CPUCare – BIOS Access.To find your settings in your BIOS, if needed: Press to access system configurationTake note of the key – this is the key or key combination you should press to get into the BIOS.Common keys are: F1, F2, Del, and F12. Wake For Network Access Not Working Mac OS X VersionsNow scroll down, and uncheck “ Turn on fast startup (recommended).”.The consequence will be that your PC will start up a little bit slower, which probably does not affect the speed of coming out of standby, but you’ll be able to use Wake-on-LAN.There are numerous Linux variants available and each might have it’s own quirks when it comes to setting up.I strongly recommend checking the BIOS to see if it has Wake On Lan enabled before doing anything else. You will have to disable Fast Startup.You can do this by going to “ Control Panel” “ System and Security” “ Power Options” “ Choose what the power buttons do” “ Change settings that are currently unavailable”. That’s all there is to it, you can close this window now.Note: Enabling Wake On Lan on a laptop will drain your battery even when you’re not using your laptop.Note: Older Mac OS X versions might call this option in Energy Saver “Wake for Ethernet network administrator access”.Windows 8 and Fast Startup – WOL doesn’t work or not available …Windows 8 might have issues with WOL when Fast Startup is enabled. In my test setup:Eth0 Link encap:Ethernet HWaddr 00:0c: 29: 15:c8:8cInet addr:192.168.1.195 Bcast:192.168.1.255 Mask:255.255.255.0Inet6 addr: fe80::20c:29ff:fe15:c88c / 64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1RX packets: 280481 errors: 6 dropped: 0 overruns: 0 frame: 0TX packets: 143653 errors: 0 dropped: 0 overruns: 0 carrier: 0RX bytes: 379209958 ( 379.2 MB ) TX bytes: 11171656 ( 11.1 MB )RX packets: 3969 errors: 0 dropped: 0 overruns: 0 frame: 0TX packets: 3969 errors: 0 dropped: 0 overruns: 0 carrier: 0RX bytes: 401117 ( 401.1 KB ) TX bytes: 401117 ( 401.1 KB )I know my computer has the IP address 192.168.1.195 (line 4), looking up where this list starts, we see in line 3 that our NIC is called “ eth0“.
0 Comments
Leave a Reply. |
AuthorRoger ArchivesCategories |