From a872a5afdaadff6fd5e32feb57a183977ad6a333 Mon Sep 17 00:00:00 2001 From: wakgill <76528604+wakgill@users.noreply.github.com> Date: Mon, 4 Jan 2021 23:58:49 -0600 Subject: [PATCH] Create 55.md --- docs/forum/bitcoin-forum/55.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 docs/forum/bitcoin-forum/55.md diff --git a/docs/forum/bitcoin-forum/55.md b/docs/forum/bitcoin-forum/55.md new file mode 100644 index 0000000..133555b --- /dev/null +++ b/docs/forum/bitcoin-forum/55.md @@ -0,0 +1,27 @@ +--- +layout: forum +title: 'Re: Setting up multiple bitcoin machines behind NAT' +grand_parent: Forum Posts +parent: Bitcoin Forum +nav_order: 55 +date: 2010-02-16 01:34:56 UTC +original: https://bitcointalk.org/index.php?topic=54.msg360#msg360 +--- + +# Re: Setting up multiple bitcoin machines behind NAT + +--- +``` +Re: Setting up multiple bitcoin machines behind NAT +February 16, 2010, 01:34:56 AM + +Right now there isn't a port number setting to do that. It's a feature yet to be implemented. You can only set up your NAT to port-forward to one of the computers. (I said something earlier about NAT port translation, but that wouldn't work, other nodes wouldn't know to connect to that port) + +If you want, as a small optimization, you could run the rest of your computers as: +bitcoin -connect= + +so they get all their network communication from the first computer and don't all connect over the net individually for the same information. This saves bandwidth, although it doesn't use much bandwidth to begin with, so it wouldn't really matter unless you had tons of computers. + +For redundancy in case the first computer goes down, you could have two that connect out and the rest connect to both of them. The first two are run normally, the rest are run like: +bitcoin -connect= -connect= +```