Skip to the content.

Architecture

Overview

MMT-DPI is a modular deep packet inspection library built around a plugin-based architecture. The core engine handles packet processing and session management, while protocol-specific logic is implemented in dynamically loaded plugins.

Components

Core Engine (src/mmt_core/)

The central component responsible for:

Protocol Plugins

Protocol implementations are organized into shared libraries loaded at runtime from plugins/ (the plugin list make install links there is MMT_LAYOUT_PLUGINS, sdk/Makefile:249; library names in rules/common.mk:216-223):

Plugin Library Description
mmt_tcpip libmmt_tcpip.so TCP/IP stack and application-layer protocols (HTTP, DNS, FTP, QUIC, etc.)
mmt_mobile libmmt_tmobile.so LTE/5G protocols (NAS, S1AP, NGAP, GTP, Diameter)
mmt_business_app libmmt_business_app.so Business application protocols
mmt_dicom libmmt_tdicom.so DICOM medical-imaging protocol

libmmt_security.so (the rule-based security engine) and libmmt_fuzz.so are not plugins: they are built only with ENABLESEC=1 (rules/common.mk:225-228) and linked by the application.

The LTE NAS decoder does not decrypt ciphered NAS messages (EEA1/EEA2/EEA3): the per-UE NAS keys cannot be derived from the traffic, and the SDK has no API for a host to supply them. A ciphered NAS PDU is decoded as plain text only when its S1 connection’s Security Mode Command selected EEA0 (null ciphering), or, when that command was not seen, if its first octet is the one of a plain NAS message. So after EEA1/EEA2/EEA3, s1ap.ue_ipv4 and s1ap.m_tmsi are not read from a ciphered Attach Accept. Background in the decision log (issue #452).

Build System (rules/, sdk/)

Platform-specific build rules supporting Linux (GCC, Clang, ICC), built natively on x86-64 and arm64; cross-compilation is not supported (ARM status).

Packet Processing Flow

Network Packet
    │
    ▼
┌─────────────────┐
│ packet_process() │  ← Core engine entry point
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│ Protocol        │  ← Walk the protocol stack (ETH → IP → TCP → HTTP...)
│ Classification  │
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│ Attribute       │  ← Extract registered attributes
│ Extraction      │
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│ Session Update  │  ← Update session state, statistics
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│ Handler         │  ← Invoke registered callbacks
│ Callbacks       │    (packet handlers, attribute handlers, session handlers)
└─────────────────┘

Key Abstractions

Plugin Interface

Plugins register protocols and their attributes via the core API during initialization. Each protocol provides:

See Add New Protocol for implementation details.