-
Notifications
You must be signed in to change notification settings - Fork 238
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
[trel] require link-local for peer discovered by mDNS #2709
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2709 +/- ##
===========================================
- Coverage 55.77% 43.75% -12.03%
===========================================
Files 87 110 +23
Lines 6890 13426 +6536
Branches 0 957 +957
===========================================
+ Hits 3843 5874 +2031
- Misses 3047 7242 +4195
- Partials 0 310 +310 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
LGTM. Thanks. 👍
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.
👍
@jwhui There could be a TREL peer using a (legacy?) mDNS stack that doesn't include any link-local address in host records if a non-LL address is available, such as Avahi. Wouldn't this change break TREL with all such "legacy" peers? |
@EskoDijk please check these PRs and issues related to this (which are similar to what you mention above):
I think we should prefer link-local but if there is none then use other addresses. |
@EskoDijk , given the reported issues with existing "legacy" peers, maybe it is good to avoid connecting to such "legacy" peers. |
No description provided.