The MoofTCP control panel lets users switch between DHCP and fixed IP on a vintage Mac.
MOOFTCP REPLACES MACTCP ON 68K MACS WITH SLIM, RELIABLE STACK
*MoofTCP delivers a drop‑in MacTCP replacement for System 6 68k Macs. Built for 4 MB machines, it promises no hangs, low latency and comparable memory use. The project targets classic enthusiasts stuck with aging networking code.*
A new open‑source stack is breathing life into the networking of vintage 68k Macs. MoofTCP, hosted on GitHub, replaces Apple’s aging MacTCP with a fresh C‑written implementation that fits inside the tight 4 MB memory envelope of a Mac Classic. The project promises reliability—no hangs, no leaks—and low latency for interactive sessions, while keeping resident memory on par with the original stack. For hobbyists and preservationists, the drop‑in installer means existing MacTCP applications run unchanged, but with a modern code base that can be rebuilt from source using Docker. The release includes a Lite variant that trims DHCP code, shaving roughly 5 KB off the footprint, a crucial saving on machines that run on the edge of memory limits.
What is MoofTCP and how does it work?
MoofTCP is a modern, memory‑lean TCP/IP stack written in portable C. It implements the MacTCP .IPP driver interface, supporting TCP, UDP and ICMP echo, plus the dnrp name resolver. The stack lives in the core/ directory, contains no malloc calls or global state, and is tested on desktop with sanitizers and fuzzers. A single installer moves the original MacTCP files aside, installs MoofTCP, and adds a control panel with DHCP or fixed‑address options. An optional Lite build omits DHCP, saving roughly 5 KB of system memory. The installer can also remove MoofTCP and restore the original MacTCP environment without residue.
Can MoofTCP run on any System 6 Mac?
MoofTCP requires a 68k Mac running System 6.0.8, the version it was tested on. It also needs an Ethernet adapter that provides a .ENET0 driver, such as a BlueSCSI v2 Wi‑Fi with DaynaPORT. The project does not ship an Ethernet driver; users must supply a compatible one. Installation succeeds on a real Mac Classic with 4 MB RAM and on the Snow emulator when the appropriate driver image is supplied. After a full install on a single‑Finder setup, free system heap measures about 30.7 KB. MultiFinder environments grow the heap on demand, so memory usage varies.
How does MoofTCP compare to the original MacTCP?
Both stacks occupy similar resident memory, but MoofTCP promises reliability: no hangs, no leaks, and clean shutdown when apps quit. It targets low latency for interactive use, such as telnet typing, and higher throughput for quasi‑modern tasks. The Lite version trims DHCP code, saving about 5 KB. In tests, classic programs like Flynn (telnet), Wikipedia Reader, and NCSA Telnet run unchanged on MoofTCP. FTP, Gopher and other utilities also work in the Snow emulator. Memory footprints show driver code at 95,623 bytes for the full build and 90,722 bytes for Lite. The project logs 161 commits, indicating active maintenance.
What limitations does MoofTCP have?
MoofTCP lacks IPv6 support and has been tested only with the DaynaPORT Ethernet driver on System 6.0.8. Its DHCP implementation is basic: it does not release leases, perform INIT‑REBOOT, or probe for address conflicts. While DHCP runs, UDP port 68 is unavailable. Without a DHCP server, the first open waits about 10 seconds before failing. The stack does not include an Ethernet driver, so users must provide a compatible .ENET0 driver. Programs that rely on IPv6 or advanced DHCP features will not function.
Frequently asked questions
What hardware is required to run MoofTCP?
A 68k Mac with System 6.0.8, 4 MB of RAM, and an Ethernet adapter that provides a .ENET0 driver, such as a BlueSCSI v2 Wi‑Fi with DaynaPORT.
Does MoofTCP support IPv6?
No. MoofTCP currently has no IPv6 support and has only been tested with the DaynaPORT Ethernet driver on System 6.0.8.
How does the Lite version differ from the full MoofTCP build?
MoofTCP Lite omits DHCP code, saving about 5 KB of system memory, and its driver code is 90,722 bytes versus 95,623 bytes for the full build.
MoofTCP demonstrates that even the most constrained classic hardware can benefit from contemporary software practices. By delivering a lean, test‑driven TCP/IP stack that respects the memory limits of a 4 MB Mac Classic, the project offers a practical path for preserving networked workflows on legacy machines. As the codebase grows beyond 161 commits, the community can expect further refinements, but the current release already proves that vintage Macs can surf, telnet and fetch files without the baggage of obsolete networking code.
Sources: Hacker News article, GitHub repository https://github.com/matthewmrichter/mooftcp