Deployment Guide

Installation

From Source

cd sdk
make -j$(nproc)
sudo make install

Default installation directory: /opt/mmt/dpi/

To install to a custom directory:

sudo make install MMT_BASE=/path/to/install

From Debian Package

cd sdk
make deb
sudo dpkg -i mmt-dpi_*.deb

Uninstall

cd sdk
sudo make dist-clean

Installed Files

After installation, the following files are placed:

/opt/mmt/
├── dpi/
│   ├── include/     # Header files for development
│   └── lib/         # Shared libraries (libmmt_core.so, etc.)
├── plugins/         # Protocol plugin libraries (rules/common.mk:7)
└── examples/        # Example sources (rules/common.mk:8)

The library path is configured via /etc/ld.so.conf.d/mmt-dpi.conf (sdk/Makefile:89,145).

Linking Against MMT-DPI

gcc -o myapp myapp.c \
    -I /opt/mmt/dpi/include \
    -L /opt/mmt/dpi/lib \
    -lmmt_core -ldl

For TCP/IP protocol attributes:

gcc -o myapp myapp.c \
    -I /opt/mmt/dpi/include \
    -L /opt/mmt/dpi/lib \
    -lmmt_core -lmmt_tcpip -ldl -lpcap

Runtime Configuration

Plugin Loading

By default, plugins are loaded from /opt/mmt/plugins/ (rules/common.mk:7). You can also place plugins in a plugins/ directory relative to your application binary.

Environment Variables

No environment variables are documented in the codebase for runtime configuration. The plugin load path is compiled in at build time from MMT_BASE; the contract is stated once, in Agent Environment Notes §4 MMT_BASE Install-Prefix Behavior.

Production Considerations

See Deployment Considerations for detailed guidance on: