4 ms·

I only had one problem with it, and that was that it isn't enough to enable it in the BIOS, but I needed to flip a switch on Windows and set up a systemd servic

I only had one problem with it, and that was that it isn't enough to enable it in the BIOS, but I needed to flip a switch on Windows and set up a systemd service on Linux (I dual boot). For Linux set it to "g": https://wiki.archlinux.org/title/Wake-on-LAN#Make_it_persistent https://wiki.archlinux.org/title/Wake-on-LAN#Make_it_persist... For Windows you need to enable "Wake on Magic Packet": https://www.windowscentral.com/how-enable-and-use-wake-lan-wol-windows-10 https://www.windowscentral.com/how-enable-and-use-wake-lan-w...

striking 2y ago
"set it to 'g'". Awesome. G for maGic, I presume?
- BenjiWiebe 2y ago
  Yep, pretty sure. m is for multicast. From arch wiki: d (disabled), p (PHY activity), u (unicast activity), m (multicast activity), b (broadcast activity), a (ARP activity), g (magic packet activity)
ryandrake 2y ago
I always wondered: why make it so difficult to turn on? Is it a security issue? I mean, an off-by-default OS setting and an off-by-default BIOS setting? How dangerous is this thing??
- tjoff 2y ago
  It draws more power because the NIC can't power off completely. So Microsoft and every hardware vendor are incentiviced to turn it off to look good. (And probably to please regulations) That it is defaulted off I feel is motivated, but to make it so hard to turn it on is pretty pathetic. The fury Microsoft generated by turning it off in a Windows update still fuels me. I had a remote PC that I need to access remotely during holiday season. And Microsoft turns off my ability to power it on, with me left trying to figure out why I can't access the machine anymore.