![]() Loaded: loaded (/etc/systemd/system/wol.service enabled vendor preset: enabled)Īctive: inactive (dead) since Mon 23:10:52 CEST 1min 57s ago Sudo chmod 755 /etc/rc0.d/wol_poweroff.sh & sudo chmod 755 /etc/rc6.d/wol_poweroff.sh Created script to bring the ethernet interface down properly at shutdown :Ĭp /etc/rc6.d/wol_poweroff.sh /etc/ rc0.d/wol_poweroff.shįinally changed permissions to make it executable: I tried sending packets to the combination of host's MAC and IP (as well as broadcast to 255.255.255.255), ports 7,9,4343,4000,etc.When the machine is powered off, and I send magic packets using apps like "wol" (from a windows host), an android app (landroid), I understand that they are reaching the NIC as I can see the ethernet port flashing, but the machine doesn't boot.When the machine is powered on, I successfully tested receiving magic packets using netcat.I also created a systemd service " wol.service", to also set the eno1 interface's wol to "g", using ethtool (see #3 below).Created script to bring the ethernet interface eno1 down properly at shutdown, based on this bug (see #2 below).Updated cat /etc/network/interfaces so that at every boot, it sets the vmbr0 interface's wol to "g", using ethtool (see #1 below). ![]() The NIC supports WoL and is (/was already correctly) enabled and set to "g".The BIOS (is up-to-date) supports WoL and is enabled. ![]() At this point I am not sure if it is a configuration issue or a BUG? I can't get Wake on Lan (WOL) to work with Proxmox, no matter what. I then installed Proxmox 7 (5.11.22-4-pve) on the same hardware. I was able to wake up the system from a "Hibernate" or "Sleep" mode by sending a magic packet from another windows host. disable "reduce speed on power down") and the UEFI BIOS to make it work. I had to make some changes in the adapter settings (eg. To make it simpler to use wakeup.exe from within a Cygwin session, I just created a little script in the Cygwin bin directory, one that included the MAC address of the machine in question: $ echo "/cygdrive/c/bin/wakeup.I confirmed that Wake On Lan works with Windows 10 Pr o on a Lenovo ThinkStation P310 with onboard Intel I219-LM GB Ethernet controller. I could then SSH into the box and do my wacky bit of science. You can get the MAC address in many ways, but an easy one is to run ifconfig on the server (may need to be root): c:\bin\> wakeup 00:25:F3:C9:98:F8Īt the prompt and… bingo. I mean, who needs a GUI for this kind of thing!Ĭopied wakeup.exe into my bin dir - no need for admin, which is good - and ran it - note that 00:25:F3:C9:41:F8 is the MAC address of the Ethernet card on the server in the shed, and the BIOS is set to allow WOL. (Better things to do.) If does not work out of the box … into the bin! PS> Uninstall-Module -Name WakeOnLanįound a utility described as ‘a bit old’. On my old laptop, that takes a while! It installed but did not work - did not even run. Found a couple of options.įollowing … PS> Install-Module -Name WakeOnLan I looked for but did not see anything in the Cygwin repository. The laptop runs Windows 10, and I use Cygwin on Windows. So let’s assume the box was put to sleep using the pm-suspend command. So, the simple plan is to install pm-utils on the box (Devuan) and use a wake-on-LAN (WOL) utility on the laptop. Now, suspending does not zero power use, but does cut it down a lot. The idea is that we don’t want the fan and suchlike making noise in the house when the machine runs overnight, so it is in the shed, but I also don’t want it wasting electricity by running when not needed. I want to be able to control it from my laptop. I have a Linux box in the shed that I want to be able to log in to using SSH to run numerical calculations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |