Daniel Markstedt

For the record, we got some excellent code review feedback from a Debian developer in this now-orphaned commit: https://github.com/Netatalk/netatalk/commit/b860bd8479623c4c5c574cbb46d6094c3a4b77da

@Hyperblue Thank you for the detailed bug report! Do you have an idea how to solve this cleanly in netatalk code? We very much welcome PRs.

Some analysis in https://sourceforge.net/p/netatalk/bugs/595/

@minfrin What OS were you running Netatalk at the time this issue was observed? Have you tried the dual-stack configuration again with recent releases?

Closing for now. I haven't seen it myself, and it isn't widely reported by other users. Please reopen and provide additional context if you're still experience the issue!

What is the content of your afp.service file? In 3.1 the `netatalk` wrapper daemon is in charge of advertising zeroconf, while in 2.2 the `afpd` daemon handles that. That's the...

Good job narrowing down the triggering factor! Another user has reported trouble with ipv6 (dual stack) so there may be some underlying defect in netatalk code. https://github.com/Netatalk/netatalk/issues/181

@pbobbenb We have done some general improvements and bugfixes since your report. Any chance you can try again with the latest Netatalk v4 release?

@pbobbenb Ubuntu 20.04 ships with a much earlier version of the Tracker stack, which should work fine with netatalk. Use apt to search for *tracker* or *sparql*. After installation, you...

Thanks for testing! FWIW, netatalk's Avahi based zeroconf can get... stuck sometimes. Not sure what causes it, but a reboot of the client often solves the problem.