feat: Testing with external peers #227
Open
+23
−3
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.
Description
This PR updates the js-libp2p-example-webrtc-private-to-private example to support and document testing peer-to-peer connectivity in realistic network conditions, such as when peers are:
Running on separate machines
Behind NATs or VPNs
Without public IPs
Key changes include:
Binding the development server to all interfaces (0.0.0.0), so the example is reachable from external machines.
Documentation for exposing port 5173, including guidance for environments like AWS EC2.
Recommendation to use a static public IP for the signaling server host to avoid connectivity issues.
Connection type indicator: The UI now displays whether a peer connection is established Directly or via a Relay.
Fixes #226.
Notes & open questions
Change checklist