This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
schedule_wol [2023/05/08 05:00] – -reformatted BIOS WoL setting names, reorganize intro hogwild | schedule_wol [2023/08/07 22:44] (current) – [Schedule Tomato To "Wake Up" Network Devices] hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Schedule Tomato To "Wake Up" Network Devices ====== | ====== Schedule Tomato To "Wake Up" Network Devices ====== | ||
- | FreshTomato includes a Wake-On-LAN (WOL) function under the Tools menu. While often useful, this function must be performed manually every time you wish to wake a device. | + | FreshTomato includes a Wake-on-LAN (WoL) function under the Tools menu. While useful, this function must be performed manually every time you wish to wake a device. Instead, waking devices can be performed automatically using the Scheduler function. |
- | Instead, this can be performed automatically in FreshTomato using the Scheduler. Automating this process using the Scheduler has two main advantages. First, waking many devices on a network with many clients using Wake-On-LAN menu would be tedious and time-consuming. Doing the same in a script makes the process much more manageable. Second, the Scheduler allows you to wake devices automatically. You don't need to remember to do anything, as long as the Scheduler is functioning. | + | Automating |
+ | |||
+ | - First, waking many devices on a network with many clients using the Wake-On-LAN menu would be tedious and time-consuming. | ||
+ | - Second, the Scheduler allows you to wake devices automatically. You don't need to remember to do anything, as long as \\ the Scheduler is functioning. | ||
\\ | \\ | ||
Here are the available parameters for **ether-wake**: | Here are the available parameters for **ether-wake**: | ||
+ | |||
+ | \\ | ||
<code bash> | <code bash> | ||
Line 21: | Line 26: | ||
</ | </ | ||
- | \\ \\ For example, this will send a Wake-On-LAN signal to the device on your LAN with a MAC address of AB: | + | |
- | - Go to the Administration/ | + | - Go to the [[admin-sched|Scheduler]] menu. |
- | - Scroll to the Custom field of your choice (**Custom 1**). | + | - Scroll to the Custom field of your choice (in our example, |
- Check the corresponding **Enabled** setting. | - Check the corresponding **Enabled** setting. | ||
- In the **Time** menu, select 2:45 PM. | - In the **Time** menu, select 2:45 PM. | ||
- | - Check the checkboxes for Monday through Friday. | + | - Enable |
+ | - Enter **ether-wake -b AB: | ||
- | \\ | ||
- | |||
- | Enter **ether-wake -b AB: | ||
- | |||
- | \\ {{: | ||
- | |||
- | \\ | ||
===== Notes and Troubleshooting ===== | ===== Notes and Troubleshooting ===== | ||
- | For a PC to wake up from a WOL packet, it must have its WOL firmware setting enabled. Before testing scheduled | + | For a PC to wake up from a WoL packet, it must have its WoL firmware setting enabled. Before testing scheduled |
Most UEFI/BIOS interfaces will have a Wake-On-LAN option named similar to: | Most UEFI/BIOS interfaces will have a Wake-On-LAN option named similar to: | ||
Line 47: | Line 46: | ||
* AMI BIOS - "Power on by PCI devices" | * AMI BIOS - "Power on by PCI devices" | ||
- | WOL settings in the PC's operating system also must be enabled. For Details, see: [[https:// | + | \\ |
+ | |||
+ | WoL settings in the PC's operating system also must be enabled. For Details, see: [[https:// | ||
- | WOL functions generally assume a client PC/device starts from a powered off state. | + | WoL functions generally assume a client PC/device starts from a powered off state. |
\\ | \\ | ||