docs: note macOS multicast fallback for D2D discovery#57
Open
nicolas-rabault wants to merge 1 commit into
Open
docs: note macOS multicast fallback for D2D discovery#57nicolas-rabault wants to merge 1 commit into
nicolas-rabault wants to merge 1 commit into
Conversation
Zenoh D2D multicast scouting does not reliably connect two local processes on macOS (loopback), leaving discover() empty and invoke() with no responders. Add a collapsed note documenting the ZENOH_LISTEN / ZENOH_CONNECT TCP-link fallback.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The quick-start says a device started in D2D mode is discovered "instantly, no URLs needed." That relies on Zenoh UDP multicast scouting, which on macOS (loopback) does not reliably connect two local processes —
discover(...)returns empty andinvoke(...)reports no responders.This adds a collapsed
<details>note in step 3 documenting the explicit TCP-link fallback (ZENOH_LISTENon the device,ZENOH_CONNECTon the agent), so the happy path stays uncluttered while users who hit the issue have an answer.Verified locally on macOS: with the TCP link the agent discovers the device and
invokereturns the reading.