OK, I now add the connect= entrie to both core PCs, and now it works.
Maybe I was to stupid to choose the right one.
Now the Core24H connect to the wallet core PC in the bitcoin.conf.
That works now, and I will report, if that is now quicker or not.
I was maybe thinking the wrong way! Sorry for that.
before:
bitcoin.conf only changed on the walletPC connect=core24HPC
walletpc => core24H
does not work
after:
bicoin.conf changed on core24H connect=walletPC
core24 => walletPC
works fine
I removed the connect entrie on the walletPC, and the connection works still fine, so this must be done
from the sender side, not from the receiving side.
Thank you for the Help!
@LoyceV: I did that, but then the reorginize tooks longer ;( , so that does not help.
Edit: clear things up, for maybe the next one who searched for that
Topic: how to connect two bitcoind to each other (Read 96 times)
But, if that will not help me to speed up the sync, then I can stop right here.
Reason is, I do not use the wallet so often, sometimes once a month, and that take forever
to sync over the internet because of my poor internet speed.
So I was thinking, let use the other 24H core and sync from there.
It won't. It'll actually even synchronize even more slowly. The synchronization is usually either CPU or HDD bound and having a faster internet connection often makes no difference. Connecting to 10 peers simultaneously to download the blocks in parallel would be much more efficient.Reason is, I do not use the wallet so often, sometimes once a month, and that take forever
to sync over the internet because of my poor internet speed.
So I was thinking, let use the other 24H core and sync from there.
If you still want to try to fix it, try running it and add -debug=net as the argument. It will log the more specific network messages and perhaps gives us an idea on why it gets disconnected after the initial connection.
Would it be an option to use for instance rsync to synchronize both directories on a filesystem level (before starting Bitcoin Core)?
I also use bitcoin core . Is there a command, addnode or so that i can help you with, from the configuration of my wallet?
thank you for your offer, but no.
I allready use addnode for the 24H Core PC, and that is not my problem.
thank you for the reply,
yes, my Nodes allow incomming connection.
The conf is loaded,
If I watch Debug/Network connection, the ip of the core24H PC pops up, then went away,
and no connection/transfer is made.
But, if that will not help me to speed up the sync, then I can stop right here.
Reason is, I do not use the wallet so often, sometimes once a month, and that take forever
to sync over the internet because of my poor internet speed.
So I was thinking, let use the other 24H core and sync from there.
yes, my Nodes allow incomming connection.
The conf is loaded,
If I watch Debug/Network connection, the ip of the core24H PC pops up, then went away,
and no connection/transfer is made.
But, if that will not help me to speed up the sync, then I can stop right here.
Reason is, I do not use the wallet so often, sometimes once a month, and that take forever
to sync over the internet because of my poor internet speed.
So I was thinking, let use the other 24H core and sync from there.
Code:
[main]
rpcallowip=192.168.2.0/24
rpcuser=xxxxxx
rpcpassword=xxxxxxx
rpcbind=192.168.2.110
rpcbind=127.0.0.1
rpcport=8332
# Only connect to core24H
connect=192.168.2.234
rpcallowip=192.168.2.0/24
rpcuser=xxxxxx
rpcpassword=xxxxxxx
rpcbind=192.168.2.110
rpcbind=127.0.0.1
rpcport=8332
# Only connect to core24H
connect=192.168.2.234
Connecting solely to a single peer will not speed up your update and it could actually slow it down. If you're talking about synchronization, multiple peers can do it in parallel and if you're talking about normal block relays, then there will be an additional hop through that node before it reaches you. It will not result in any speed increment whatsoever.
For the node that you're attempting to connect to, does it allow incoming connections? You should only use connect=IP address in bitcoin.conf and that should work fine, not addnode. Is the configuration loaded if you check the debug.log?
For the node that you're attempting to connect to, does it allow incoming connections? You should only use connect=IP address in bitcoin.conf and that should work fine, not addnode. Is the configuration loaded if you check the debug.log?
Code:
connect=
Hello all,
maybe a stupid question, elswhere allready answerd, but I could not find it.
I got two PCs running core, one 24H and the other just if needed for my wallet.
I want that the wallet PC only connect to my 24H Core PC dircetly and update the blockchain.
Reason is, I think that speed up my update.
Both PCs are in the same local network.
I tryed it with 'connect' in bitcoin.conf, but the wallet just connect to the internet.
I also tryed 'addnode' but that does also only connect to the internet.
Maybe someone can write down the needed conf entries, to do the wanted connection.
thank you
maybe a stupid question, elswhere allready answerd, but I could not find it.
I got two PCs running core, one 24H and the other just if needed for my wallet.
I want that the wallet PC only connect to my 24H Core PC dircetly and update the blockchain.
Reason is, I think that speed up my update.
Both PCs are in the same local network.
I tryed it with 'connect' in bitcoin.conf, but the wallet just connect to the internet.
I also tryed 'addnode' but that does also only connect to the internet.
Maybe someone can write down the needed conf entries, to do the wanted connection.
thank you
Jump to: