-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remote example #203
Comments
@developpsoft it should work out of the box. Did you try it? |
Yes, maybe I am missing something?
The examples works fine but I would be interested in making them work in
"P2P" not just local.
Le 19 août 2017 7:40 PM, "David Dias" <notifications@github.com> a écrit :
… @developpsoft <https://github.com/developpsoft> it should work out of the
box. Did you try it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#203 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKMEJirJ1kmV-yCzKhPIyuvWCE_L0gwQks5sZx4jgaJpZM4OKRQ7>
.
|
So, they generally "just work" on computers in the same network. Unfortunately, if both machines are behind NATs, they won't be able to connect to each other at the moment. We're currently working on NAT traversal (specifically, relays) but they're a work in progress. If you want to try out relays, checkout the examples in https://github.com/libp2p/go-libp2p-circuit-progs. Currently, they require manually specifying the relay (and the relay can't be behind a NAT) but @vyzo is working working on that. |
Oh ok I see. Thanks for explaining 😄 |
I think I can close that then |
Hi, I can see all the examples in this repo are working with local addresses, any ways to make them work with remote ones? I mean, running them on two separated networks.
The text was updated successfully, but these errors were encountered: