How Mac OS 9 Handled PPPoE Broadband Connections

During the transition from dial-up to high-speed internet in the late 1990s and early 2000s, Mac OS 9 managed broadband connections through a combination of classic networking control panels and external software. While cable internet generally worked out of the box using straightforward Ethernet protocols, DSL connections frequently required Point-to-Point Protocol over Ethernet (PPPoE). Early versions of Mac OS 9 lacked native PPPoE support and relied on third-party drivers, but Apple eventually integrated PPPoE functionality into its core Remote Access system with later OS updates, bridging the gap between legacy networking and the modern broadband era.

The Divide Between Cable and DSL

Cable internet services and DSL services were handled differently under Mac OS 9:

  • Cable Internet: Most cable providers assigned IP addresses automatically via standard dynamic networking. To connect, a user only had to plug an Ethernet cable from the cable modem into the Mac and configure the native TCP/IP control panel. Setting "Connect via" to "Ethernet built-in" and "Configure" to "Using DHCP Server" was typically all that was required.
  • DSL Services: Most telephone companies implemented PPPoE to mimic traditional dial-up architecture. This required user authentication (a username and password) before granting network access, which the standard Open Transport networking stack in early Mac OS 9 could not handle natively over Ethernet.

The Early Approach: Third-Party PPPoE Clients

When Mac OS 9.0 launched in late 1999, it had no built-in mechanism to negotiate PPPoE over an Ethernet interface. As a result, DSL subscribers had to install third-party client software supplied by their Internet Service Providers (ISPs).

The most common utilities were:

  • EnterNet 300 / EnterNet 305
  • MacPoET
  • FreePPPoE

These applications installed system extensions that hooked into Apple’s Open Transport networking architecture. To connect, users launched the third-party client application, entered their ISP credentials, and clicked a "Connect" button similar to a traditional dial-up utility. Once the software negotiated the tunnel, the Mac received an IP address and could access the internet.

Native PPPoE Integration in Mac OS 9.1 and 9.2

Apple addressed the need for built-in PPPoE support starting with the Mac OS 9.1 update by integrating the protocol directly into the Remote Access subsystem.

To configure a native PPPoE connection in Mac OS 9.1 or later:

  1. Remote Access Control Panel: Users opened the Remote Access control panel, clicked "Options," navigated to the "Protocol" tab, and changed the connection type from the default modem setting to PPPoE over Ethernet.
  2. Credential Setup: The user entered their ISP-provided username and password directly into the primary fields of the Remote Access window.
  3. TCP/IP Control Panel: The TCP/IP control panel was set to "Connect via: Remote Access (PPPoE)" or left on Ethernet with configuration set to PPP/Remote Access, depending on the specific update.
  4. Initiating the Link: Users could connect by clicking "Connect" in the Remote Access control panel or by using the Remote Access module in the Mac OS Control Strip on the desktop.

The Hardware Router Alternative

Because software-based PPPoE on Mac OS 9 could cause system instability, extension conflicts, or connection dropouts, many users bypassed the operating system’s PPPoE handling entirely by using external hardware broadband routers (such as those from Linksys, Netgear, or Apple's original AirPort Base Station).

By offloading the PPPoE authentication and credential storage to a dedicated router, Mac OS 9 was only required to connect via plain Ethernet using DHCP. This eliminated the need for software PPPoE negotiation, reduced system resource usage, and provided a seamless broadband experience identical to that of cable internet.