-
Notifications
You must be signed in to change notification settings - Fork 8
libp2p network issues #97
Comments
(same subnet => work) |
The new update in libp2p: |
nodes on linode can connect to nodes on digital ocean (both are with public ip) |
Another possible p2p lib: https://github.com/anacrolix/torrent |
Another possible p2p lib: https://github.com/pions/webrtc |
based on libp2p/go-libp2p#375 It's possible that we can have nat working by following the example. |
We will firstly try the following setup for the libp2p-relay: https://github.com/libp2p/go-libp2p-examples/blob/master/relay/main.go |
issue with pions/webrtc pions-to-pions example: requiring specifying true ip/port to connect to the peer. https://github.com/pion/webrtc/tree/master/examples/pion-to-pion |
Quick note: WebRTC doesn't require a specific port. It requires you to exchange some data ( An offer and the corresponding answer) in order to set up a connection. It is not specified how to exchange this information. You can copy/paste it, send it over a central server, ... . In the case of the pion to pion example we send this information it over a direct http connection but this is not required. It just makes the example easy to run. |
Thank you so much for the explanation~ I am noob to webrtc, |
After testing #257: Given 1 relay-server, Would like to:
|
We had done switching to WebRTC in #271. |
Version information:
Version: 0.1.0-unstable
Git Commit: b8de7e6
Architecture: amd64
Go Version: go1.10.4
Operating System: darwin
Type:
Enhancement
Description:
Currently we are using libp2p as the underlying p2p mechanism.
However, libp2p is still in the development stage, and it does not guarantee the success of the connections in the various network environment (ex: VPN).
We would like to know the connectivity under different network environment through this issue.
The text was updated successfully, but these errors were encountered: