Search results

I have on the netatalk roadmap to create a PQC UAM. Once that's in place, Apple then just has update their macOS client and bam, fully secure AFP. ;)

Has Apple announced the removal date for the AFP client yet? I saw MacRumors and other news sites making assumptions, based on some warning messages you get recently when attempting to use AirPort and Time Capsule devices. But beyond the deprecation notice in the Sequoia 15.5 release notes, I...

FWIW I have been tinkering with my own fork of afpfs-ng on and off for a few years. I have fixed a lot of bugs and improved the code quality while adding support for MacFUSE. But there's some fundamental flaw with the FUSE code that makes it extremely unstable on contemporary systems (Linux and...

I don't think you need to care about all that. The "system/io.netatalk.daemon" service just needs to be enabled, after which the netatalk daemons will start up automatically on system boot. The meson build system should set it up for you by default. But if you for instance run "launchctl print...

As a side note, I filed the macOS crash bug as https://github.com/Netatalk/netatalk/issues/2452 so that we can try to figure out what's causing it. The callstack suggests that that the crash is in the afp_flush() function.

Can you please describe the official new way that you tried? To my best knowledge launchd didn't significantly change in macOS Tahoe but I could be missing some detail. If it doesn't get built by default for some reason, you can force the netatalk build system to install the launchd files with...

@Slimes Did you recall what your afp.conf looked like before? You only added "log file" and nothing else? If you comment out "log file" and try again, does the crash make a return? When it was crashing, how frequently did you see the crash? Was is intermittent, or fully deterministic and...

@Slimes It's working well on macOS Tahoe for me! It's my main netatalk dev/test host OS right now. I would be curious to see the afp.conf that triggered the issue. It should definitely be possible to run netatalk on macOS without setting "log file", although we cannot currently log to the macOS...

@EricFromCanada I really appreciate you for all your contributions to the netatalk Homebrew formula! It's really come a long way after only a few months. It was a great idea to make SQLite the default CNID backend for new installations. It will get us adoption without putting established...

Netatalk 4.3.0 was released today. It includes the new sqlite CNID backend. It is still flagged as experimental, and should only be used for testing at this point. Still, now is a great time to try it out! I'm looking forward to your feedback.

Major netatalk news: we now support SQLite as the CNID database backend for the AFP file server, in the main development branch. Why is this big news you ask? Thank you for the great question! For the last two decades (since at least v1.5 in 2002) netatalk has been using Berkeley DB as the...

Easter update: over the last few days, I have containerized both the mysql CNID backend as well as the netatalk webmin module. As a quick recap, netatalk uses a berkeleydb CNID backend by default presently. However the mysql backend allows for better control and scalability, while also being a...

If options aren't taking effect, a common cause is that netatalk is reading afp.conf from a different location. Run "netatalk -V" and compare the path to afp.conf with what you're editing.

For number 1, enabling "legacy volume size" in afp.conf should make file size calculations work on older clients. Number 2 is a bug I haven't encountered myself, so some more context would be needed to reproduce & debug. Can I ask you to file a bug ticket in GitHub?

@bribri What version of netatalk are you running? Would you be able to share the rest of your afp.conf? You are using the correct option for forcing appledouble dot files so there must be an error elsewhere.

@scj312 a 4.2.0 container image has been pushed to Docker Hub. Please check it out and let me know if it works out for you!

@scj312 Yeah, I've been too busy with my day job to properly test 4.2.0 running in the Docker container. I don't want to inadvertently destroy anyone's deployment. 😬 In 4.2.0, I completely rewrote the entry point script in POSIX compliant shell script to remove the bash dependency (for size and...

quick poll: of you netatalk users here, is anyone relying on the "include = /path/to/extra_afp.conf" directive in afp.conf? For context, this is a directive that allows you to dynamically load and nest a secondary afp.conf file. However this relied on local hacks to the iniparser library. I am...

@scj312 Agreed that this is highly puzzling. Have you tried to do what the logs earlier suggested: define an explicit "afp listen" or "afp interfaces" in afp.conf (override with MANUAL_CONFIG plus a bind mount with a custom afp.conf) Beyond that, what I'd suggest is to enable debug logging for...

Could you try ejecting the connected AFP mount from the modern Mac, and then try connecting again to netatalk in the container through the Connect to Server dialog: Press Cmd+K in Finder and connect to "afp://ip-address-of-docker-host" It would also be interesting if you could run "nbplkup"...