Topic: block source (Read 1030 times)
It's definitely working now and local. Thank you.
Thank you!
Turns out I was blocking 8883 and 6667 on the machine that is up to date. Fixed that and the incoming rate shot up but I still don't see the other host in getpeerinfo so I'm not sure if maybe I got lucky and it found another peer very close but outside my lan.
Turns out I was blocking 8883 and 6667 on the machine that is up to date. Fixed that and the incoming rate shot up but I still don't see the other host in getpeerinfo so I'm not sure if maybe I got lucky and it found another peer very close but outside my lan.
create file ~/.bitcoin/bitcoin.conf
Code:
rpcuser=user
rpcpassword=your long password
server=1
daemon=1
rpcallowip=127.0.0.1
addnode=192.168.0.103
rpcpassword=your long password
server=1
daemon=1
rpcallowip=127.0.0.1
addnode=192.168.0.103
Well it's not showing up in getpeerinfo so i don't know...
Tried this in the debug console -
addnode 192.168.0.103 add
Is that correct?
Guess I'll quickly find out...
addnode 192.168.0.103 add
Is that correct?
Guess I'll quickly find out...
Setting up bitcoin-qt on a new laptop.
Need to tell it to use my desktop as a block source so it goes faster.
There use to be a ~/.bitcoin/bitcoin.conf file where I could do that, but I don't see that file.
What is the current method for telling it to use the "caught up" client I have running on another machine on my gigabit wired LAN ??
Looking via google seems to all point to old documentation for 0.8 client - which used ~/.bitcoin/bitcoin.conf
Need to tell it to use my desktop as a block source so it goes faster.
There use to be a ~/.bitcoin/bitcoin.conf file where I could do that, but I don't see that file.
What is the current method for telling it to use the "caught up" client I have running on another machine on my gigabit wired LAN ??
Looking via google seems to all point to old documentation for 0.8 client - which used ~/.bitcoin/bitcoin.conf
Jump to: