Webmin Module

The official Webmin module for Netatalk was first created in the year 2000. It facilitates the administration of the AFP server via a user friendly Web GUI.

At the time of writing, maintained modules for the latest stable Netatalk v3 as well as oldstable Netatalk v2 exist. Find the source code and release tarballs for both in the netatalk-webmin Git repository. They are confirmed compatible with Debian, Fedora, and Solaris.

This page is meant to give an overview of the feature set and usage notes of the module. Installation instructions can be found in the respective README file, and will not be repeated here.

v3 Module

Netatalk v3 got an entirely rewritten ini-style configuration file format, replacing the legacy format in v2 and earlier. Therefore, the backend of the Webmin module was entirely rewritten from scratch.

The module index is the hub for all of the module's features. You can see the configured shared volumes, as well as start and stop the netatalk daemons from here.

Create or edit a shared volume

Create or edit volume presets

Can be used to streamline configuration of multiple volumes at once.

Create or edit home shares

Modify global server settings

v2 Module

The legacy v2 version of the Webmin module allows you to control the AFP server as well as the AppleTalk services.

The module index is the hub for all of the module's features. You can see the configured shared volumes and virtual servers, as well as start and stop the Netatalk and AppleTalk daemons from here.

Create or edit shared volume

Complete support for all volume options are available when creating new or editing shared volumes. Equivalent to editing AppleVolumes.default.

Global server settings

All virtual AppleShare server options are available through the GUI. Equivalent to editing afpd.conf.

Config editor

An interactive config file editor is also available for manual fine tuning of settings.

Common Functions

These functions are identical between the v3 and v2 versions of the module.

Connected user management

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.

Server capabilities

The response from asip-status gives you an overview of the addresses and capabilities of the AFP server.