-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
fix(dns): skip probe for NetBird overlay addresses at engine startup #5625
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
Closed
sbeaudry-qms
wants to merge
3
commits into
netbirdio:main
from
sbeaudry-qms:fix/dns-skip-overlay-probe
+324
−20
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
434ad13
fix(dns): skip probe for NetBird overlay addresses at engine startup
sbeaudry-qms dc9aaa6
fix(dns): Addressing CodeRabbit suggestion. Remove mutex around wg.W…
sbeaudry-qms 931dbae
fix(dns): Following CodeRabbit's suggestion: Using probedAny flag ins…
sbeaudry-qms 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
Some comments aren't visible on the classic Files Changed page.
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
Oops, something went wrong.
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.
Do not treat every
100.64.0.0/10resolver as a NetBird peer.100.64.0.0/10is shared CGNAT space, not NetBird-exclusive. With the current check, any resolver in that block is skipped, soprobedAnystays false and the group never disables or emits the startup warning even if that address is just a local/ISP resolver that's actually down.DefaultServer.ProbeAvailability()and engine startup both rely on this path to disable groups when no real upstream responds.At minimum, only skip when you can positively map the address to a NetBird peer/route; otherwise keep the normal probe behavior. Please also add a regression case for a non-NetBird
100.64/10nameserver.💡 Safer gating direction
Also applies to: 303-310, 339-343
🤖 Prompt for AI Agents