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

1. 
   helpau commented at 7:49 am on December 16, 2023: none

   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

    0#non-synchronized node
    1.\bitcoin-qt.exe -connect="192.168.88.1:19000" -port=19010 -rpcport=19011 -bind="192.168.1.70"
    2#reference node
    3.\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"
    4
    5### Relevant log output
    6
    7_No response_
    8
    9### How did you obtain Bitcoin Core
   10
   11Other
   12
   13### What version of Bitcoin Core are you using?
   14
   1525.1 and master@b5a271334ca81a6adcb1c608d85c83621a9eae47
   16
   17### Operating system and version
   18
   19Windows 10
   20
   21### Machine specifications
   22
   23C:\Users\melchior>ipconfig
   24
   25Windows IP Configuration
   26
   27
   28Ethernet adapter Ethernet:
   29
   30   Connection-specific DNS Suffix  . : xxxx
   31   IPv6 Address. . . . . . . . . . . : xxxx
   32   Temporary IPv6 Address. . . . . . : xxxx
   33   Link-local IPv6 Address . . . . . : xxxx
   34   IPv4 Address. . . . . . . . . . . : 192.168.1.70
   35   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   36   Default Gateway . . . . . . . . . : xxxx
   37                                       192.168.1.1
   38
   39Ethernet adapter VMware Network Adapter VMnet1:
   40
   41   Connection-specific DNS Suffix  . :
   42   Link-local IPv6 Address . . . . . : xxxx
   43   IPv4 Address. . . . . . . . . . . : 192.168.88.1
   44   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   45   Default Gateway . . . . . . . . . :
   46
   47Ethernet adapter VMware Network Adapter VMnet8:
   48
   49   Connection-specific DNS Suffix  . :
   50   Link-local IPv6 Address . . . . . : xxxx
   51   IPv4 Address. . . . . . . . . . . : 192.168.109.1
   52   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   53   Default Gateway . . . . . . . . . :
   

   debug_reference_node.log debug_not_synced.log

2. 
   helpau commented at 7:51 am on December 16, 2023: none

   Probably related #21747 #22559
3. fanquake added the label Windows on Dec 18, 2023
4. maflcko added the label P2P on Dec 19, 2023
5. maflcko removed the label Windows on Feb 8, 2024
6. 
   maflcko commented at 6:17 pm on February 8, 2024: member

   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.

7. maflcko closed this on Feb 8, 2024

   ---

8. maflcko added the label Questions and Help on Feb 8, 2024
9. 
   helpau commented at 8:46 am on February 11, 2024: none

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

Contributors
helpau maflcko

Labels
P2P Questions and Help