mirror of
https://github.com/DaLaw2/NetGuardia.git
synced 2026-08-24 14:10:28 +09:00
DaLaw2
004daafdcf
Three rates the operator actually needs to judge whether fusion is
doing its job: how often sources agree, how often windows get dropped
under LRU pressure, and which source dominates the firing mix.
- `core/detection/metrics.rs` holds a lock-free `FusionMetrics` struct
with relaxed-order `AtomicU64` counters for total emits, multi-source
emits, LRU-pressure evictions, and per-source ingress counts. Shared
via `Arc` — readers never block the orchestrator task.
- `FusionMetricsSnapshot` precomputes `agreed_rate`,
`window_drop_rate`, and a `PerSourceRate` view so the frontend never
re-implements the formulas and drifts.
- Orchestrator instruments three call sites:
- `handle_detection` → `record_fire(source)` before canonicalization
so the per-source counter reflects raw ingress.
- `emit_fused` → `record_emit(active_source_count)` so multi-vs-solo
is tagged by the actual count used in the fused event.
- Path B dedup `put` → when the LRU is at capacity and the key is
absent, bump `windows_evicted` and log
`DetectionLog::FusionWindowEvicted` with the evicted key. Wires
up the log variant that was previously declared but unused.
- `AppServices` owns the `Arc<FusionMetrics>`. `system.rs` threads it
into `DetectionOrchestrator::new`; `http_server.rs` injects it as
Actix `app_data`.
- New `adapter/http/fusion.rs` scope at `/api/fusion/metrics` returning
the snapshot JSON. Future `/api/fusion/explain/{ip}` lands in the
same scope.
Tests: 5 new (zero-traffic snapshot is all-zeros, agreed_rate reflects
multi/total ratio, window_drop_rate isolates evictions from emits,
per-source rates sum to 1.0, record_fire routes to the correct
bucket). 224 pass total. clippy --package net-guardia -- -D warnings
clean.
Closes B-region Q-6.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
NetGuardia
Project Overview
NetGuardia is a high-performance network security solution that combines eBPF XDP technology with deep learning models to provide advanced network protection. The system operates as a standalone network appliance that can run on any Ubuntu-based system with compatible network hardware.
Core Technologies
- eBPF XDP Technology - Provides high-performance packet processing directly at the data link layer
- Deep Learning Models - Identifies and predicts potential network attacks with intelligent threat detection
- Hardware Integration - Designed to work with Intel i350 T2 and similar enterprise-grade network interface cards
Functional Modules
Resource Overview
- Real-time control system occupancy rate
Dashboard Overview
- Real-time network traffic monitoring and visualization
- Recent traffic statistics and trend analysis
Detailed Traffic Statistics
- Detailed traffic usage information per IP address
Network Access Control
- IPv4/IPv6 whitelist and blacklist management
- Precise port-level access control
System Features
- High Performance - Low-latency packet processing with minimal network performance impact
- User-Friendly - Cross-platform web management interface with intuitive operation
- Reliability - Hardware-accelerated processing ensures stable operation
- Scalability - Modular design supports functional expansion
System Requirements
NetGuardia requires the combination of a kernel with eBPF support and a NIC driver that implements AF_XDP on that kernel. There is no single "minimum kernel version" — it depends on which NIC driver you use.
- Linux with eBPF + AF_XDP support for your NIC driver. Any modern distribution (Ubuntu 22.04+, Debian 12+, RHEL 9+, Fedora recent) is fine as long as the driver matrix below lines up.
- Dual-port NIC with an AF_XDP-capable driver (see matrix).
- Root / sudo access for eBPF program loading.
NIC driver / kernel matrix (AF_XDP)
| Driver | NIC family (examples) | Min kernel for AF_XDP |
|---|---|---|
| mlx5 | Mellanox ConnectX-4/5/6/7 | 5.x (early) |
| ixgbe | Intel 82599, X520, X540, X550 | 5.x |
| i40e | Intel X710, XL710, XXV710 | 5.x |
| ice | Intel E810 | 5.5+ |
| igb | Intel i350 T2 (reference hardware) | 6.17 |
| igc | Intel I225/I226 | 6.x |
| virtio_net | QEMU/KVM virtual NICs | varies; AF_XDP is limited |
If you are using the reference Intel i350 T2, you need Linux 6.17 or newer because
igb AF_XDP support landed in that release. On a kernel older than 6.17 the system
will still build, but ingress/egress setup will fail at runtime when AF_XDP
binding is attempted — check driver support with ethtool -i <iface> and confirm
against the matrix above before deploying.
Hardware Compatibility
- Network Interface: dual-port NIC with an AF_XDP-capable driver on your kernel (see matrix above). Intel i350 T2 is the reference hardware.
- CPU: multi-core recommended; XDP scales with RX queue count.
- Memory: 8 GB minimum, 16 GB+ for high-traffic environments.
NetGuardia is not limited to embedded platforms — it runs on standard server hardware, virtual machines, or dedicated appliances as long as the driver/kernel requirement above is met.