ATALKD.CONF(5)

💖 ATALKD.CONF(5) 💖 — the Netatalk AFP Fileserver manual, but make it cute

okay so bestie, we're doing the atalkd.conf page from the Netatalk AFP Fileserver Manual and I am so excited to tell you about it, because this file is literally the little config gremlin that tells atalkd how to set up your AppleTalk interfaces. no cap. let's get into it 🦋

---

✨ NAME ✨

atalkd.conf — the configuration file that atalkd uses to configure the interfaces that AppleTalk runs on. it's giving "wiring diagram but make it text file" fr fr 💅

---

🌸 DESCRIPTION 🌸

okay so atalkd.conf is the configuration file that atalkd reads to configure the Appletalk interfaces and how they behave. it's literally the vibe-setter for your network interfaces. periodt.

any line that is not prefixed with # gets interpreted. and listen — each interface has to be configured on one uninterrupted line, okay? there is no support for split lines. do not wrap that line, babe, it will not go well 😭

the configuration line format is:

interface [ -seed ] [ -phase <number> ] [ -net <net-range> ] [ -addr <address> ] [ -zone <zonename> ] ...

the simplest case, and honestly the icon behavior: either you have no atalkd.conf at all, or you have one with no active lines. in that case atalkd will auto-discover the local interfaces on the machine and write them to the atalkd.conf file — and it'll create that file if one doesn't already exist. it's giving "I'll handle it myself, don't worry about it" 👑

the interface is the network interface you want this to work over, like eth0 for Linux, or le0 for Solaris. slay.

note that all fields except the interface are optional. the loopback interface is configured automatically (bestie doesn't need your help). but if -seed is specified, then all other fields must be present — no skipping. also, atalkd will exit during startup if a router disagrees with its seed information 💀 so double-check that. if -seed is not given, all the other information may be overridden during auto-configuration. and if no -phase option is given, the default phase as given on the command line is used (and the default is 2). if -addr is given and -net is not, a net-range of one is assumed. little treat for you 🍓

the first -zone directive for each interface is the “default” zone. under Phase 1, there is only one zone, simple as that. under Phase 2, all routers on the network are configured with the default zone and must agree. atalkd maps “*” to the default zone of the first interface. note: the default zone for a machine is determined by the configuration of the local routers; to appear in a non-default zone, each service, e.g. afpd, must individually specify the desired zone. see also nbp_name(3). iykyk 🧚

the possible options and their meanings are:

🎀 OPTIONS 🎀

• -addr net.node — lets you specify the net and node numbers for this interface, written in AppleTalk numbering format (example: -addr 66.6). cute and precise ✨
• -dontroute — disables AppleTalk routing. it's the inverse of -router. the anti-router, if you will 💅
• -net first[-last] — lets you set the available net, optionally as a range. ranges? obsessed.
• -phase ( 1 | 2 ) — specifies the AppleTalk phase this interface is to use (either Phase 1 or Phase 2). pick your fighter ⭐
• -router — seed an AppleTalk router on a single interface. the inverse option is -dontroute. it's akin to -seed, but allows single interface routing. baby router energy 🫶
• -seed — seed an AppleTalk router. this requires two or more interfaces to be configured. if you have a single network interface, use -router instead. it also causes all missing arguments to be automatically configured from the network. no cap.
• -zone zonename — specifies a specific zone that this interface should appear on (example: -zone "Parking Lot"). please note that zones with spaces and other special characters should be enclosed in quotation marks. quotes are your bestie here, don't forget them 🔥

---

🌈 EXAMPLES 🌈

single interface on Solaris with auto-detected parameters:

le0

the same thing on Linux:

eth0

and below is an example configuration file from a Sun 4/40. this machine has two interfaces, “le0” and “le1”. the “le0” interface is configured automatically from other routers on the network. the machine is the only router for the “le1” interface. main character router behavior, honestly 👑

le0
le1 -seed -net 9461-9471 -zone netatalk -zone Argus

---

💜 SEE ALSO 💜

• atalkd(8)

---

👑 AUTHOR 👑

Contributors to the Netatalk Project (https://netatalk.io/contributors)

---

and that's the whole page bestie!! this was the ATALKD.CONF(5) page from the Netatalk AFP Fileserver Manual, Netatalk 4.5.1 edition 💖 go forth and configure your interfaces, you've got this, mwah 🎀✨