Title: Multiple Machines Post by: bbking2010 on December 17, 2010, 10:25:58 PM I am sure this has been covered, but I can run the client on multiple machines on the same network, correct? each has it's own "bitcoin address".
Title: Re: Multiple Machines Post by: kiba on December 17, 2010, 10:30:37 PM That's correct. Each bitcoin client have their own wallet.
Title: Re: Multiple Machines Post by: bbking2010 on December 18, 2010, 07:33:02 PM So what's all the stuff about NAT translations, etc. Brief summary.
Title: Re: Multiple Machines Post by: Gavin Andresen on December 18, 2010, 08:19:02 PM So what's all the stuff about NAT translations, etc. Brief summary. Short answer: you don't have to worry about it.Long answer: if you want to worry about being as network-bandwidth-efficient as possible, run one node normally, and run all the rest with the -noirc -connect=IP.AD.DR.SS flags so they connect only to the one 'master' node. All the network traffic will then go through the master node. Title: Re: Multiple Machines Post by: x86Daddy on December 22, 2010, 07:55:13 PM Additional question on this matter: if I have multiple of my own machines I'd like to use to generate coins, it looks like there's a few ways to go...
Title: Re: Multiple Machines Post by: neptop on December 24, 2010, 07:34:19 PM Maybe you also want to use -addnode option, which results in a non-exclusive connection, so it still does connect to others. I use this option, so a connections are established faster when there is at least one other node available in your network.
|