-
Notifications
You must be signed in to change notification settings - Fork 63
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
Running multiple instances of ckd #8
Comments
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. |
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... |
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). |
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)?
The text was updated successfully, but these errors were encountered: