Netify Agent Requirements
Netify is a lightweight, high-performance deep packet inspection (DPI) and traffic intelligence solution that delivers real-time network telemetry and actionable insights with minimal resource overhead. Optimized for efficiency, Netify can operate on a wide range of hardware platforms - from embedded systems to enterprise servers - while maintaining accurate protocol detection and flow analysis.
The following sections outline the minimum and recommended system requirements for deploying Netify on supported platforms.
Supported Operating Systems
Linux
- Kernel 3.10 or newer recommended
- x86_64, ARM, and MIPS architectures supported
FreeBSD
- Version 13 or newer recommended
- x86_64 architecture supported
Supported Containers
Contact us for information on deploying Netify inside Docker or LXC/LXD containers.
Installation Footprint
Netify's installation requires approximately 10MB of storage. Additional space may be required for:
- Commercial signatures
- Installed Netify plugins
- Local logging or telemetry storage
- Local caching
Recommended Cores
Based on Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
Network Capture Performance
NFQUEUE redirects traffic to user space and often serves as a bridge to specialized hardware packet accelerators for high-throughput processing. TPACKET_V3 is a high-performance, zero-copy interface that batches packets into memory blocks to minimize CPU overhead. PCAP is the industry-standard library that provides a portable API for packet capture and filtering.
NFQUEUE
| Active flows | Minimum | Recommended |
|---|---|---|
| 1-500 | 1 | 1 or more |
| 500-1000 | 1 | 2 |
| 1000-100K | 2 | 3 |
| 500-1000 | 2 | 4 |
TPACKET_V3
| Active flows | Minimum | Recommended |
|---|---|---|
| 1-500 | 1 | 2 |
| 500-1000 | 2 | 4 |
| 1000-100K | 4 | 6 |
| 500-1000 | 6 | 8 |
PCAP
| Active flows | Minimum | Recommended |
|---|---|---|
| 1-500 | 1 | 2 |
| 500-1000 | 2 | 4 |
| 1000-100K | N/A | N/A |
| 500-1000 | N/A | N/A |
Performance Considerations
Netify performance can be highly influenced by:
- Packet capture rate and interface bandwidth
- Type of bandwidth (long-running flows vs. short/sporadic)
- Number of active flows
- Type and number of plugins enabled
- Logging and telemetry frequency
- Configuration