mirror of
https://github.com/MarekZegare4/MeshCore-Solo.git
synced 2026-07-26 14:58:12 +00:00
A discover response often arrives twice — the zero-hop direct copy and a re-flooded copy relayed by another repeater carry different packet hashes, so the mesh duplicate filter passes both. The standalone scan appended the same node twice and app-driven discover forwarded both copies, so one repeater showed up as two. Track (tag, responder pubkey) for a short window in isDupDiscoverResp() and drop the second copy in both the standalone and app-forward paths. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>