Select OTA Provider port randomly #885
Merged
Conversation
This file contains 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
Instead of using a fixed port for OTA Provider, pass 0 to let the Matter SDK/bind() syscall select a random port. This allows multiple OTA Providers to run on the same host without port conflicts. Fixes: home-assistant/core#125130
|
Pretty sure I had dynamic ports used at one point, but I think I was unsure if issues we've seen with Apple Thread border router were maybe related to port selection. Anyhow, initial investigation point more towards mDNS issue on that front. |
marcelveldt
approved these changes
Sep 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Instead of using a fixed port for OTA Provider, pass 0 to let the Matter SDK/bind() syscall select a random port. This allows multiple OTA Providers to run on the same host without port conflicts.
Fixes: home-assistant/core#125130