TheRealSirHaXalot / AntiHunter-Command-Control-PRO
AntiHunter Perimeter Defense Systems
AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing TheRealSirHaXalot/AntiHunter-Command-Control-PRO in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Repository Overview (README excerpt)
Crawler viewAntiHunter Command & Control Pro AntiHunter Command & Control PRO is the companion operations platform for the AntiHunter SIGINT mesh network. Flash your AntiHunter detection nodes with the AntiHunter builds, then connect them here to orchestrate the entire perimeter defense mission. The Command Center ingests every heartbeat, target hit, triangulation update, and vibration alert from the mesh, renders nodes and geofences on a live map, automates scan/baseline/triangulation workflows, and drives alarm cues, exports, and audit trails. > **Firmware note:** The companion firmware for mesh detection nodes lives in lukeswitz/AntiHunter. Flash those builds to your field hardware before connecting them to this Command Center. > **Early Release:** This is a beta build. Expect stability issues, breaking changes, and evolving features. > **Security disclosure:** The platform has **not** undergone formal penetration testing or hardening for Internet-exposed deployments. Run it on trusted networks only, behind your own perimeter controls, until a full security review is complete. --- Table of Contents • Overview • Core Features • Key Highlights • Digital Detection, Scanning & Triangulation • Drone Awareness & FAA Enhancements • UI Modules at a Glance • Architecture • Security & Hardening • Repository Layout • Quick Start • Prerequisites • Platform Setup • Installation • Configuration • Database & Migrations • Running the Stack • Updating an Existing Deployment • Running with Docker • Building for Production • Production Deployment • Serial Hardware & Meshtastic Sniffer • Useful Scripts • Operations & Maintenance • Troubleshooting • Legal Disclaimer --- Overview AntiHunter Command & Control PRO turns raw radio/mesh telemetry into actionable situational awareness. The application keeps track of nodes, devices, and geofences, allows operators to launch complex detection sequences, and streams alerts through a tone-aware alarm engine. Everything is multi-site aware and backed by Prisma/PostgreSQL for durability. Core Features Key Highlights Digital Detection, Scanning & Triangulation • **Digital detections**: Meshtastic-like frames are parsed in real time and normalized into inventory entries with vendor/OUI resolution. The detector renders RSSI, timestamps, and raw payloads so analysts can confirm legitimacy. • **Scanning workflows**: Command presets fire scan/baseline/deauth/randomization pipelines against nodes, with FOREVER protections and audit trails. Operators can schedule sweeps, chain commands, and monitor acknowledgements/results inside the console. • **Tracking**: Every detection updates the live map with trails, heading vectors, RSSI pulses, and site-specific coloration. Inventory rows store the location history so you can pivot from console map export seamlessly. • **Triangulation**: Multi-node detection events feed the triangulation engine, capturing angle-of-arrival data set by the nodes. Results surface in the Targets module with exports for external tooling (e.g., CSV/GeoJSON) and can be reviewed in the map view as overlays. • **Exports & auditing**: Scan logs, triangulation snapshots, and detection histories are exportable from their respective modules, ensuring mission reporting and post-op analysis are one click away. Drone Awareness & FAA Enhancements Drone Tracker & Inventory Drawer • The live map now spawns a **Drone Tracker & Inventory** drawer whenever a telemetry frame arrives. The drawer lists every tracked drone/operator pair on a single line, shows the current heading (cardinal string), operator details, FAA metadata, and exposes map focus buttons for each entry. • Clicking a drone or operator on the map re-opens the drawer if it was dismissed. Hostile rows pulse red, neutral/friendly rows pick up their site colors, and **Unknown** defaults to the new blue palette so status is immediately obvious. • Status changes (Friendly / Neutral / Hostile) are committed through and reflected everywhere (map markers, drawer rows, Socket.IO events, MQTT federation). The UI guards against race conditions so you can keep toggling a status even while telemetry continues to stream. • Set (see Configuration) to automatically mirror every drone detection into the Inventory module; clearing inventory now flushes the drone cache and removes map markers until fresh telemetry arrives. FAA Registry Integration • The **Config -> FAA Registry** card can download and parse the public archive from the FAA ( ). Uploading the ZIP (or just ) populates the local lookup cache. • When the Command Center has internet access, it also performs on-demand lookups using the uasdoc API ( ) through a throttled background queue. Results are cached for (default 60) and each RID/MAC lookup is rate-limited via (default 10). • FAA matches update the drawer, map tooltips, and websocket/MQTT payloads automatically, so operators always see the craft and registrant names even after a restart. Drone Geofence Breach Alarms • Geofences now evaluate drone positions in addition to ground nodes. Tripping a perimeter raises a dedicated **Drone Geofence Breach** alarm level with its own sound slot on the **Config -> Alarms** page. • While a breach is active the impacted geofence keeps its configured color but pulsates to draw attention, and the Drone Tracker drawer highlights the offending aircraft. Flight Trails, Operators, and Persistence • Each drone and operator pin now uses the same status-driven palette, includes heading vectors, and draws a historical trail so you can reconstruct the approach path. • The backend keeps only one copy of each drone snapshot in memory and debounces writes to the database, preventing the persistence flood that previously occurred when running simulators or high-rate feeds. • MQTT federation has been updated to publish only local drones and to retry failed subscriptions with exponential backoff, ensuring remote sites receive telemetry even across flaky links. Simulator-Driven Testi…