Skip to content

Conversation

@sipa
Copy link
Member

@sipa sipa commented Feb 11, 2012

In preparation of IPv6 support: prevent double connections to the same node.

Not urgent.

@jgarzik
Copy link
Contributor

jgarzik commented Feb 11, 2012

ACK

@luke-jr
Copy link
Member

luke-jr commented Feb 17, 2012

Does this break connecting to multiple nodes on different ports? eg, multiple local bitcoinds

@sipa
Copy link
Member Author

sipa commented Feb 17, 2012

All nodes have a self-generated unique 64-bit identifier. This patch will prevent two connections to a partner with the same identifier.

Running two nodes on one system and connecting to both should not be a problem.

@luke-jr
Copy link
Member

luke-jr commented Feb 20, 2012

Per https://en.bitcoin.it/wiki/Protocol_specification#version the nonce is unique for every version message, so this would imply a protocol change making it static per client...

@sipa
Copy link
Member Author

sipa commented Feb 21, 2012

Nice catch; that makes this problem somewhat harder to solve. Closing for now...

@sipa sipa closed this Feb 21, 2012
destenson pushed a commit to destenson/bitcoin--bitcoin that referenced this pull request Jun 26, 2016
If we want to be compatible to 12.0 on network layer we need them back in ppszTypeName[] to keep inv type consistent (allNetMessageTypes[] should not have them, we shouldn't accept non-implmented messages)
ptschip pushed a commit to ptschip/bitcoin that referenced this pull request Nov 4, 2017
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants