I have an M1 Mac Mini running Sonoma 14.3. I would like to be able to put it to sleep or shut it down when not in use to conserve energy. But, I also want to be able to remotely power it up so I can access it when I need to using VNC, SMB, or SSH. I have typically done this by sending WOL (WakeOnLan) magic packets from my home router which is pfSense. This has always worked fine—until this Mini. I've checked the Energy Saver prefs, made sure womp=1 in pmset -g and even tried mucking around with nvram / darkwake settings. I'm sure the Ethernet MAC address is correct. Nothing has worked. WOL to an Intel NUC sitting on the same network works as expected. What happens when I send the WOL packet is one of: - absolutely nothing: no lights, no activity, screen remains dark. - power LED comes on, Mac becomes "pingable", screen stays dark, but after 5-10 seconds, the Mac goes back to sleep. At no point during this sequence am I able to connect via VNC. Is this a hardware bug with the M1's? Anyone know of a solution?

I have a web app on port 3333 on my mac os (ventura). This mac has a static internal network IP (192.168.1.234). I want to access this web app from another machine on the. LAN via 192.168.1.234:3333. When I hit that url from another machine, the address never resolves and gets stuck loading. Strangely, I also have ssh access to that mac hosting the web app. The instant I ssh into that mac from the same machine that is trying to load 192.168.1.234:3333, this address resolves and a get access to the web app. ## update I don't even need to ssh **from that same machine** that is trying to access the web app. I can access the mac from another machine on the same LAN. It seems like this is "waking up" the mac to resolve the web app So for some reason ssh into the machine also opens up the web app address in the brower 1. **why is that ?** 2. how can I access the web app without having to first ssh? The mac does not have a firewall enabled in place. So I am not sure what is blocking the access.

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?

I am trying to use the "Wake on LAN" feature to remotely turn on the display of my MacBook Pro running Catalina. **I have confirmed that "WoL" feature is working properly and the MBP awakes** into some state, however the display never turns on. Neither the laptop display nor the HDMI connected display light up. I have tried several things already: - Changing macOS config to darkwake=0, i.e. https://www.insanelymac.com/forum/topic/342002-darkwake-on-macos-catalina-boot-args-darkwake8-darkwake10-are-obsolete/ . The change of this setting didn't do anything - Using sleepwatcher https://formulae.brew.sh/formula/sleepwatcher . The sleepwatcher script only runs when I physically push a button on the computer. Any ideas what else I can try to make this work? **UPDATE**: Seems like the only way to wake the display up is using SSH commands sent to the Mac, see detailed answer below.

My 2019 MBPR has an USB-C ethernet adaptor. I've been running it with the display closed and having a difficult time getting Wake-On-Lan to work. I'm hoping that macOS Ventura is smart enough to keep power to USB-C accessories (i.e. an ethernet adaptor) when asleep so that Wake-on-lan works. Is there a way to determine if an accessory supports WOL and/or how I can verify the OS is set up properly to enable this feature?

I've enabled "Wake for network access" in my energy preferences. Then, I try to confirm that the UDP port is open:

$ sudo nmap -sU -p 9 127.0.0.1
Starting Nmap 7.91 ( https://nmap.org  ) at 2021-06-10 01:36 CDT
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000079s latency).

PORT  STATE  SERVICE
9/udp closed discard

Is there something else I need to do to open up the WOL port?

I've created a bash script to start a network computer if it is sleeping, then start a streaming client. However, as the script executes the final command to run the streaming client, each cli option with a hyphen becomes wrapped in

$'\342\200\224'

. E.g.

-resolution

becomes

$'\342\200\224resolution'

. Specifically, this command in the script: /Applications/Moonlight.app/Contents/MacOS/Moonlight stream "$_target_computer_ip" "$_moonlight_app_name" —resolution "$_moonlight_resolution" —fps "$_moonlight_fps" &>/dev/null & executes in the shell as: /Applications/Moonlight.app/Contents/MacOS/Moonlight stream 192.168.1.30 mstsc.exe $'\342\200\224resolution' 1920x1024 $'\342\200\224fps' 30 I've tried escaping the hyphen as \-, but that just changes the output to

$'?\200\224

. What am I doing wrong? Here's the full script:

#!/bin/bash
set -x

_target_computer_ip='192.168.1.30'
_target_computer_subnet='192.168.1.255'
_target_computer_mac='2C:F0:5D:27:7C:95'

_moonlight_app_name='mstsc.exe'
_moonlight_resolution='1920x1080'
_moonlight_fps='30'

if ping -c 1 -W 1 "$_target_computer_ip"; then
  echo "is alive"
else
  echo "nope"
  wakeonlan -i $_target_computer_subnet $_target_computer_mac
fi

/Applications/Moonlight.app/Contents/MacOS/Moonlight stream "$_target_computer_ip" "$_moonlight_app_name" —resolution "$_moonlight_resolution" —fps "$_moonlight_fps" &>/dev/null &

And the full command output:

