Search results

I recommend you find resources that explain the general upsides of 64 bit addressing and instructions better than I can (or ask ChatGPT.) But the primary reason in my mind that you should run 64 bit software, is that most people develop and test on 64 bit machines exclusively, and generally...

It’s more important to run a 64 bit operating system on your RPi than to have docker for netatalk. IMHO. Building from source is not hard.

Good to see a refresh of maciprpi! I'm curious what base OS you're using now? It's also encouraging to see that you're on a supported and secure release version of netatalk now. May I ask what it would take for you to migrate to the netatalk 4.x release series? Is there some technical reason...

IINM the RPi 3 series has a 64 bit CPU. You should be using the 64 bit version of the OS. ...but for some bizarre reason, Docker Engine only supports 32 bit RPi OS. So it might not be the best choice for your setup after all. Due some time later this year, the next major RPi OS release is...

Yeah I was going to say: you already have a powerful file sharing protocol at your fingertips there thanks to Netatalk. ;)

If you start a new GitHub Discussions thread, we can try a little troubleshooting again, if you like. I bet the "DDP/IP situation" referred to the now-removed IPDDP Linux kernel module. It conflicted with macipgw operation.

Please remind me: Were you able to get around to trying a more recent FTP client (late 90s-ish) that can do passive mode? I don't think it's feasible to use active FTP over a NAT'ed bridge, but passive FTP should theoretically work fine.

@Mk.558 It's worth calling out that two features that you requested are in the 4.1.0 release version. Namely, a macipgw.conf configuration file. And, the new tabbed interface in the Webmin module. Check the updated macipgw manual page for an example of the configuration file. This allows you...

These improvements to macOS interoperability are included in netatalk 4.1.0 which I tagged and released moments ago. Check out the release notes and grab the tarballs at: https://github.com/Netatalk/netatalk/releases/tag/netatalk-4-1-0 This version will trickle downstream to Homebrew and...

In the next revision of the Homebrew formula, I'm looking to replace mysql with mariadb, which is significantly lighter (as in, less disk space and much quicker to install.)

@mactjaap This is on your Monterey Mac? Did you do anything special to make it work? @NJRoadfan I was on the fence about whether to have mysql as a dependency or not. The formula is noticeably heavy to install even on a 2019 MacBook Air. I might look into making it an optional dependency in a...

If the compilation hasn't completed after 24h on your Monterey Mac, I would suspect that the system is running out of memory and clang gets starved and stalls. I've seen that happen on f.e. Raspberry Pis when you try to compile software with too many concurrent threads. You could try shutting...

@mactjaap Do you get any errors when you run "brew doctor"? Like the error message says, there's a permissions issue on that Cellar subdir. You can try running "sudo chmod -R 775 /usr/local/Cellar/libunistring"

Good news: netatalk 4 is now available as a Homebrew formula for macOS (and Linux, for you weirdos who use brew on Linux) If you have brew installed already, just do: brew update brew install netatalk sudo brew services start netatalk If you're using an Intel Mac, this should work out of the...

@Tashtari Thanks for sharing about your project! I hope that you recover your motivation one day. :)

There is no AppleTalk userland stack available today, to my best knowledge. If you search these forums you will find that it has been attempted, however. I think it's absolutely feasible. BTW, I agree that getting rid of the AppleTalk transport layer amounted to throwing out the baby with the...

This was an epic thread to follow. Great job both of you! I'm excited about NetBSD compatibility for TashRouter. It's worthwhile breaking out of the Linux monoculture every once in a while. :)

Great sleuthing work! Hopefully the commented out code was because no one had bothered to test it on aarch64… May I ask you to add a section to the NetBSD wiki page with a summary of your findings? https://github.com/Netatalk/netatalk/wiki/Installing-Netatalk-on-NetBSD It would be a handy...

It’s definitely concerning that Red Hat, FreeBSD and OpenBSD all made the explicit decision to remove old network stacks. From their perspective I understand the rationale (removing potential attack vectors) but it’s sad nonetheless. @robin-fo you're our only hope! 💪

@thecloud Looking at your terminal logs, I get the impression that this is an arm64 system. My immediate guess would be that the appletalk kernel module hasn't gotten ported to this architecture. I spun up my amd64 VM with NetBSD 10.0 here and could confirm that atalkd boots up happily (4.0.8...