Mac OS 9 Network Wakeup and Wake-on-LAN Explained

During the classic Mac OS era, Apple integrated power management with local networking to allow unattended machines to conserve power without losing network availability. In Mac OS 9, remote wakeup enabled a suspended or sleeping Macintosh to resume full operation upon detecting specific network traffic directed to its Ethernet interface. This feature relied on a tightly integrated combination of hardware standby power, specialized network interface controller (NIC) firmware, the Mac OS 9 Energy Saver control panel, and the Power Management Unit (PMU).

The Hardware Foundation and Standby Power

For a sleeping Mac to detect incoming network traffic, its network hardware could not be entirely powered down. Mac models from the late 1990s and early 2000s—such as the blue-and-white Power Mac G3, Power Mac G4, and late-model iMacs—featured Ethernet controllers designed to draw power from an auxiliary standby rail (typically +3.3V auxiliary power via the PCI bus or motherboard logic).

While the main power supply cut current to the PowerPC processor, hard drives, cooling fans, and video circuitry, the Ethernet physical layer (PHY) and media access control (MAC) core remained energized in a low-power monitoring state.

Configuration via the Energy Saver Control Panel

The software configuration for remote wakeup in Mac OS 9 was managed through the Energy Saver control panel. Under the "Advanced Settings" or "Options" panel, users could toggle settings such as "Wake when the modem detects a ring" and "Wake for network administrative access" (or "Wake on directed network activity," depending on the specific OS revision and hardware generation).

When this option was enabled, Mac OS 9 programmed the Ethernet controller prior to entering sleep mode. The OS configured the network hardware's packet filter registers, defining the exact criteria under which the card was permitted to signal the rest of the machine to turn back on.

Network Trigger Mechanisms

Mac OS 9 systems supported two primary methods of waking via network activity:

  1. Magic Packets (Standard Wake-on-LAN): The most common trigger was the standard AMD Wake-on-LAN frame. A remote machine on the local subnet would broadcast a Magic Packet containing a synchronization stream (six bytes of FF FF FF FF FF FF) followed immediately by 16 repetitions of the target Mac's 48-bit MAC address. Because this frame was evaluated entirely within the controller's onboard logic, it bypassed the sleeping operating system.
  2. Directed Unicast and Administrative Traffic: On certain Apple hardware implementations, the Ethernet controller could be configured to wake on directed unicast frames matching the Mac's IP or AppleTalk address. This allowed services like AppleShare File Sharing (via AFP) or network backups (using tools such as Dantz Retrospect) to contact the machine directly. When an incoming connection request matched the internal filter, the interface initiated the wake routine.

The Wake Sequence and OS Resumption

Once the Ethernet controller identified a valid wake frame, it initiated the hardware power-up sequence:

  1. Asserting the Wake Signal: The NIC asserted the PCI Power Management Event line (PME#) or sent a dedicated hardware interrupt to the Mac's Power Management Unit (PMU).
  2. Power Supply Engagement: The PMU signaled the main power supply to switch on the primary system rails (+12V, +5V, and standard +3.3V).
  3. Hardware Initialization: System clocks stabilized, the PowerPC processor exited its sleep state, and memory contexts were restored from RAM without requiring a cold reboot.
  4. Driver and Protocol Re-engagement: Mac OS 9 restored device drivers, re-initialized the Open Transport networking stack, and handed the pending network connection to the appropriate system daemon or application.

Through this coordinated handoff between the standby-powered NIC, the PMU, and the Open Transport architecture, Mac OS 9 maintained server-like availability while operating within standard desktop energy limits.