Bitcoin Forum
December 04, 2016, 06:23:27 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Setting up multiple bitcoin machines behind NAT  (Read 10980 times)
foobar
Newbie
*
Offline Offline

Activity: 1


View Profile
February 16, 2010, 12:35:25 AM
 #1

Hello,

well the title says it all. I want to set up multiple bitcoin machines behind NAT.
For this it reason would be nice, if one could choose an other port than 8333, which I guess would have other nice side effects. Maybe someone uses this port for something else or maybe it isn't possible to set up port forwarding to this port for one reason or another.

Or is there an other way one should go?

Greetings,
foobar
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480875807
Hero Member
*
Offline Offline

Posts: 1480875807

View Profile Personal Message (Offline)

Ignore
1480875807
Reply with quote  #2

1480875807
Report to moderator
satoshi
Founder
Sr. Member
*
Offline Offline

Activity: 364


View Profile
February 16, 2010, 01:34:56 AM
 #2

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=<the IP of the first computer>

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=<IP1> -connect=<IP2>
Xunie
Full Member
***
Offline Offline

Activity: 132



View Profile
April 08, 2010, 08:06:37 PM
 #3

Right now there isn't a port number setting to do that.  It's a feature yet to be implemented.

So, if I somehow I forwarded port router:8333 to bitcoinhost1:8333 and router:8334 to bitcoinhost2:8333, we get undefined behavior?
Because that seems like trivial to me, to keep track of port numbers in any p2p app.

Thank me for this post here: 1PyNKEyqtDFB4HBG8ueDVxdPZfgwC6gAqw
Caffeinism -- a toxic condition caused by excessive ingestion of coffee and other caffeine-containing beverage.
satoshi
Founder
Sr. Member
*
Offline Offline

Activity: 364


View Profile
May 16, 2010, 11:56:03 PM
 #4

At the moment, it always assumes the incoming port is 8333, so it would tell other bitcoin nodes to connect to router:8333 even if you're redirecting from another port number.

I'm not in a big hurry to fix this because I can't think of any benefit to having more than one incoming connection port.  If you're providing one incoming port, then you've done your bit to help the network.  Having two incoming ports to the same person doesn't help redundancy.

If you have many computers, then using the -connect switch on most of them to connect locally makes more sense.
Xunie
Full Member
***
Offline Offline

Activity: 132



View Profile
May 17, 2010, 07:11:08 PM
 #5

Right now there isn't a port number setting to do that.  It's a feature yet to be implemented.

So, if I somehow I forwarded port router:8333 to bitcoinhost1:8333 and router:8334 to bitcoinhost2:8333, we get undefined behavior?
Because that seems like trivial to me, to keep track of port numbers in any p2p app.

Sorry about that, must've been drunk when I wrote that. Huh

Thank me for this post here: 1PyNKEyqtDFB4HBG8ueDVxdPZfgwC6gAqw
Caffeinism -- a toxic condition caused by excessive ingestion of coffee and other caffeine-containing beverage.
SmokeTooMuch
Legendary
*
Offline Offline

Activity: 873


View Profile
October 11, 2010, 09:47:27 PM
 #6

Sorry for digging out this thread, but what if I have two machines running bitcoin behind a NAT, port 8333 forwarded to one of these and both bitcoin clients are generating coins. Is the "unforwarded cleint" even able to generate coins ? Do they get send to the forwarded client ?

Date Registered: 2009-12-10 | I'm using GPG, pm me for my public key. | Bitcoin on Reddit: https://www.reddit.com/r/btc
You like what I'm doing? Why don't you send me a coin: 17Pj8jpUgY6qTaKgiopL5U48zxU4rTrkuB
BitLex
Hero Member
*****
Offline Offline

Activity: 588


View Profile WWW
October 11, 2010, 09:55:30 PM
 #7

they'll both generate,
only difference is the number of connected nodes, it'll be limited to 8 on all un-forwarded clients.

BlueBird
Newbie
*
Offline Offline

Activity: 2


View Profile
February 27, 2011, 03:00:39 AM
 #8

I have two copies running on two computers behind the same router with both systems pointing to the same 8333 port.  Only one computer gets more than 8 connections, but why cant both systems use the same port? 

P.S. If anyone wants to generate a transaction or two they can send .01 to  1C4eBje7vpxuE2deewfiNj8zgoiF4jpV4C    I will send it back at you, provide me your address.  Have fun!

Jim   Smiley
FooDSt4mP
Full Member
***
Offline Offline

Activity: 182


View Profile
February 27, 2011, 05:48:47 AM
 #9

I have two copies running on two computers behind the same router with both systems pointing to the same 8333 port.  Only one computer gets more than 8 connections, but why cant both systems use the same port? 

P.S. If anyone wants to generate a transaction or two they can send .01 to  <a href='bitcoin:?addr=1C4eBje7vpxuE2deewfiNj8zgoiF4jpV4C' id='lnk01C4eBje7vpxuE2deewfiNj8zgoiF4jpV4C'>1C4eBje7vpxuE2deewfiNj8zgoiF4jpV4C</a>    I will send it back at you, provide me your address.  Have fun!

Jim   Smiley

Both systems can't receive messages from the outside network.  The router can only forward the packets coming in on port 8333 to one of the computers.  However, if the two are connected to each other (which you can ensure with the -connect option mentioned above), the messages will be forwarded to the other node by the one that does receive it.

As we slide down the banister of life, this is just another splinter in our ass.
Dominic Sayers
Newbie
*
Offline Offline

Activity: 6



View Profile
May 18, 2011, 12:07:13 PM
 #10

You can only set up your NAT to port-forward to one of the computers.

<snip>

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=<IP1> -connect=<IP2>

I agree with the first statement (you can only forward the port to one computer).

Therefore I do not understand the second statement. How does this achieve redundancy? Only one of the two will receive forwarded traffic. If that one goes down then you've lost the connection (AFAIK).

Am I being dumb?
krepta3000
Member
**
Offline Offline

Activity: 92


View Profile
June 26, 2011, 02:04:40 PM
 #11

You can only set up your NAT to port-forward to one of the computers.

<snip>

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=<IP1> -connect=<IP2>

I agree with the first statement (you can only forward the port to one computer).

Therefore I do not understand the second statement. How does this achieve redundancy? Only one of the two will receive forwarded traffic. If that one goes down then you've lost the connection (AFAIK).

Am I being dumb?

I can think of how it can be redundant, if the second connect command is connecting to a known, usually running, node Outside your own network, a public IP address.  There, redundancy achieved.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!