Sample Header Ad - 728x90

"Wake for Ethernet network access" no longer works after changing router

0 votes
0 answers
81 views
For years I've used an Apple Airport Extreme router which recently began randomly dropping connections and exhibiting other odd issues. This coupled with slow wireless speeds (by modern standards) led me to buy a new router, a TP-LINK AC1750 (Archer A7). So far it's awesome, but I've noticed a couple behaviours have changed. Most significantly, "Wake for Ethernet network access" no longer works on my desktop. It's a Macpro running OSX 10.14.6. Previously, it would go to sleep, but if I made an attempt to connect via SSH it would wake up. I could also access it via finder as a network share and even when asleep it would show up on under "Locations" in the finder. Clicking on it would wake the computer. Now, once it's asleep, I need to go physically do something to the computer. After reading up a bit on the subject, I've now configured DHCP as well as ARP binding so that the machine in question has a fixed LAN IP and I am now able to use commandline util wakeonlan to wake up this machine. Is there a way to get the old behaviour back? How was the Airport Extreme doing this? I didn't need wakeonlan previously - I only had to ssh to the machine and it would wake up. Was the old router doing something special here?
Asked by You Old Fool (515 rep)
Sep 16, 2023, 03:58 PM