Issue Details

Number

5299

Title

Initial connection management

Description

Pointing two peers at each other via the "addnode" / "connect" args in bitcoin.conf on init results in multiple (3 as observed in getpeerinfo on regtest) connections (on different ports) and, hence, chatty traffic (say inventory exchange) when running off of the current master. Connecting via the "addnode" RPC call after a successful initialization of both peers corrects this.

URL

https://github.com/bitcoin/bitcoin/issue/5299

Closed by

#27804

Notes We are closer to diagnosing the root cause, but no fix proposed. Found a fix, just by deduplicating the added node vectors.

Attention of

Kill Factor (1-10)

Save

Back to List