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 [2023/05/07 03:53] – [Notes and Troubleshooting] -Complete Windows WoL link hogwild | schedule_wol [2023/06/07 16:20] – [Notes and Troubleshooting] -spelling, formatting 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 you can also schedule a WOL signal to automatically be sent to any local device at a preset time by using the **ether-wake** command in conjunction with the scheduler. | + | 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. |
- | Here are the available parameters for **ether-wake**: | + | Instead, waking devices can be performed automatically using the Scheduler function. Automating the process by 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. The ether-wake |
\\ | \\ | ||
+ | |||
+ | Here are the available parameters for **ether-wake**: | ||
<code bash> | <code bash> | ||
Line 19: | Line 21: | ||
</ | </ | ||
- | \\ \\ For example, | + | \\ \\ For example, |
- | - Navigate | + | - Go to the [[admin-sched|Scheduler]] menu. |
- | - Scroll to the Custom field of your choice (e.g. **Custom 1**). | + | - Scroll to the Custom field of your choice (in our example, |
- | - Tick its **Enabled** | + | - Check the corresponding |
- In the **Time** menu, select 2:45 PM. | - In the **Time** menu, select 2:45 PM. | ||
- | - Tick the checkboxes for Monday through Friday. | + | - Check the checkboxes for Monday through Friday. |
- | + | ||
- | 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 |
- | * Power on by PCI-E or PCI | + | Most UEFI/BIOS interfaces will have a Wake-On-LAN option named similar to: |
- | * PME Event Wakeup | + | |
- | * Power on by PCI devices | + | |
- | WOL settings in the PC's operating system also must be enabled. | + | * 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. | ||
+ | |||
+ | WoL functions generally assume a client PC/device starts from a powered off state. | ||
+ | |||
+ | \\ | ||