feat(topology): force-directed mesh graph from NEIGHBORINFO and TRACEROUTE#72
Open
iceice400 wants to merge 4 commits into
Open
feat(topology): force-directed mesh graph from NEIGHBORINFO and TRACEROUTE#72iceice400 wants to merge 4 commits into
iceice400 wants to merge 4 commits into
Conversation
…ROUTE Extend GET /api/analytics/topology with hours window, nodes, edges, and traceroute paths. Add Topology dashboard tab with D3 force graph; map overlay reads new response shape.
Co-authored-by: Cursor <cursoragent@cursor.com>
Build mesh links from NEIGHBORINFO, ROUTING route_reply/request, and TRACEROUTE paths with normalized node IDs and edge confidence. Add API stats for field debugging, design-token styling in the Topology tab and map overlay, and expanded unit tests. Co-authored-by: Cursor <cursoragent@cursor.com>
Add TOPOLOGY status strip with edge sources and packet counts. Show amber map banner when links exist but lack GPS on both ends. Co-authored-by: Cursor <cursoragent@cursor.com>
iceice400
added a commit
to iceice400/AA_Testing_meshpoint
that referenced
this pull request
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GET /api/analytics/topology?hours=24— returns{ nodes, edges, routes }from NEIGHBORINFO + TRACEROUTE (last 500 NI / 100 route packets)Why
Operators need a mesh link view beyond the map polylines. Reuses decoded NEIGHBORINFO/TRACEROUTE already in SQLite — read-only, no relay/TX impact.
Type
Testing
Manual checklist (on gateway with NEIGHBORINFO traffic):
Hardware: RAK7248 or Pi + HAT · US915 mesh with NEIGHBORINFO
Impact
Risks: Low — read-only SQL; edge query capped at 500 packets. D3 loaded from CDN (same pattern as Chart.js).
AI-assisted?