Sleeping Macs with wake for ethernet access enabled will register with an Airport so that an incoming ssh connection will be sensed by the router and send a Wake on Lan packet to wake up the Mac. Basically, ssh can wake a sleeping mac under some circumstances. Jan 13, 2017  The wake for network access only wakes when the 'magic packet' or Wake On LAN packet is sensed. I did not see where Apple ID, Airport or such send such a packet. About Wake on Demand No. It's not just a matter of keeping WiFi on. The app that you use to download will not run if your Mac is sleeping. Caffeine can temporarily override your Energy Saver settings and prevent your Mac from sleeping, if you leave the lid open.

Here's a seemingly contradictory piece of info from the Apple page for 'About Energy Saver sleep and idle modes in Mac OS X': 'Note: Portable computers have no network connectivity when in sleep mode, but can wake if the Energy Saver option 'Wake for network access' is enabled. If you wish to use file sharing or don't want to interrupt your Internet connection, you should not manually put the computer to sleep, and you should drag the 'Computer sleep' slider to Never.' So portables have no network connection when asleep, but can wake if 'wake for network access' is enabled. If that is actually possible then why does it also say you should not ever put it to sleep and should set sleep to 'never'? Firefox for mac os x 10.7.4.

At I had written about a strange DNS issue with OS X and Firefox. That's gone away, but for some time now I've had a new problem: when I wake from sleep, it takes a long time before I can do any network access. Firefox and Safari just hang with spinning beach balls, ssh times out. It looks like networking is dead. It isn't dead though: I often leave an ssh session to other machines connected when I sleep briefly. Those sessions remail connected without problem. I just can't start new sessions.

Maddeningly, the problem would sometimes disappear entirely, only to reappear a day or so later. I thought that an Apple update or Firefox upgrade had fixed it. But no, it came back again.

I thought it might be a DNS issue again, so I tried with hard IP addresses. Combine pdf files. No, those don't work either. I've found plenty of similar complaints on the Net, but for wireless activity.

This is happening to me with a hard Ethernet cable on en0 - I have Airport shut off most of the time. Airport did give me a clue. I noticed that when I happened to be using Airport, whether here or elsewhere, I wouldn't get the sleep problem. As I said, I usually have Airport shut off. I don't know why - I just don't like anything running if I'm not using it.

So I usually have it shut off. So what's happening here?

Is OS X trying to use Airport for new connections even though I have it shut off? That might explain why existing connections are still fine. Here's another clue: If I turn Airport on and then shut it off, the hanging after sleep goes away for a while. That probably explains the supposedly random nature of this - I had probably turned on Airport for some reason. Maybe OS X just gets confused and thinks Airport is on unless it has been turned off recently? I don't know.

The obvious fix is to just leave Airport on. I suppose that's what I'll do. Got something to add? Sun Nov 9 16:: 4750 badanov My guess would be if you disable ACPI most of your sleep problems will disappear. Autocad 2016 crack for mac. Portrait professional for mac free download. It has been my experience FreeBSD has an ongoing problem with ACPI Sun Nov 9 17:: 4751 TonyLawrence That's often been the suggestion for Wireless wake from sleep problems, yes.