Connection between nodes on the PC interfaces doesn't work #29097

Is there an existing issue for this?

• I have searched the existing issues

Current behaviour

The nodes haven't started synchronising, User-Agent are doubled

Expected behaviour

The nodes have started synchronising, User-Agents are different

Steps to reproduce

Preconditions: Bitcoin Core 25.1(reference node, partially synchronized) and self-compiled Bitcoin Core(from master, not synchronized)

1. Select IP for nodes(i used IP from different interface but from one PC)
2. Launch both nodes

#non-synchronized node
.\bitcoin-qt.exe -connect="192.168.88.1:19000" -port=19010 -rpcport=19011 -bind="192.168.1.70"
#reference node
.\bitcoin-qt.exe -datadir="C:\Users\melchior\AppData\Roaming\Bitcoin_ref" -connect="192.168.1.70:19010" -port=19000 -rpcport=19001 -bind="192.168.88.1"

### Relevant log output

_No response_

### How did you obtain Bitcoin Core

Other

### What version of Bitcoin Core are you using?

25.1 and master@b5a271334ca81a6adcb1c608d85c83621a9eae47

### Operating system and version

Windows 10

### Machine specifications

C:\Users\melchior>ipconfig

Windows IP Configuration


Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : xxxx
   IPv6 Address. . . . . . . . . . . : xxxx
   Temporary IPv6 Address. . . . . . : xxxx
   Link-local IPv6 Address . . . . . : xxxx
   IPv4 Address. . . . . . . . . . . : 192.168.1.70
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : xxxx
                                       192.168.1.1

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : xxxx
   IPv4 Address. . . . . . . . . . . : 192.168.88.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : xxxx
   IPv4 Address. . . . . . . . . . . : 192.168.109.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

debug_reference_node.log debug_not_synced.log

Probably related #21747 #22559

On the server node you'll have to fully sync the chain, or disable -minimumchainwork=<hex> on the client.

Let us know if this is still a problem after you tried at least one of the suggested solutions.

I tried again with a fully synchronised node, did not reproduce. I think minimumchainwork will similarly solve the problem. Thanks for the reply.