-
Notifications
You must be signed in to change notification settings - Fork 100
Webmin Module
The Netatalk Webmin module facilitates the administration of the AFP server via a user friendly Web GUI.
As of Netatalk 4.0, the Webmin module is bundled with Netatalk proper. The module is distributed as a .wbm.gz with each release, e.g. netatalk-4.4.1.wbm.gz for Netatalk 4.4.1.
Install the tarball from within the Webmin UI, or on the CLI:
- From the dir where Webmin is installed, run
./install-module.pl /path/to/netatalk_webmin-x.y.z.wbm.gz - From within the Webmin UI: Configuration -> Modules -> select the tarball from the local file system
Hit the gear icon next to the module name to configure it. By default, the module will be configured to use systemd init commands and /usr prefix directories.
When building from source, pass -Dwith-webmin=true to the build system to build and install the module.
For the old stable versions Netatalk v3 and Netatalk v2 exist, find the source code and release tarballs in the netatalk-webmin Git repository.
The module is tested on Debian, Fedora, and Solaris.
For deeper technical information, see the Webmin module's README file.
By default when installed from tarball, the module will look for binaries in /usr/sbin and config files in /usr/etc and use systemd init system commands for starting and stopping the services.
If needed, you can make manual adjustments in the config file in the installed module or via the Webmin UI,
on the Netatalk module's Module Config page.
The Module Config page is typically accessible through the little gear icon in the module's title bar.
When installed from the Meson build system, the build scripts will attempt to detect and configure the correct binary and config file paths, as well as init commands, for your system.
If you have netatalk running a container, you can deploy another container with the webmin module in the same constellation for a nice user-friendly way to manage your setup.
Either build the container yourself from the Dockerfile in the root of the netatalk code repo, or pull a pre-built image from Docker Hub or the GitHub repo.
See the container docs for usage notes.
Netatalk v4 combines the best aspects of Netatalk v3 and v2, so the Netatalk Webmin module does the same. While building on the solid foundations of the v3 module, it adds the ability to manage AppleTalk services.
(Screenshot from 4.x module)
(Screenshot from 3.x module)
Can be used to streamline configuration of multiple volumes at once.
(Screenshot from 3.x module)
(Screenshot from 3.x module)
(Screenshot from 3.x module)
Each connected user has its own forked afpd daemon process that is owned by that user. By killing the process, the connected user will be effectively kicked off the server.
(Screenshot from 2.x module)
The response from asip-status gives you an overview of the addresses and capabilities of the AFP server.
(Screenshot from 2.x module)
Resources
- Getting Started
- FAQ
- Troubleshooting
- Connect to AFP Server
- Webmin Module
- Benchmarks
- Interoperability with Samba
OS Specific Guides
- Installing Netatalk on Alpine Linux
- Installing Netatalk on Debian Linux
- Installing Netatalk on Fedora Linux
- Installing Netatalk on FreeBSD
- Installing Netatalk on macOS
- Installing Netatalk on NetBSD
- Installing Netatalk on OmniOS
- Installing Netatalk on OpenBSD
- Installing Netatalk on OpenIndiana
- Installing Netatalk on openSUSE
- Installing Netatalk on Solaris
- Installing Netatalk on Ubuntu
Tech Notes
- Capturing AFP network traffic
- Kerberos
- Special Files and Folders
- Spotlight
- MySQL CNID Backend
- Slow AFP read performance
- Limiting Time Machine volumes
- Netatalk and ZFS nbmand property
Retro AFP
Development