Netatalk seems to always have some issue with OS X. Why I still use little NAS boxes for this that and the other is beyond me. I got stuck dealing with this for a little while and if you’re using Netatalk w/ a DHCAST128 UAM you probably will too. For more on DHCAST see the Netatalk page on UAM support. Kerberos and DHX2 are arguably better, but I’ve found they don’t always work right on some of my NAS boxes. This wasn’t just a quick defaults command as it was in previous instances. It’s not much of a script but the following should fix it if you’re having this issue…
-
-
Enable Jumbo Frames in Ubuntu Server 10
Jumbo frames can completely suck. But they can also boost network throughput performance. The MTU in networking terminologies is the Maximum Transmission Unit in bytes that protocol data can send over the wire. MTU is configured per interface and needs (er, prefers) the network infrastructure to match about the same MTU sizes. By default, eth0 (en0 in Mac OS X) is set to 1500. But increasing that to 9000 means that you’re sending less error correction and addressing data and more payload (but as usual the payload can get messy if all parties aren’t knowledgeable that they’re taking it). Before you get started, install ethtool: apt-get install ethtool Then run…
-
afp on Linux via Bonjour
Based on a few messages I got after the article on building netatalk to host afp on Linux, it looks like building netatalk to host your shares just isn’t enough. I guess people still like Bonjour or something… In that case, let’s make this netatalk thingie announce itself to the world (er, your local network)! Avahi is much simpler than netatalk, given that there’s none of this dhx nonsense preventing us from using aptitude (again, this whole thing is for Debian/Ubuntu and you’re gonna’ need to escalate those privileges): aptitude install avahi-daemon Then we’re gonna’ need to teach it about the whole afpd service we built, which is done in…
-
Hosting afp on Linux
One of the main reasons people get a server is to share files. Mac OS X Server is one of the more common devices used to share files to Mac OS X clients, using afp, the default file sharing protocol for Mac OS X. But you don’t have to use Mac OS X Server. You can use Linux as well. We’re going to look at using an open source project called netatalk to do so. If you find that after reading this that you’d like to find out more about netatalk then check out the open source project page at http://netatalk.sourceforge.net. The netatalk installer can be installed through most of…
-
bdb and netatalk
I’ve been finding recently that practically every netatalk implementation is using bdb instead of cdb (the default), due to the fact that cdb seems to be more susceptable to corruption. To make this change, you open the netatalk configuration file at /etc/default/netatalk. Here you will see the following options: ATALKD_RUN=no PAPD_RUN=no CNID_METAD_RUN=no AFPD_RUN=yes TIMELORD_RUN=no A2BOOT_RUN=no To switch from cdb to the dbd scheme change CNID_METAD_RUN = no to CNID_METAD_RUN = yes. Save the netatalk file and then restart using the ‘netatalk restart’ command (with sudo or as root): /etc/init.d/netatalk restart No further changes need to be made in AppleVolumes.default or afpd.conf, but do be sure to check that the users…
-
Ubuntu: Installing Netatalk
Netatalk is an Open Source implementation of AFP. To get Netatalk you have to perform a custom build from the source code. To start: open system -> Administration -> Software Sources. Check the Source Code Box then click on close and click reload. Then open a terminal and type the following commands: sudo apt-get build-dep netatalk sudo apt-get install cracklib2-dev fakeroot libssl-dev sudo apt-get source netatalk cd netatalk-2* Next build the Netatalk package using: sudo DEB_BUILD_OPTIONS=ssl dpkg-buildpackage -rfakeroot sudo dpkg -i ~/netatalk_2*.deb echo “netatalk hold” | sudo dpkg –set-selections That’s it.