mirror of
https://github.com/DaLaw2/NetGuardia.git
synced 2026-08-24 14:10:28 +09:00
DaLaw2
86358074b9
Land v12 M1. Promote the 88-arm feature match in PrecomputedStats::get()
to a FEATURE_REGISTRY (name → fn pointer) keyed by every legacy alias;
manifest validation consults it via feature_is_known(). Add a YAML
ModelManifest parser with AdapterKind { classifier_only, autoencoder_only,
multi_task }, per-label metadata (confirmations/playbook — parsed, wired
in M2), thresholds, and a scaler sidecar pointer. Introspect ONNX input
shape via tract's InferenceFact and cross-check against the manifest-
declared feature count; mismatches surface as MLError::FeatureMismatch
with both declared and onnx dims. Compose runtime MLInferenceConfig from
(manifest + scaler sidecar JSON) with order-sensitive feature reconcili-
ation — any drift between the two is rejected, not silently overridden.
service_factory prefers models/manifest.yaml when present; the legacy
JSON-only path remains as fallback. For multi_task manifests, model
filenames come from the manifest, not AppConfig. Ship models/manifest.yaml
describing the current v10 multi_task model (31 AE features, 10 labels).
Incidental clippy fixes bundled: reorder mod tests / impl blocks in
adapter/http/setup.rs and infrastructure/secret_store.rs to silence
items_after_test_module under --tests; rustfmt polish on unrelated drift.
New error variants: ManifestInvalid, FeatureMismatch, UnknownFeature.
New log variants: ManifestLoaded, OnnxShapeChecked.
Tests: +13 ML-layer tests — registry coverage of v10 features, alias
consistency, safe_div zero-denominator, manifest parse/validate, sidecar
feature-count rejection, real v10 ONNX introspection (AE=31,
classifier=32), end-to-end load_named via manifest paths. Suite 157/157;
cargo clippy --package net-guardia --tests -- -D warnings clean.
Co-Authored-By: Claude Opus 4.6 (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.