Difference between revisions of "Netatalk"

From ArchWiki
Jump to: navigation, search
(Installation)
(Link for iptables.)
 
(19 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
[[Category:Networking]]
 
[[Category:Networking]]
[https://aur.archlinux.org/packages.php?ID=10032 Netatalk] v3.0 is a free, open-source implementation of the Apple Filing Protocol (AFP). It allows Unix-like operating systems to serve as file servers for Macintosh computers.
+
[[ja:Netatalk]]
 
+
Netatalk is a free, open-source implementation of the Apple Filing Protocol (AFP). It allows Unix-like operating systems to serve as file servers for Macintosh computers.
The older version of netatalk, v2.2.3, is distributed as [https://aur.archlinux.org/packages.php?ID=59006 netatalk-ddp] and supports the Apple Macintosh network protocols, including AppleTalk (ATalk), Apple Filing Protocol (AFP), and Printer Access Protocol (PAP).
+
 
+
==Compiling==
+
Use either the netatalk or netatalk-ddp packages available in AUR, which have initscripts tailored for ArchLinux.
+
 
+
===Choosing Features===
+
With the deprecation of DDP (ATalk, PAP, timelord, and a2boot were removed in v3.0), netatalk has been divided into netatalk and netatalk-ddp. DDP is only necessary to support Mac OS  <= 9, but OS X <= 10.3 will also benefit from the integration of SLP since it does not fully support Bonjour/Zeroconf. DDP would network older Macs which ran on AppleTalk instead of TCP/IP, and timelord and a2boot were for time-synchronization and Apple II booting. PAP may still be necessary for users with LaserWriter printers without TCP/IP support.
+
 
+
A build of the netatalk AUR package will only build the "modern" features cnid_metad and afpd, with Bonjour/Zeroconf support only.
+
 
+
To build the full complement of features with SLP support, build netatalk-ddp instead.
+
  
 
==Installation==
 
==Installation==
Install your finished package with pacman as usual, and remember to add "netatalk" to the daemons list in {{Ic|/etc/rc.conf}}. If using systemd, and compiled with {{Ic|--with-init-style&#61;systemd}}, remember to {{Ic|systemctl enable netatalk.service}}.
+
Netatalk can be [[install]]ed with the {{AUR|netatalk}} package.
  
Besides the configuration files that are installed (and checked during upgrade), netatalk may generate two files {{Ic|/etc/netatalk/afp_signature.conf}} or {{Ic|/opt/netatalk/afp_signature.conf}} which holds the system UUID, and {{Ic|/etc/netatalk/afp_voluuid.conf}} or {{Ic|/opt/netatalk/afp_voluuid.conf}} which holds volume UUIDs for TimeMachine. These files may remain after package removal and should be kept in most cases to disambiguate the services broadcast over the local network.
+
==Configuration==
===Netatalk-ddp Initscripts===
+
Enable and/or start {{ic|netatalk.service}} [[systemd#Using units|using systemd]].
To emulate the init functionality of the systems fully-supported by netatalk, one initscript "netatalk" is responsible for starting and stopping the individual daemons. The script checks for the binaries available on the system, and starts them in a specific order, skipping those that are already running. The stop process occurs in reverse. To prevent ambiguity, only "netatalk" registers as a daemon with the system, but is silent, it doesn't echo any messages. The individual initscripts echo to the terminal, but don't register as daemons to prevent confusion.
+
  
The individual scripts are provided for users who may want to manage the daemons at runtime or add specific arguments, but don't worry, they will obey the necessary dependencies for proper operation. If a daemon is required by others, it won't stop until its children aren't running; if a daemon has dependencies it won't start until these are met.
+
Besides the configuration files that are installed (and checked during upgrade), netatalk may generate two files {{Ic|/etc/netatalk/afp_signature.conf}} or {{Ic|/var/state/netatalk/afp_signature.conf}} which holds the system UUID, and {{Ic|/etc/netatalk/afp_voluuid.conf}} or {{Ic|/var/state/netatalk/afp_voluuid.conf}} which holds volume UUIDs for TimeMachine. These files may remain after package removal and should be kept in most cases to disambiguate the services broadcast over the local network.
  
==Configuration==
+
Netatalk 3.x uses a single configuration file, {{ic|/etc/afp.conf}}. See {{ic|man afp.conf}} and the following example (make sure processes have write access to {{ic|afpd.log}}):
===Netatalk===
+
{{hc|/etc/afp.conf|<nowiki>
Netatalk v3.0 now uses a single configuration file, {{Ic|/etc/afp.conf}}. Installing v3 will move any old config files ({{Ic|/etc/netatalk/afpd.config}}, {{Ic|/etc/netatalk/AppleVolumes.default}}) out of the way. Global options and volume definitions will need to be added to {{ic|/etc/afp.conf}}. See {{ic|man afp.conf}} for help, but here is an example:
+
 
+
{{hc|/etc/afp.conf|
+
 
[Global]
 
[Global]
hosts allow &#61; 192.168.1.0/16
+
mimic model = TimeCapsule6,106
 +
log level = default:warn
 +
log file = /var/log/afpd.log
 +
hosts allow = 192.168.1.0/16
 +
 
 +
[Homes]
 +
basedir regex = /home
  
 
[TimeMachine]
 
[TimeMachine]
path &#61; /srv/share/timemachine
+
path = /mnt/timemachine
valid users &#61; joe
+
valid users = tmuser
time machine &#61; yes
+
time machine = yes
  
[media]
+
[Shared Media]
path &#61; /srv/share/media
+
path = /srv/share/media
valid users &#61; joe sam}}
+
valid users = joe sam
 
+
</nowiki>}}
In addition, the daemons init scripts have been consolidated with this version. If you have {{ic|afp}}, {{ic|cnid}}, etc in you {{ic|rc.conf}} {{ic|DAEMONS}} list, remove then. Just {{ic|netatalk}} should appear.
+
{{Warning|Avoid using symbolic links in {{ic|afp.conf}}}}
 
+
===Guest access===
If you have issues with {{ic|CNID}}, try rebuilding the databases. I had to remove the {{ic|.AppleDB}} files and run {{ic|dbd}}. This has the benefit of moving the {{ic|.AppleDB}} files into {{ic|/etc/netatalk/CNID}} rather than the root of the volume.
+
In order to allow guest '''read-only''' access to your shared folders, add following line to the {{ic|[Global]}} section:
 
+
{{hc|/etc/afp.conf|<nowiki>
{{bc|
+
[Global]
# Save the old .AppleDB files
+
uam list = uams_guest.so
tar -cvzf /path/to/your/volume/.AppleDB
+
</nowiki>}}
rm -rf /path/to/your/volume/.AppleDB
+
To allow guest '''read/write''' access, first, allow read-only access as in the previous example and then add following lines to a particular share section:
# Rebuild
+
{{hc|/etc/afp.conf|<nowiki>
dbd -r /path/to/your/volume
+
[Your Share]
# Wait... on a large share it can take hours
+
path = /mnt/public/share
}}
+
rwlist = nobody
 
+
</nowiki>}}
One note: '''avoid symbolic links the volume paths.''' This caused me significant headaches. Also, I was able to eliminate the {{ic|uams}} and {{ic|cnidscheme}} configuration options that were previously in my v2 configuration files. The (new) defaults worked well.
+
  
===Netatalk-ddp===
 
====System====
 
Edit the afpd configuration file ({{Ic|/etc/netatalk/afpd.conf}}), and add a line similar to
 
{{hc|/etc/netatalk/afpd.conf|...<br>- -mimicmodel TimeCapsule6,106 -setuplog "default log_warn /var/log/afpd.log"}}
 
This tells netatalk to use the system's hostname, mimic a TimeCapsule, and log warnings and errors to file.
 
====Volumes====
 
Edit the volumes configuration file {{Ic|/etc/netatalk/AppleVolumes.default}}, and append the following to add a TimeMachine-like share
 
{{hc|/etc/netatalk/AppleVolumes.default|...<br><path_to_share> <sharename> allow:<username> options:usedots,upriv,tm}}
 
* The {{Ic|volsizelimit:<limit_in_whole_mebibytes>}} argument can be useful here to limit the total space reported to TimeMachine.
 
* If you wish to turn off "home" shares, change the {{Ic|~}} line to {{Ic|#~}}.
 
{{Warning|Avoid nesting volumes, and do not share directories by any other protocol. All file changes must be made via afpd only}}
 
 
==IP Tables==
 
==IP Tables==
If you use the iptables package for firewall services, consider adding the following: (replace {{Ic|-I}} with {{Ic|-A}} as necessary)
+
If you use the [[iptables]] package for firewall services, consider adding the following: (replace {{Ic|-I}} with {{Ic|-A}} as necessary)
 
{{hc|Bonjour/Zeroconf|iptables -I INPUT -p udp --dport mdns -d 224.0.0.251 -j ACCEPT
 
{{hc|Bonjour/Zeroconf|iptables -I INPUT -p udp --dport mdns -d 224.0.0.251 -j ACCEPT
 
iptables -I OUTPUT -p udp --dport mdns -d 224.0.0.251 -j ACCEPT}}
 
iptables -I OUTPUT -p udp --dport mdns -d 224.0.0.251 -j ACCEPT}}
Line 80: Line 59:
 
==Enable Bonjour/Zeroconf==
 
==Enable Bonjour/Zeroconf==
 
Bonjour/Zeroconf is now a requirement of netatalk and is compiled by default. No configuration is necessary, netatalk will register its own services using the dbus link. Make sure you set {{Ic|-mimicmodel}} to the desired string (see {{Ic|/System/Library/CoreServices/CoreTypes.bundle/Contents/Info.plist}} on a Mac for a full list).
 
Bonjour/Zeroconf is now a requirement of netatalk and is compiled by default. No configuration is necessary, netatalk will register its own services using the dbus link. Make sure you set {{Ic|-mimicmodel}} to the desired string (see {{Ic|/System/Library/CoreServices/CoreTypes.bundle/Contents/Info.plist}} on a Mac for a full list).
 +
 +
You may need to enable and/or start {{ic|avahi-daemon.service}} [[systemd#Using units|using systemd]] if it is not running yet.

Latest revision as of 01:36, 28 November 2016

Netatalk is a free, open-source implementation of the Apple Filing Protocol (AFP). It allows Unix-like operating systems to serve as file servers for Macintosh computers.

Installation

Netatalk can be installed with the netatalkAUR package.

Configuration

Enable and/or start netatalk.service using systemd.

Besides the configuration files that are installed (and checked during upgrade), netatalk may generate two files /etc/netatalk/afp_signature.conf or /var/state/netatalk/afp_signature.conf which holds the system UUID, and /etc/netatalk/afp_voluuid.conf or /var/state/netatalk/afp_voluuid.conf which holds volume UUIDs for TimeMachine. These files may remain after package removal and should be kept in most cases to disambiguate the services broadcast over the local network.

Netatalk 3.x uses a single configuration file, /etc/afp.conf. See man afp.conf and the following example (make sure processes have write access to afpd.log):

/etc/afp.conf
[Global]
 mimic model = TimeCapsule6,106
 log level = default:warn
 log file = /var/log/afpd.log
 hosts allow = 192.168.1.0/16

[Homes]
 basedir regex = /home

[TimeMachine]
 path = /mnt/timemachine
 valid users = tmuser
 time machine = yes

[Shared Media]
 path = /srv/share/media
 valid users = joe sam
Warning: Avoid using symbolic links in afp.conf

Guest access

In order to allow guest read-only access to your shared folders, add following line to the [Global] section:

/etc/afp.conf
[Global]
uam list = uams_guest.so

To allow guest read/write access, first, allow read-only access as in the previous example and then add following lines to a particular share section:

/etc/afp.conf
[Your Share]
path = /mnt/public/share
rwlist = nobody

IP Tables

If you use the iptables package for firewall services, consider adding the following: (replace -I with -A as necessary)

Bonjour/Zeroconf
iptables -I INPUT -p udp --dport mdns -d 224.0.0.251 -j ACCEPT
iptables -I OUTPUT -p udp --dport mdns -d 224.0.0.251 -j ACCEPT
AFP
iptables -I INPUT -p tcp --dport afpovertcp -j ACCEPT
SLP
iptables -I INPUT -p tcp --dport slp -j ACCEPT
iptables -I OUTPUT -p tcp --dport slp -j ACCEPT
iptables -I INPUT -p udp --dport slp -j ACCEPT
iptables -I OUTPUT -p udp --dport slp -j ACCEPT
AppleTalk
iptables -I INPUT -p tcp -m multiport --dport at-rtmp,at-nbp,at-echo,at-zis -j ACCEPT
iptables -I OUTPUT -p tcp -m multiport --dport at-rtmp,at-nbp,at-echo,at-zis -j ACCEPT

Enable Bonjour/Zeroconf

Bonjour/Zeroconf is now a requirement of netatalk and is compiled by default. No configuration is necessary, netatalk will register its own services using the dbus link. Make sure you set -mimicmodel to the desired string (see /System/Library/CoreServices/CoreTypes.bundle/Contents/Info.plist on a Mac for a full list).

You may need to enable and/or start avahi-daemon.service using systemd if it is not running yet.