How tworjaga/esp32watchdog works
ESP32Watchdog is an autonomous, passive Wi-Fi threat monitor. Wireless traffic enters the scan task, which filters and parses packets and applies the DEAUTH, TWIN, and FLOOD detectors; alerts are queued for a dedicated SD-writing task. A separate UI task reads device state, displays status and alerts, drives the LED, and handles button input to change modes or restart. The README documents these responsibilities and relationships, but no source excerpts were provided, so implementation-level call details are unavailable.
Main entry points: ESP32Watchdog.ino Scan task
Components 15
Packet Scanning
- Scan task
ESP32Watchdog.ino - Packet pool
ESP32Watchdog.ino - Channel hopping
ESP32Watchdog.ino
Threat Detection
- DEAUTH detector
ESP32Watchdog.ino - TWIN detector
ESP32Watchdog.ino - FLOOD detector
ESP32Watchdog.ino - Alert queue
ESP32Watchdog.ino
Device Output
- SD write task
ESP32Watchdog.ino - CSV logs
ESP32Watchdog.ino - UI task
ESP32Watchdog.ino - OLED display
ESP32Watchdog.ino - Status LED
ESP32Watchdog.ino - Button
ESP32Watchdog.ino
Other components
- Wi-Fi traffic
- Device user
Connections 15
- Wi-Fi traffic → Scan task: supplies frames
README.md - Scan task → Packet pool: claims and releases
README.md - Scan task → DEAUTH detector: checks frames
README.md - Scan task → TWIN detector: checks frames
README.md - Scan task → FLOOD detector: checks frames
README.md - Scan task → Channel hopping: advances channels
README.md - DEAUTH detector → Alert queue: queues alerts
README.md - TWIN detector → Alert queue: queues alerts
README.md - FLOOD detector → Alert queue: queues alerts
README.md - SD write task → Alert queue: reads indices
README.md - SD write task → CSV logs: writes rows
README.md - UI task → OLED display: draws status
README.md - UI task → Status LED: drives patterns
README.md - Device user → Button: presses
README.md - Button → UI task: cycles mode
README.md