Skip to content
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

Cannot connect to nodes over the internet behind NAT. Throwing random errors. #213

Closed
vaibhav6233m opened this issue Jul 2, 2018 · 1 comment
Labels
status/ready Ready to be worked

Comments

@vaibhav6233m
Copy link

  • Version: b7f67f2
  • Platform: Linux x64
  • Subsystem: Ubuntu

Type: Bug

Severity: High

Description:

I want to use the libp2p functionality for building a p2p network where the nodes are sharing some contentID and other nodes can discover these nodes using the FindContentProvider functionality in DHT.

What actually happening is that the nodes are not getting connected to each other behind NAT and also From EC2 servers where the incoming traffic is disabled, but the ports of bootstrap node are open. I am getting the list of other nodes in the network (Some random nodes, because I did enable some libp2p bootstrap nodes for sometime and it must have cached these details inside the peerBook) but not the nodes I am creating manually.

Also after some amount of time I am getting these errors at random.

See SS:

screenshot from 2018-07-02 16-37-36

screenshot from 2018-07-02 16-38-07

screenshot from 2018-07-02 16-39-40

Steps to reproduce the error:

Clone, npm i and run the dht-contentrouting.js
dht-contentrouting.js

Bootstrap Node

@achingbrain
Copy link
Member

Closing due to staleness. Please try again with the most recent version, if it's still a problem open a new issue with a reproduction case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

3 participants