[Epic] MeshCore Phase 3 — Traceroute / path parity (planning)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- django, neo4j, python, react, typescript
- Domain
- backend-api-design, data-visualization, devtools
Research direction
This is a planning epic, not a task: it lists a spike and ADR on MeshCore versus MeshTastic traceroute semantics, a schema decision on AutoTraceRoute versus a new MeshCorePathObservation model, and Celery target selection. Start by reading the linked meshflow-api #360, meshflow-bot #119 and meshflow-ui #304 issues for the passive path slice. Done means those child issues are scoped and an ADR is written; it is not a code change.
Written by the indexing model from the issue text.
Description
Summary (future work)
MC path/trace or passive hop accumulation as traceroute analog; AutoTraceRoute.protocol or sibling model; scheduler filters by protocol; Neo4j edges labelled by protocol; UI filters on TR pages; MC new-node baseline.
Proposed breakdown
- Spike + ADR: MC vs MT traceroute semantics (
meshcore_py). - Schema: extend
AutoTraceRouteor addMeshCorePathObservation. pick_traceroute_target+ Celery: never mix MT sources with MC targets.traceroute_analytics/ Neo4j: protocol on nodes/edges.- UI: heatmap/topology/coverage protocol filter.
Milestone: MeshCore Support or post-MVP
Passive path visualization (filed 2026-05-26)
First concrete slice under this epic — passive route breadcrumbs on forwarded MC packets (not active AutoTraceRoute yet):
| Repo | Issue |
|---|---|
| meshflow-api | #360 — resolve path_hashes → observed nodes + API |
| meshflow-bot | #119 — forward path_hashes on ingest (extend existing serializer) |
| meshflow-ui | #304 — show resolved path in UI |
Note: path_hashes already exist on MeshCoreRawPacket / ingest OpenAPI; bot _path_hashes() exists when payload.path is present. Gaps: many DMs have path_len=0; rx_log_data PATH frames are not uploaded today.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 5
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pskillen/meshflow-api
-
enhancement meshtastic-2.8
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pskillen/meshflow-api#459 ·
-
enhancement meshtastic-2.8
Difficulty 3/5 1-2 days Newbie friendliness 35/100
pskillen/meshflow-api#465 ·
-
enhancement meshtastic-2.8
Difficulty 4/5 3-5 days Newbie friendliness 22/100
pskillen/meshflow-api#464 ·
-
enhancement meshtastic-2.8
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pskillen/meshflow-api#463 ·
-
enhancement meshtastic-2.8
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pskillen/meshflow-api#462 ·
All issues in pskillen/meshflow-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/markitdown#2820 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yt-project/yt#5624 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NousResearch/hermes-agent#148376 ·
Maintainers usually reply within 1 day