The way I approached the development process, was to work in relatively atomic PRs against the mainline branch-netatalk-2-2. After a few months of gathering patches and testing, I'm ready to share with you all Netatalk 2.x, the latest and greatest among Netatalk forks! Here are a few of the major ones that I encountered:Īll this fragmentation seemed like a huge missed opportunity to me. In addition, there is an outstanding bug that frequently causes it to fail to run on Linux with an error in setifaddr.Īs a matter of fact, in the 5 years since the release of Netatalk 2.2.6 an impressive number of forks and projects with their own downstream patchset to keep Netatalk running have emerged. Unfortunately, Netatalk 2.2.6 (which was the last one in the 2.x series) no longer compiles out of the box on modern systems. For us who want to use Netatalk with really quite old Macs (and Apple //e & //gs) Netatalk 2.2 is mandatory. For those who are unaware, Netatalk 3.x dropped support for the AppleTalk / DDP protocol in favor of TCP/IP.

While researching Netatalk integration with RaSCSI it struck me just how painful it was to get Netatalk 2.2 working well on a modern Linux distro. Grab the latest stable release from GitHub. TL DR There is a new fork called Netatalk 2.x that integrates all the community patches since the 2.2.6 release, which works out of the box on modern distros.

Netatalk connection error raspberry pi