This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tools-wol [2023/06/06 17:59] – [Wake on LAN] -condense, formatting hogwild | tools-wol [2023/08/05 18:32] (current) – [Wake on LAN] -fix incorrect link hogwild | ||
---|---|---|---|
Line 7: | Line 7: | ||
* Devices already active in the ARP table. | * Devices already active in the ARP table. | ||
* Devices defined in a static DHCP assignment. | * Devices defined in a static DHCP assignment. | ||
- | * Devices defined manually in the //Dnsmaq Custom configuration// | + | * Devices defined manually in the //Dnsmaq Custom configuration// |
\\ Some devices might appear on this menu without their hostname defined/ | \\ Some devices might appear on this menu without their hostname defined/ | ||
Line 25: | Line 25: | ||
===== Wake on LAN Notes and Troubleshooting ===== | ===== Wake on LAN Notes and Troubleshooting ===== | ||
- | For Wake On LAN to work on your client device, it must be configured to respond to magic packets, both in firmware and in software. | + | Your client device must be configured to respond to magic packets, both in firmware and in software, for WoL to wake it. Enabling the firmware option causes the device' |
Most PCs have a Wake-on-LAN option that must be enabled in the UEFI or BIOS, named something like: | Most PCs have a Wake-on-LAN option that must be enabled in the UEFI or BIOS, named something like: |