Linux netatalk server install#
Linux netatalk server pro#
Linux netatalk server password#
Linux netatalk server download#
Linux netatalk server windows#

Once you’re in the new share you should look at the title bar of the Finder window and drag the little disk icon from the middle of the bar somewhere into your favorites bar in the left. Now you can use Apple + K or “Go -> Connect to Server” whenever you want to mount this share. Upon attempting to connect you will be prompted to enter a username/password just as with the “Connect As…” button you will use the info you setup earlier, in my case “storage” and my password. There I typed in “afp://192.168.1.99” as the server and then clicked the + button to save the share to favorites.

Linux netatalk server password#

In my case I connected with the username “storage” and the password I set for the storage user earlier.Īnother option is to use the “Go -> Connect to Server” menu option (Shortcut: Apple + K) which brings up a connection screen. When I clicked it in Finder I saw I could do “Connect As…”, I played with that first and it works just fine.

Linux netatalk server pro#

Now from my Mac Pro I was able to immediately see a share called “home” in Finder. sbin/iptables -A INPUT -i br0 -p udp -s 192.168.1.0/24 -dport 5353 -j ACCEPTĪfter I reloaded my firewall I launched the necessary services to start sharing files between my CentOS ZFS file server and my Mac Pro: chkconfig avahi-daemon on I also had to add some firewall entries: /sbin/iptables -A INPUT -i br0 -p tcp -s 192.168.1.0/24 -dport 548 -j ACCEPT On my system it went like this: useradd storage -d /storage

You should also “chmod” and “chown” the /storage structure appropriately for the “storage” user. This assumes that you have a user called “storage” and you want to have a share called “storage” which is mounted as /storage on your server system, as it is on my ZFS storage server. Now I edited the config file output earlier: nano -w /usr/local/etc/afp.conf Server messages path: /usr/local/var/netatalk/msg/ UAM search path: /usr/local/lib/netatalk// State directory: /usr/local/var/netatalk/Īfp_nf: /usr/local/var/netatalk/afp_nfĪfp_nf: /usr/local/var/netatalk/afp_nf

Linux netatalk server download#

Now we’re ready to download Netatalk and compile it.

Linux netatalk server install#

Yum install db4-devel libacl-devel avahi-devel libgcrypt-devel pam-devel psiconv-devel dbus-devel dbus-c++-devel globus-gssapi-gsi-devel cracklib-devel libtdb-devel libevent-devel tcp_wrappers-devel libcddb-devel libdbi-devel mysql-devel openldap-devel systemtap-sdt-devel dbus-glib-devel Sounds promising, lets go to their download page and snag the latest copy (3.1.7 as of 03/2015), direct link to Netatalk 3.1.7.įirst we need some prerequisites installed: yum groupinstall 'Development Tools' AFP stands for Apple Filing Protocol and it’s non-proprietary linux version is called Netatalk. I did a little research and it seems Apple has something called AFP, which is apparently it’s native file sharing. Imagine working with many large files over this SMB share and then consider that it’s also unresponsive between interactions adding more seconds of delay each time it’s accessed. Sent 409650131 bytes received 42 bytes 39014302.19 bytes/secĪs you can see I more than double my performance by using SSH instead of Samba, 38.7MB/s vs 17.3MB/s, 10 seconds vs. Mac-Pro:~ $ rsync -avP testfile file list. That’s not very impressive, just 17.3MB/s, let’s see what we get if we rsync over SSH instead of SMB. Below is the documentation of the procedure I followed and any outcome I was able to document.įirst I wanted to benchmark SMB performance from OS X to the CentOS server running SMB: Mac-Pro:~ $ dd if=/dev/urandom of=~/testfile bs=4k count=100000Ĥ09600000 bytes transferred in 25.887503 secs (15822306 bytes/sec) Tonight I decided to install Netatalk, latest version on my CentOS server from source code. On OS X however I’ve never had any luck, the connectivity is slow, buggy and generally unreliable.

Linux netatalk server windows#

I have a lot of experience with SMB and I’ve never had much trouble working with Linux servers and Windows clients. My Mac Pro absolutely must access that ZFS share reliably and it would be nice if my two Mac Books were able to as well. The server has a large ZFS share with all my backups and archives as well as various KVM instances running off SSDs.

I’ve struggled to improve Samba (SMB) performance between my Mac Pro (Late 2013) running OS X Yosemite 10.10.2 and my CentOS 6.6 Linux server.