For years I’ve used an Apple Airport Excessive router which not too long ago started randomly dropping connections and exhibiting different odd points. This coupled with gradual wi-fi speeds (by fashionable requirements) led me to purchase a brand new router, a TP-LINK AC1750 (Archer A7).
To date it is superior, however I’ve seen a pair behaviours have modified.
Most importantly, “Wake for Ethernet community entry” now not works on my desktop. It is a Macpro operating OSX 10.14.6. Beforehand, it might fall asleep, but when I made an try to attach by way of SSH it might get up. I might additionally entry it by way of finder as a community share and even when asleep it might present up on beneath “Areas” within the finder. Clicking on it might wake the pc. Now, as soon as it is asleep, I must go bodily do one thing to the pc.
After studying up a bit on the topic, I’ve now configured DHCP in addition to ARP binding in order that the machine in query has a set LAN IP and I’m now ready to make use of commandline util wakeonlan to get up this machine.
Is there a solution to get the outdated behaviour again? How was the Airport Excessive doing this? I did not want wakeonlan beforehand – I solely needed to ssh to the machine and it might get up. Was the outdated router doing one thing particular right here?
