AFP_CLIENT(1)

✨ NAME ✨

okay bestie, meet afp_client 💖 It's the tool that lets you mount, unmount and control Apple Filing Protocol (AFP) sessions using the FUSE infrastructure 🦋

✨ SYNOPSIS ✨

afp_client mount|status|unmount|suspend|resume|exit [options]

✨ DESCRIPTION ✨

okay so the afp_client command handles the basics for AFP volumes 🎀 You can mount, unmount, get status, suspend and resume 💅

Do NOT mix this up with afpcmd 🙅‍♀️ afp_client is only for the FUSE client, and it works alongside afpfsd(1). afpcmd is a batch-mode file transferring client. Both of them use the afpfs-ng libraries 🌸

afp_mount(1) is normally a symlink to afp_client. It only handles mounting commands with a fully formed AFP URL ✨

✨ COMMANDS ✨

• mount — the name of the interface 🌈 This is usually a driver name followed by a unit number, so eth0 is the first Ethernet interface.
• mount [mount options] node — using the authentication and server info from your mount options, this mounts the remote filesystem on node 🧚 For more on those, check the "mount options" section further down. If you'd rather use AFP URL syntax, see mount_afp(1).
• unmount node — removes the AFP mount that's currently connected to node 👋
• status — shows status info for all connected servers 📊 You get each server's IP address, server descriptions (machine type, machine name, signature, login message), and available volumes. It also gives you statistics and other details. This is critical for debugging 💀
• suspend — suspends the current connections to all connected servers, but does not unmount them 😴 Currently unsupported.
• resume — resumes all suspended server connections 🔄 Currently unsupported.

Also, there's a stray line from the original sitting under resume, so here it is: enable or disable the promiscuous mode of the interface. If selected, all packets on the network will be received by the interface 👀

✨ MOUNT FLAGS ✨

• -u, --user <username> — log in using username 🫶
• -p, --pass <password> — if you put '-' as the password, you'll get prompted for it 🔐 This way you can use a password without exposing it on the command line.
• -o, --port <portnum> — uses TCP portnum instead of the default, 548 🔌
• -V, --volumepassword <volumepassword> — use this if the volume you're accessing has a volume password 🙈 It's a very weak form of protection since it's sent as clear text, so be careful. If you put '-' as the password, you'll get prompted for it, so it never has to be exposed on the command line.

The original repeats the '-' prompt paragraph twice under -V. Once is plenty, bestie 💅

• -v, --version <afp version> — picks the AFP version for a mount 🦋 For AFP 2.2, use 22. For 3.2, use 32, and so on. By default afpfs-ng chooses the highest AFP version shared between the client and server. afpfs-ng supports AFP 2.0 up to 3.2.
• -a, --uam <uam> — sets the authentication method to one of these 🔑
  • No User Authent
  • Cleartxt Passwrd
  • Randnum Exchange
  • 2-Way Randnum Exchange
  • DHCAST128
  • Client Krb v2
  • DHX2

If you don't specify a UAM, the most secure one that both the server and client (afpfs-ng) share will be chosen 🔒

• -m, --map <uam> — sets the method used to map local UIDs and GIDs to server ones 🗺️ The possible values are:
  • Common user directory — use this when the UID and GID of the client and server are expected to match perfectly 💜 An example is an NIS or open directory server.
  • Login ids — use this when you want all files to appear owned by the uid and gid of the userid you used for your authentication info 👑

✨ HISTORY ✨

afp_client is part of the FUSE implementation of afpfs-ng 🧚

✨ SEE ALSO ✨

afpfsd(1), mount_afp(1) 🔗

✨ AUTHORS ✨

Alex deVries, alexthepuffin@gmail.com 🌟

---

and that's the whole tea, bestie 🫶 This page came from afpfs-ng and is dated 3 February 2008 🍓 Stay iconic, stay mounted 💖✨