![]() So while industry-wide Wake-on-LAN is a network device feature based on a magic packet (that requires no OS interaction), Mac's magic "wake-on-LAN and also still respond to pings" is because they haven't actually put the whole OS to sleep and/or have a separate network stack still running in sleep mode. My assumption is this is because Apple controls the hardware and software stack. And after I've logged out, 15 minutes later it will go to sleep again. This 2nd property ends up being really nice: it automatically goes to sleep and saves power when not in use and doesn't require any extra thought to power on when I want to ssh into it. It will wake up automatically upon incoming ssh connection, no Wake-on-LAN required. It still responds to ping on the network. The command to enable Wake-on-LAN is as follows: sudo ethtool -change < Your ethernet interface name > wol g This will enable the service and allow your PC to be turned on by a network device. you should see a g next to wake on lan after writing the second command.ifconfig -a Check the ethernet adapter to see what 'Wake-on' is set to. ![]() apt install wakeonlan Find your ethernet adapter, mine was called 'enp10s0' (usually called 'eth0'). I have noticed that it goes to sleep and has two distinct properties separate from any Linux machine I have while asleep: Install the wakeonlan program on the computer you want to be able to wake up remotely. I have been using Wake-on-LAN successfully for many years now for a number of my Linux devices. Enable wake on lan in BIOS, enter the BIOS setup and look for something called 'Wake up on PCI event', 'Wake up on LAN' or similar.
0 Comments
Leave a Reply. |