Repository navigation
Running multiple instances of ckd #8
Description
At the moment it looks like I'm able to run only one instance of ckd on my network in connected mode.
When I run the second instance (not on the same machine as the first one of course) this second instance can't connect to peers.
Is this intentional (maybe as they are both sharing the same external IP)? Even when one of them is not mining (has miner=false in config)?
Activity
metalicjames commentedon Mar 1, 2018
Right now nodes use the external IP addresses of incoming peers to determine duplicate connections. I need to find a better method of detecting this.
alkavan commentedon Oct 10, 2018
Maybe adding some machine specific identification to the external IP and hashing it all, check by hashes? I might be able to assist (code) with this issue...
delbonis commentedon Oct 10, 2018
As a hack, you could use docker-compose and have only one node talk to the outside world, and all of the other nodes talk to that one node (using it like a bridge).