Skip to content
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.

fix: update multiaddr in webrtc connection to include webRTC #121

Merged
merged 1 commit into from
Apr 11, 2023

Conversation

MarcoPolo
Copy link
Contributor

@MarcoPolo MarcoPolo commented Apr 10, 2023

The multiaddr in the webrtc connection would previously not include the webrtc component. This was confusing since if you wanted to see if a connection was over webrtc, checking the multiaddr alone would be wrong.

This sets the multiaddr on a webrtc connection to be <boostrapMultiaddr>/webrtc/p2p/<peerid>.

Closes #120

@MarcoPolo MarcoPolo requested a review from mxinden April 10, 2023 21:35
@maschad maschad changed the title Fix multiaddr in webrtc connection fix: update multiaddr in webrtc connection to include webRTC Apr 11, 2023
Copy link
Member

@maschad maschad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made suggestion based on the idea that should we decide to change how multiaddrs are formed in the future, I think this would be a more robust validation. Otherwise looks good to me.

@maschad maschad merged commit 6ea04db into main Apr 11, 2023
@maschad maschad deleted the marco/fix-multiaddr branch April 11, 2023 14:26
github-actions bot pushed a commit that referenced this pull request Apr 11, 2023
## [1.1.2](v1.1.1...v1.1.2) (2023-04-11)

### Bug Fixes

* update multiaddr in webrtc connection to include webRTC ([#121](#121)) ([6ea04db](6ea04db))
@github-actions
Copy link

🎉 This PR is included in version 1.1.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

remote addr in peer_transport is wrong after webrtc connection is established
2 participants