I have had some luck disabling Wake-On-LAN on the systems that don’t need it, or enabling higher sleep modes on the systems where that is available. My pet theory is that a lot of systems are constantly looking at what is active on the network and those pings are keeping the machine awake.
My pet theory is that a lot of systems are constantly looking at what is active on the network and those pings are keeping the machine awake.
or if you meant that, computers are normally not pingable when they are asleep. net adapters only wake the computer when seeing a magic packet with their mac address in it, and it is the operating system that receives the ping request and decides to send back a ping response.
an exception is when it is set up to wake on some network traffic pattern, but few net adapters support that mode of operation
Meanwhile every Windows 10 install I’ve ever had fails to go to sleep 90% of the time, and none of the powercfg commands reveal why.
S0 Standby and its consequences have been a disaster for the computing race
I have had some luck disabling Wake-On-LAN on the systems that don’t need it, or enabling higher sleep modes on the systems where that is available. My pet theory is that a lot of systems are constantly looking at what is active on the network and those pings are keeping the machine awake.
its not the system that handles wol, it doesn’t need to ping anything. even the net adapter doesn’t need to do that
I’m not sure what you are trying to say.
I wanted to say this is not how it works:
or if you meant that, computers are normally not pingable when they are asleep. net adapters only wake the computer when seeing a magic packet with their mac address in it, and it is the operating system that receives the ping request and decides to send back a ping response.
an exception is when it is set up to wake on some network traffic pattern, but few net adapters support that mode of operation
https://wiki.archlinux.org/title/Wake-on-LAN#Enable_WoL_on_the_network_adapter