I have some unique hardware where the onboard NIC's WoL output is wired to cause a system reset, I believe by NMI, instead of causing a power-on.
It was made like this, I think, to facilitate remote reboot without incurring the cost of a switched PDU or IPMI.
But it looks like the WoL capability is suppressed once an OS loads. I noticed that memtest 86 doesn't surpress it, but linux does. I tried ethtool -s wol a/u/m/b/a/g/s
Am I on the right track? How can I get WoL to stay awake while the OS is running?
/ # lspci -nn | grep -i net
01:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
/ # ethtool -i
ethtool -i eth0
driver: e1000e
version: 2.3.2-k
firmware-version: 2.1-0
bus-info: 0000:01:00.0
/ # uname -a
Linux (none) 3.19.0 #1 SMP Mon Oct 19 15:48:25 CDT 2015 x86_64 GNU/Linux
/ #
Target Kernels are latest CentOS, Ubuntu, Debian, Windows, Proxmox(Debian) and VMware.
My hope was that WoL would function 'outside' of the OS. I would accept that the OS might be able to disable it if it wanted to, but that by default, it would not, and that if WoL was simply enabled in bios and supported by hardware, it would work consistently no matter what the OS was doing.
lspci -nn
line of that NIC? The driver used by the NIC can be identified withethtool -i
. You might also identify the version of the Linux kernel you're using or planning to use in this hardware. – telcoM Feb 20 at 15:20