Remote Wake-Up does have some security issues. Moreover, different hardware have a variety of low-power states, such as a fully-off state, sleep or hibernation some may allow wake-up while others may not. This can make the setup and testing frustrating for the IT network technician. To function reliably, Remote Wake-Up requires the proper BIOS and NIC and sometimes the proper OS and support for the final router are required.
The magic packet does not provide any delivery confirmation signal back to the sending computer.įor Remote Wake-Up to function, there are parts of the network/computer interface that need to remain powered, even though the computer is shut off and some power is consumed for this purpose, as long as the computer is plugged in to a powered electrical outlet. The magic packets use the data link layer in the OSI model as they are sent to all NICs using the network broadcast address. However, some operating systems can control the operation with hardware drivers. Support for this feature is implemented on the motherboard (in the BIOS) along with the network interface or firmware. Remote Wake-Up is independent of the operating system, or network interface card (NIC), used by the computer. The Remote Wake-Up feature goes by many names, including: wake on LAN (WOL), wake on WAN, wake up on LAN, power On By LAN, power Up By LAN, resume by LAN and resume on LAN.įor computers communicating via WiFi, the wake on wireless LAN” (WoWLAN) supplementary standard must be used. However, there are exceptions making it possible to remotely wake-up a computer from outside its LAN. Generally, Remote Wake-Up will only work if magic packets are sent from a computer on the same local area network (LAN) or within the current network subnet.
0 kommentar(er)
