|
Title: Port 8333 Post by: BlueBird on February 27, 2011, 03:17:31 AM I have two copies of BitCoin 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 8333 port, my router allowed the assignment for each system?
P.S. If anyone wants to generate a transaction or two they can send to 1C4eBje7vpxuE2deewfiNj8zgoiF4jpV4C I will send it back at you, send your address. Have fun! Jim :) Title: Re: Port 8333 Post by: Tril on February 27, 2011, 04:06:11 AM I have two copies of BitCoin 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 8333 port, my router allowed the assignment for each system? P.S. If anyone wants to generate a transaction or two they can send to 1C4eBje7vpxuE2deewfiNj8zgoiF4jpV4C I will send it back at you, send your address. Have fun! Jim :) This is a limitation of TCP- a connection end point is uniquely defined by an IP and a port number. If you only have one publically-accessible IP address from your ISP, you can only have one bitcoin accept incoming connections on 8333. This shouldn't be a problem, though. I would forward port 8333 to whichever machine you have online more often, then connect the second machine directly to the first machine using -connect=<internal IP of first machine> on the bitcoin command line or in bitcoin.conf. This will be faster, anyway, as you won't be downloading the same block twice from the Internet; each block will go from the Internet to first machine, then to the other machine over the high-speed LAN. Title: Re: Port 8333 Post by: crash893 on March 01, 2011, 10:00:22 PM I dont recommend this but wouldn't UPnP work
|