Apple Time Capsule Custom Firmware

Three main open-source projects support the later AirPort/Time Capsule hardware.

Conclusion on Wi-Fi: If you need Wi-Fi from the Time Capsule itself, do not flash custom firmware. Keep it stock as an access point. apple time capsule custom firmware

So why flash custom firmware at all? Because you turn the Time Capsule into a wired router (WAN + 3 LAN) plus a NAS. You then attach a modern Wi-Fi 6 access point (like Ubiquiti or TP-Link Omada) to the LAN port. So why flash custom firmware at all

With the stock firmware, multiple Macs backing up simultaneously caused kernel panics. OpenWrt’s modern SMB daemon handles concurrent connections perfectly. You can create separate sparsebundle disk images for each Mac via a script. With the stock firmware, multiple Macs backing up

| Model | Flash | RAM | Custom FW Status | Limitation | | :--- | :--- | :--- | :--- | :--- | | A1470 (ac) | 128MB | 512MB | Stable | No PCIe bus for NVMe | | A1409 (n) | 32MB | 256MB | Experimental | 100Mbps WAN bottleneck | | A1302 (gig) | 16MB | 128MB | Legacy | 802.11b/g only |

For years, attempts to port Linux to the Time Capsule resulted in a router that worked via Ethernet but had no Wi-Fi. This changed with the work of developers like Rafał Miłecki and the community surrounding the DejaVu project.

The breakthrough came from a clever workaround. Developers realized that the Apple firmware updates are essentially archive files. By manipulating the firmware update process, it is possible to inject custom scripts and binaries into the system without replacing the kernel entirely.