Goal
Evaluate OpenWrt as the first non-FRITZ enhanced router integration after the router-adapter contract is stabilized.
Generic UplinkWitness monitoring should already remain independent of router APIs; this issue is specifically about optional deeper WAN/router telemetry.
Questions to resolve
- which stable OpenWrt interface should be used (for example ubus/rpcd or another documented local API)
- what authentication model is appropriate for a least-privilege local account
- which telemetry maps cleanly to the common adapter contract
- how WAN/session resets can be distinguished from router reboots
- what behavior is possible across common OpenWrt versions and WAN transports
Constraints
- do not weaken or complicate generic mode
- do not require cloud services
- avoid scraping unstable UI pages when a structured local interface exists
- do not advertise OpenWrt as supported until validated against real hardware or a detailed external compatibility report
Blocked conceptually by #4.
Goal
Evaluate OpenWrt as the first non-FRITZ enhanced router integration after the router-adapter contract is stabilized.
Generic UplinkWitness monitoring should already remain independent of router APIs; this issue is specifically about optional deeper WAN/router telemetry.
Questions to resolve
Constraints
Blocked conceptually by #4.