-
Notifications
You must be signed in to change notification settings - Fork 531
discover sends a single repeater discovery request and populates the neighbor list; self is excluded #1718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
liamcottle
merged 4 commits into
meshcore-dev:dev
from
realtag-github:repeater-v1.13-implement-discover
Feb 17, 2026
+56
−0
Merged
discover sends a single repeater discovery request and populates the neighbor list; self is excluded #1718
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e8785dd
discover sends a single repeater discovery request and populates the …
87c78a9
discover.neighbors sends a tagged repeater discovery request and only…
bf9c6cb
Increased the timeout timer to 60 seconds, up from 30 seconds.
0770618
Allow repeater discovery even if repeater mode is disabled on the req…
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should save the 4-byte tag to a member variable, then make sure the response packets match. Otherwise, a bad actor could pollute everyone's neighbors lists with random garbage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly with a timeout too. So if the request tag is reused by some other nearby repeater in the future, it isn't using those responses as well. Probably unlikely since there's 4.2 billion combinations for a
uint32_ttag, but if the member variable is never cleared, it's still another way to pollute, as anyone can listen to those tags as they go over the air.