This cookie is set by GDPR Cookie Consent plugin. These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. something happening between cron and the user session has reset wake-on back to d login as malcolm: only upDone.txt and cronDone.txt exist, both give “wake-on=g” as expectedĨ/ BUT now run: sudo ethtool eth0 to confirm persistence and find that “wake-on=d” NOT expected. (c) create a cron ‘root’ job by creating /etc/cron.d/eth0_wol containing: root ethtool -s eth0 wol g & ethtool eth0 > /home/malcolm/cronDone.txt”ħ/ reboot. (b) edit: /etc/network/if-up.d/ethtool to append an additional action: “ethtool -s eth0 wol g & ethtool eth0 > /home/malcolm/upDone.txt” (a) set a udev rule similar to post #83668 with action: “ethtool -s eth0 wol g & ethtool eth0 > /home/malcolm/udevDone.txt” (presumably, wol must be “g” when NAS goes down, in order for it to come up on receipt of a magic packet) My logbook says:Ģ/ DC7700 bios: set “wake on lan = enable” done, power-down, power-upģ/ ethtool eth0: gives “wake-on=d” disabled as expectedĤ/ ethtool -s eth0 wol g & ethtool eth0: gives “wake-on = g” as expectedĥ/ reboot: wake-on back to “d” as expected, so need action to set “g” at each boot-up, so g is “persistent” I want to wake it up by sending magic packets from various workstations on the same LAN subnet. I have a NAS built on an HP DC7700 SFF desktop m/c running Antix 19.4 64 bit (fully apt upgraded at 12 sept 22). This topic was modified 11 months, 4 weeks ago by sybok. The HW part of output of ‘inxi -Fxz’ is the same as in the following link: The only thing that I can think of is improper value of ‘SUBSYSTEM’. I may try the alternate ‘cron’ approach (where adding user ‘root’ after the specifier may be needed based on some internet search) instead but I am curious where the problem is. The ‘udev’ method works in Fedora (tested: reboot from Fedora and reboot from antiX).ĪCTION="add", SUBSYSTEM="net", NAME="enp*", RUN+="/usr/bin/ethtool -s $name wol g"ġ) ‘/usr/bin/ethtool’ -> ‘/usr/sbin/ethtool’ (needed in the case of both systems).įor some reason, the antiX version failed to work. There is a single ethernet interface ‘eth0’ (named ‘enp3s0’ in Fedora). The PC dual boots with Fedora and Fedora “owns” the grub. I found a very useful Arch wiki-page dedicated to this topic. The only thing I haven't looked into is that this is a dual boot machine, so maybe the second OS is messing things up, but I'm always shutting down from the Linux side that I'm working on, so it is my understanding that the OS should leave the machine listening for magic packets.I intend to enable WOL on my Linux-powered desktop workstation at work. However, I cannot get the target machine to wake up by issuing the command wakeonlan I can SSH between the machines, so I know they have a LAN connection. I have the MAC address for the target machine and a wakeonlan app downloaded to my current machine to send magic packets. Ethtool says my WOL status is 'g,' which the guides say is the correct status. Wake On LAN is definitely enabled in my BIOS. I tried following this guide, this guide, a bunch of other help questions, and even the Arch wiki. I'm trying to setup my desktop (which is running 20.04) for WOL.
0 Comments
Leave a Reply. |