Install Client
This chapter covers the installation methods and platform requirements for the MSST-Net client.
Client Components
The MSST-Net client consists of the following parts:
- Client Core: Handles network connectivity and protocol processing.
- Client Controller: Handles client configuration and management.
Installation methods may vary by platform.
Installation Methods
MSST-Net provides the following installation methods:
- Using the client installer (recommended)
- Manual installation
Using the Client Installer (Recommended)
For desktop systems (Windows / Linux / macOS), the MSST-Net Client Installer is recommended.
The installer supports the following operations:
- Install: Download and deploy the latest client core and controller
- Update: Stop the service, replace old binaries, and restart
- Uninstall: Stop and remove the service, delete all installed files
On startup, the installer prompts you to choose:
- Controller type: Tauri (native desktop GUI) or WebUI (browser-based)
- Download source: Gitee (domestic mirror, recommended) or GitHub (official)
The installer also automatically:
- Installs the client core and controller
- Installs platform dependencies (e.g., wintun on Windows)
- Configures a system service (auto-start on boot, background operation)
- On Linux, prefers native packages (
.deb/.rpm) for the Tauri controller, falling back to AppImage when unavailable
Installation directories:
| Platform | Path |
|---|---|
| Linux | /opt/msst-net |
| Windows | C:\Program Files\MSST-Net |
| macOS | /usr/local/msst-net |
The installer must be run as root (Linux / macOS) or Administrator (Windows).
Download:
Download MSST-Net Client Installer
Manual Installation
If you prefer to install manually, download the client components:
Download MSST-Net Client Components
Desktop Installation
Desktop systems include:
- Windows
- Linux
- macOS
The following components are required:
- Client core (filename starts with
msst-net-client-core) - Client controller (filename starts with
msst-net-client-controller)
For controller selection, see:
Mobile Installation
Mobile systems (e.g., Android) use the Compose controller.
The Compose controller includes the client core — no separate core installation is needed.
Only the controller needs to be installed.
For controller details, see:
Platform Notes
Windows
The client core on Windows requires wintun.
When using the client installer, wintun is downloaded and installed automatically — no manual action needed.
For manual installation, place wintun.dll in the same directory as the client core.
Download:
Linux
Linux typically requires no additional dependencies.
For background operation, configuring a system service is recommended.
See:
macOS
macOS typically requires no additional dependencies.
For background operation, configuring a system service is recommended.
See:
Verifying Installation
After installation, perform the following checks:
- The client core starts successfully
- The client controller opens successfully
- The controller detects the client core
- A device ID is generated
If all checks pass, the client is installed correctly.
Next Steps
After installing the client:
- Configure a system service (optional)
- Complete access authentication
See: