mirror of
https://github.com/rzuasti/oott.git
synced 2026-07-08 19:21:54 +02:00
rzuastiandClaude Opus 4.8
b283699b3c
A typical router keeps active devices' ARP entries fresh continuously, so a 10-minute poll interval stays well within common ARP cache TTLs while keeping device-event churn modest (each poll records a DeviceSeen event per device). A 5s per-request timeout adds margin for a busy agent or large ARP table at no cost on the happy path. Updates the default in settings.rs and the sample TOML, README and NixOS module. TODO timing-review item narrowed to the ARP scanner. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
OOTT ToDo list
- Add linting to CLAUDE.md for both Rust and Dart
- Review and document the release process
- Add support for push notifications to the app (iOS and Android)
- Review the README.md file
Backend
- Add configuration options to enable/disable each scanner
- Implement the pushover API call directly to support HTML content and review notification text to use it
- Add "devices seen on last scan" to the ARP and SNMP scanners status
- Review the recommended timings for the ARP scanner (change defaults) — SNMP defaults set to 10m/5s
Frontend
- Can we add front-end tests?
- Break down oott_api.dart in modules
Improve engine
Passive (low noise, no probing):
- Passive packet capture — observe any broadcast/multicast traffic; a device that never responds to ARP still generates traffic
Active (you probe the network):
- NDP (Neighbor Discovery Protocol) — IPv6 equivalent of ARP; important if the network uses IPv6
Via infrastructure:
- SNMP query to router/firewall — pull the ARP table directly via SNMPv2c (no local probing); see
[snmp_scanner]config - Extend the SNMP scanner: SNMPv3 support, and switch MAC/forwarding table (port/VLAN) polling