This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
schedule_wol [2021/09/22 00:12] – hogwild | schedule_wol [2023/05/08 05:00] – -reformatted BIOS WoL setting names, reorganize intro 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. However, within FreshTomato, | + | 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. |
- | For a PC to wake up from a WOL packet, it must have its WOL firmware setting enabled. Before testing scheduled WOL events | + | Instead, this can be performed automatically |
- | * Power on by PCI-E or PCI (Asus UEFI) | + | \\ |
- | * PME Event Wakeup | + | |
- | * Power on by PCI devices | + | |
- | WOL settings in the PC's operating system also must be enabled. See here for details: \\ | + | Here are the available |
- | [[https:// | + | |
- | + | ||
- | WOL functions generally assume a client PC/device starts out from an off state. | + | |
- | [[https:// | + | |
- | + | ||
- | To schedule WOL events in FreshTomato: | + | |
- | + | ||
- | - Navigate to Administration/ | + | |
- | - Scroll to the Custom field of your choice. Check **Enabled** | + | |
- | - In the **Time** menu, select a time (e.g. 9:30 AM) or frequency option \\ (e.g. every 30 mins) for when or how often you want the task executed | + | |
- | - Now check the **Days** you want it executed or Every day | + | |
- | + | ||
- | \\ The command to execute is '' | + | |
<code bash> | <code bash> | ||
- | ether-wake --help | ||
- | BusyBox v1.33.1 (2021-08-11 16:11:49 CEST) multi-call binary. | ||
- | |||
Usage: ether-wake [-b] [-i IFACE] [-p aa: | Usage: ether-wake [-b] [-i IFACE] [-p aa: | ||
Line 39: | Line 21: | ||
</ | </ | ||
- | | + | \\ \\ |
- | <code bash> | + | - Go to the Administration/ |
- | ether-wake -b AB: | + | - Scroll to the Custom field of your choice (**Custom 1**). |
- | </code> | + | - Check the corresponding **Enabled** setting. |
+ | - In the **Time** menu, select 2:45 PM. | ||
+ | - Check the checkboxes for Monday through Friday. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | 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" | ||
+ | |||
+ | 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. |
- | {{: | + | \\ |