Fayes-MBP:Shell Scripts rain$ ./check_and_wake_pc.sh 
+ _target_computer_ip=192.168.1.30
+ _target_computer_subnet=192.168.1.255
+ _target_computer_mac=2C:F0:5D:27:7C:95
+ _moonlight_app_name=mstsc.exe
+ _moonlight_resolution=1920x1080
+ _moonlight_fps=30
+ echo 192.168.1.30
192.168.1.30
+ ping -c 1 -W 1 192.168.1.30
PING 192.168.1.30 (192.168.1.30): 56 data bytes

--- 192.168.1.30 ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss, 1 packets out of wait time
round-trip min/avg/max/stddev = 3.701/3.701/3.701/0.000 ms
+ echo 'is alive'
is alive
+ /Applications/Moonlight.app/Contents/MacOS/Moonlight stream 192.168.1.30 mstsc.exe $'?\200\224resolution' 1920x1080 $'?\200\224fps' 30

Experimenting with Wake On Lan, I tested with a small Fujitsu Esprimo mini computer and a Mac Mini. In a Windows desktop app "WakeMeOnLan" on another unrelated computer, I can see "green" dots for awake clients, and "red" dots for sleeping clients. I can put the Esprimo to sleep, so the dots turn red, but not the Mac Mini. How can I test if my Wake On Lan works? Esprimo with Ubuntu - makes a "click" noise when switched on, so I know it worked. - The colored app indicators change between green and red, as expected. - SSH connection drops on sleep via pm-suspend. Mac Mini with latest OS - LED stays on always - Monitor turns off when starting sleep via SSH and pmset sleepnow. - Even after sleepnow, the colored app indicators are always green (unless the Mac is really switched off, so I can't wake on lan anyway) - SSH connection stays alive - After some time of inactivity the MAC's LED pulsates slowly, which at least gives an indications of a changed state. Still, the colored indicator in my wake-app is still green not red. With the mac I have tested hibernate modes 0,3,25. Energy saving settings are those: - [ ] Prevent computer from sleeping automatically when the display is off - [X] Put hard disks to sleep when possible - [X] Wake for Network Access - [X] Start up automatically after a power failure - [ ] Enable Power Nap Output of pmset -g How can I be sure that the Mac is sleeping actually? (LED, SSH connection,...) I need a way to proof that my Wake On Lan actually works for the Mac. It might just be a typical Mac issue, but I have no clue about Apple stuff.

System: - iMac (21.5-inch, Late 2009) - El Capitan 10.11.6 - Non-Apple modem/router Wake on LAN isn’t working. I have tried a variety of methods: iOS apps (Fing, iNet, Mocha); Mac applications and scripting on another Mac (WakeOnMac, wakeonlan perl script). Yes, I’m on a local network, and yes I’ve ticked the ‘Wake for network access’ in System Preferences. Also checked with pmset -g that womp = 1. I have also tried overriding networkoversleep (1). I initially believed the Ethernet (which directly connects the iMac to the router and should make this process more reliable) disconnected during sleep. I tested this by opening System Preferences > Network and leaving that open while I sleep it. When I woke it from sleep, the Network Preferences panel was still open (obviously) and Ethernet (at the top) showed as Disconnected and features a red dot beside it. It reconnects very quickly, but that’s no good for WOL. I have now tested installs of Mavericks, Yosemite and macOS Sierra on a separate partition. Mavericks and Yosemite both allowed WOL (despite the Ethernet 'disconnecting' issue still being there, suggesting it doesn't actually disconnect). macOS Sierra, as El Capitan, does not allow WOL. The pmset settings and 'Wake for network access' etc. are all the same. Does anybody know of an obscure network setting somewhere that disables WOL despite it being enabled in pmset?

is it possible to use wake on lan via wifi on the macbook air 2018? What iOS app (or terminal command?) can you recommend to use? I want to wake of the MacBook Air with my iPhone which is in the same network.

I'm trying send a WOL packet from a bash script under Mojave, much like https://stackoverflow.com/a/31588036/9370650 , without any third-party utilities, such as the nifty https://github.com/jpoliv/wakeonlan . I don't, however, seem to be able to successfully broadcast anything at all to 255.255.255.255 on port 9 using netcat. If I listen to UDP port 9 like this: $ nc -uv -l 9 -w0 netcat then reports the WOL packet when I run the perl-based wakeonlan script I mentioned above. But, if I try to do my own UDP broadcast to 255.255.255.255:9, like this: $ echo "hello" | nc -vu 255.255.255.255 9 it isn't seen by my listening instance of netcat. For the record, the output from my attempt to broadcast looks like this:

found 0 associations
found 1 connections:
     1:	flags=82
	outif (null)
	src 192.168.1.7 port 51674
	dst 255.255.255.255 port 9
	rank info not available

I'm not a networking expert, so I'm likely misunderstanding something here. Any thoughts on what I'm doing wrong?

How can I wake up my MacBook pro with an iPhone, when the lid closed (no external display)? MacBook is not connected to power and there's a local wifi that it can connect to.

I'm trying to make use of an old Mac Pro with 10.6.8 I had lying around as a wireless home media server, backed up with Time Machine. I'm just using a standard Huawei router provided to me by my ISP. I've set up file sharing and screen sharing, so that I can access the files on the Mac Pro with my Macbook Pro. But is there a way that I can save power by having my Mac Pro constantly asleep, but wake up automatically when I want to access it from the Macbook Pro? Then go back to sleep once I'm done? I've ticked the Wake For Access Network on my Mac Pro and Macbook Pro. But that doesn't work. I did some research and saw that you need an Airport or Apple TV with Bonjour Sleep Proxy to get it to work. Is there any way to get it to work with what just the Mac Pro and Macbook Pro?

I can Home Share between a Mac Mini, Mac Pro, and my AppleTV with no problems as long as the two computers are awake. The ATV finds and streams the libraries with no problems. The Mac Mini and ATV are connected to a switch, while the Mac Pro is connected directly to the router. Everything is on the same subnet and has the same IP range, and everything is wired (not using Wi-Fi). If the Mac Pro is asleep, the ATV seems to be able to wake it on demand and stream it's library (after I added specific port forwarding rules to my router as suggested by Apple - details below). Again, the Mac Pro is connected directly to the router. The main problem is with the Mac Mini, which, along with the ATV, is connected via a switch. If that computer is asleep, it will not wake up and the ATV can not stream it's library. One weird thing I've noticed is that if both computers are awake, the ATV shows both libraries as available to stream. If I sleep everything (including the ATV) then wake it up, both computers appear as available to stream, but when I click in to the Mini's library it fails to load. Also, the last time I checked, Wake on Demand was working over Wi-Fi, but I'd prefer to keep as many devices hard wired. About My Setup: - Router: - IP Address in the range of 192.150.23.xxx - Subnet on 255.255.255.128 (This was done in order to port forward to the broadcast IP address. On a standard subnet of 255.255.255.0, my router wouldn’t let me forward to 255.255.255.255. I read that I could change the subnet to 255.255.255.128 and broadcast to 255.255.255.127. - Port forwarding: everywhere I read on the web recommended forwarding port 7 over UDP to my broadcast IP address of 192.150.23.127. After speaking with Apple, they also recommending doing the same with ports 1900, 5350, 5351, and 5353. - I verified this subnet change and port forwarding is working as expected because I downloaded an iPhone app called mWOL and it can send a magic packet and wake any computer I point it to. - Mac Mini: - Wired connection to switch - Energy Saver > Wake for network access checked - iTunes open - Mac Pro: - Wired connection to router - Energy Saver > Wake for network access checked - iTunes open - AppleTV: - Wired connection to switch Any ideas what could be happening? Could the magic packet be getting swallowed when sent to the Mini? Perhaps related to the fact that I’m using a switch?

We have carts of MacBooks and MacBook Pros that students use and close the lid and put them back in cart when they are done. They use wireless networking and don't have USB or displays connected. I am wondering if there is any way we can wake the MacBook remotely using wireless (WoWLAN?). We don't want to have the setting where MacBook doesn't sleep when lid is closed. Is there any way we can wake them on and have them connect to our wireless when their lid is closed? The remote management software we use couldn't work when they are in the cart overnight.

I wanted to setup TeamViewer on my MacBook Air (2015, macOS Sierra 10.12.1) to wake up on LAN. Does MacBook allow wake up on LAN (WOL)?

My ethernet wired 2012 iMac with 10.11.6 is able to wake from sleep for SSH and AFP access. "Wake for network access" is checked in System Preferences : Energy Saver. There is no Bonjour Proxy or network router, it has a public IP address. The question is, how can I configure it to wake for access on an arbitrary port? I would guess that there is a list of shared services to monitor somewhere at the unix/darwin level, but I have not yet found it.

I use Infuse on my iPad to play videos stored on my Mac. However, after a few tens of minutes, the connection drops, and it doesn't reconnect. Restarting Infuse doesn't help. When I walk over to the computer, the hard disc light (it's an external disk) is off. When I move the mouse, the hard disc light comes on, and Infuse starts working again. I tried unticking "Put hard discs to sleep when possible" and it made no difference. I tried resetting NVRAM and SMC and that didn't work either. I now ticked "Prevent computer from sleeping automatically when the display is off". Inufse now works reliably, but I don't like that the Mac is wasting energy, and possibly shortening the life of its components. Configuration: - iMac 5K (Late 2015), running 10.12.4, connected via Wifi - Infuse Pro 5.4 on iPad 13-inch running iOS 10.3.1 - The connection is via SSH. **How do I let my Mac go to sleep but wake up when Infuse connects via SSH?**

Does anyone know if a mac can be woken up from the sleep state by a Linux machine over WiFi? The router is non-Apple.

is there a way to wake the Mac out of a complete power off? I normally don't use the sleep mode,but I also want to wake the Mac sometimes for various reasons (it's a part of my entertainment system). Any way I can do this?