DHT peer discovery and routing not working with a private network

vgiotsas · June 6, 2020, 11:24am

Hello everyone,

I’m trying to create a private network that uses the KadDHT so that the private nodes can discover each other. My code is in the Gist below, I’ve run it with js-ipfs@0.45.0.

gist.github.com

https://gist.github.com/vgiotsas/573aa050a481db6a49f670d4ca32fb5f

ipfs-private-net.js

"use strict";

const IPFS = require('ipfs')
const Protector = require('libp2p/src/pnet')
const TCP = require('libp2p-tcp')
const KadDHT = require('libp2p-kad-dht')
const MPLEX = require('libp2p-mplex')
const SECIO = require('libp2p-secio')
const { NOISE } = require('libp2p-noise')
const Bootstrap = require('libp2p-bootstrap')

This file has been truncated. show original

In this code I’m testing with two nodes (apart from the bootstrap node). In
line 93 I first explicitely connect the two nodes together and then I look up the DHT for the same node to find the other node to which it just connected. While the connection is successful, dht.findpeer fails with Error: Peer lookup failed.

The bootstrap server runs using the go-ipfs cli and nodes are successfully connecting to it, when I run ipfs swarm peers I can see the nodejs peers in the output. Also, when I run additional nodes from the command line in the same private network, these nodes can successfully find the nodejs nodes connected to the bootstrap node. So the problem appears to be with the js-ipfs nodes only.

I tried to explore the problem more so I checked if js-ipfs nodes can use the DHT successfully when they’re connected in the public network, and sure enough they can discover and connect automatically to other nodes. So it seems that the DHT functionality isn’t working only for private networks.

Has anyone created private networks that utilize the DHT successfully?

mike7c2 · June 6, 2020, 11:46am

I’ve been trying to configure a pnet for development and run into a similar issue, I suspect I have something configured incorrectly as I think I have all the relays setup yet the js-ipfs nodes will not automatically use the bootstrap node as a relay.

To work around it for now I manually instruct the js-ipfs nodes to connect via a bootstrap node, so instead of:

ipfs.swarm.connect("/ipfs/Qmtarget")

do

ipfs.swarm.connect("/ipfs/QmRelay/p2p-circuit/ipfs/QmTarget")

This seems to work reliably for me but it is frustrating they don’t use relays automatically, hopefully someone has a better answer!

vgiotsas · June 6, 2020, 12:07pm

Thanks @mike7c2

I wonder if it’s a relay issue in my case since the two nodes can connect directly with each other, when the connection is created explicitely.

Topic		Replies	Views
How to set up my own bootstrap nodes to enable discovery and connection between nodes with public IP and nodes on a local network? Help dht	17	744	September 16, 2023
IPFS Private Network local peers discovery issue Help go-ipfs	2	387	December 28, 2022
0.4.23 vs 0.6.0 peer connection management Help go-ipfs	2	299	September 21, 2020
Need Help, while creating private ipfs network, nodes are unable to automatically discover each other Help go-ipfs	7	1024	June 14, 2019
Dht.findpeer fail when finding a node behind nat Help go-ipfs	3	517	July 7, 2021

DHT peer discovery and routing not working with a private network

Related Topics