This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| schedule_wol [2023/05/07 04:06] – [Schedule Tomato To "Wake Up" Network Devices] hogwild | schedule_wol [2024/10/31 20:38] (current) – [Notes and Troubleshooting] 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. In the scheduler, you schedule the ether-wake command to automatically | + | \\ |
| + | |||
| + | Automating the process using the Scheduler has two main advantages: | ||
| + | |||
| + | \\ | ||
| + | |||
| + | - Waking many devices on a network with many clients using \\ the Wake-On-LAN menu would be tedious and time-consuming. \\ Doing this in a script makes the process much more manageable. | ||
| + | | ||
| \\ | \\ | ||
| Line 9: | Line 16: | ||
| Here are the available parameters for **ether-wake**: | Here are the available parameters for **ether-wake**: | ||
| - | \\\\ | + | \\ |
| <code bash> | <code bash> | ||
| Line 23: | Line 30: | ||
| </ | </ | ||
| - | \\ \\ For example, | + | |
| - | | + | \\ |
| - | - 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 ===== |
| - | \\ {{: | + | For a PC to wake up from a WoL packet, it must have its WoL firmware setting enabled. Before testing scheduled WoL events in FreshTomato, |
| - | \\ | + | Most UEFI/BIOS interfaces will have a Wake-On-LAN option named similar to: |
| + | * Asus BIOS/ | ||
| + | * AWARD BIOS - "PME Event Wakeup" | ||
| + | * AMI BIOS - "Power on by PCI devices" | ||
| - | ===== Notes and Troubleshooting ===== | + | \\ |
| - | For a PC to wake up from a WOL packet, it must have its WOL firmware setting | + | WoL settings in the PC's operating system also must be enabled. |
| - | * Power on by PCI-E or PCI (Asus UEFI) | + | [[https:// |
| - | * PME Event Wakeup | + | |
| - | * Power on by PCI devices | + | |
| - | WOL settings in the PC's operating system also must be enabled. For Details, see: [[https://www.howtogeek.com/ | + | WoL functions generally assume a client |
| - | WOL functions generally assume a client PC/device starts from a powered off state. | + | [[https:// |
| \\ | \\ | ||