Bitcoin Forum
May 10, 2024, 04:49:36 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: max 8 connections to Bitcoin Network  (Read 7747 times)
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1520


No I dont escrow anymore.


View Profile WWW
November 19, 2015, 06:32:36 PM
 #21

Still only have 8 connections max.  The core has been running since I first posted In Mid Aug, and it still have more than 1.5 years to go.

- I have a 2wire DSL modem

- Currently computer is connected directly to 2wire

Does that mean: (Internet) <-> Modem <-> Computer with bitcoin core

or

(Internet) <-> Modem <-> Router <-> Computer /w bitcoin core


- Now running Core ver 11.0 (I've upgraded previously a couple times and nothing changed)

- Mapping UPnP and Allow incoming connects selected in Core Network settings

- ISP does NOT provide static IP

Does your ISP force IP changes by disconnect?

- I've tried adding a router inline and nothing changed (tried dedicated port modifications)

Does that mean what Mikestang is asking about, do you mean "port forwarding"? If you are not directly connected to the modem, do you use a fixed IP locally?

- Litecoin Core works fine, updates in minutes.  I'm beginning to think that LTC Core been coded properly and BTC Core has not..

Update times are fine without having more than 8 connections for me. How long do you keep your node running at a time? Is anything configured differently for the two? Different settings on your router or firewall?

Im not really here, its just your imagination.
1715316576
Hero Member
*
Offline Offline

Posts: 1715316576

View Profile Personal Message (Offline)

Ignore
1715316576
Reply with quote  #2

1715316576
Report to moderator
1715316576
Hero Member
*
Offline Offline

Posts: 1715316576

View Profile Personal Message (Offline)

Ignore
1715316576
Reply with quote  #2

1715316576
Report to moderator
In order to achieve higher forum ranks, you need both activity points and merit points.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715316576
Hero Member
*
Offline Offline

Posts: 1715316576

View Profile Personal Message (Offline)

Ignore
1715316576
Reply with quote  #2

1715316576
Report to moderator
1715316576
Hero Member
*
Offline Offline

Posts: 1715316576

View Profile Personal Message (Offline)

Ignore
1715316576
Reply with quote  #2

1715316576
Report to moderator
proline1 (OP)
Newbie
*
Offline Offline

Activity: 17
Merit: 0


View Profile
November 19, 2015, 07:52:09 PM
 #22

Still only have 8 connections max.  The core has been running since I first posted In Mid Aug, and it still have more than 1.5 years to go.

- I have a 2wire DSL modem

- Currently computer is connected directly to 2wire

Does that mean: (Internet) <-> Modem <-> Computer with bitcoin core

or

(Internet) <-> Modem <-> Router <-> Computer /w bitcoin core


- Now running Core ver 11.0 (I've upgraded previously a couple times and nothing changed)

- Mapping UPnP and Allow incoming connects selected in Core Network settings

- ISP does NOT provide static IP

Does your ISP force IP changes by disconnect?

- I've tried adding a router inline and nothing changed (tried dedicated port modifications)

Does that mean what Mikestang is asking about, do you mean "port forwarding"? If you are not directly connected to the modem, do you use a fixed IP locally?

- Litecoin Core works fine, updates in minutes.  I'm beginning to think that LTC Core been coded properly and BTC Core has not..

Update times are fine without having more than 8 connections for me. How long do you keep your node running at a time? Is anything configured differently for the two? Different settings on your router or firewall?


1.
I've tried both ways:
(Internet) <-> Modem <-> Computer with bitcoin core

and

(Internet) <-> Modem <-> Router <-> Computer /w bitcoin core



2. Does your ISP force IP changes by disconnect?
Yes


3. Does that mean what Mikestang is asking about, do you mean "port forwarding"?
Someone suggested that I try a router between the DSL and the computer with core on it and port forward through the router.


4.  If you are not directly connected to the modem, do you use a fixed IP locally?
When I tried a fixed IP locally, there were no connections to the BTC network.


5. How long do you keep your node running at a time?
It has been running 99% of the time since Aug. /15


6. Is anything configured differently for the two? Different settings on your router or firewall?
If only it was that easy.


This whole thing doesn't add up.  LTC works, BTC and Doge do not get above 8 connections.
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
November 19, 2015, 07:56:49 PM
 #23

This whole thing doesn't add up.  LTC works, BTC and Doge do not get above 8 connections.
Why do you care so much? 8 Connections means that you probably have 8 outgoing connections which is the maximum number of outgoing connections you can have. If people don't connect to your node, then you won't have any incoming connections. I myself, with Bitcoin Core, rarely have more than 8 connections even though I have upnp enabled and have port forwarding enabled.

proline1 (OP)
Newbie
*
Offline Offline

Activity: 17
Merit: 0


View Profile
November 19, 2015, 08:08:55 PM
 #24

This whole thing doesn't add up.  LTC works, BTC and Doge do not get above 8 connections.
Why do you care so much? 8 Connections means that you probably have 8 outgoing connections which is the maximum number of outgoing connections you can have. If people don't connect to your node, then you won't have any incoming connections. I myself, with Bitcoin Core, rarely have more than 8 connections even though I have upnp enabled and have port forwarding enabled.

You might want to read the WHOLE threat and you might understand.
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
November 19, 2015, 08:13:41 PM
 #25

This whole thing doesn't add up.  LTC works, BTC and Doge do not get above 8 connections.
Why do you care so much? 8 Connections means that you probably have 8 outgoing connections which is the maximum number of outgoing connections you can have. If people don't connect to your node, then you won't have any incoming connections. I myself, with Bitcoin Core, rarely have more than 8 connections even though I have upnp enabled and have port forwarding enabled.

You might want to read the WHOLE threat and you might understand.
I do understand. You think that not having more than 8 connections will make the syncing slow. BUT Bitcoin Core syncs through ONLY ONE NODE. It doesn't matter how many connections you have. Bitcoin Core will CHOOSE ONE OF THEM and do ALL of the initial syncing through that node. It doesn't matter how many you are connected to, ONLY ONE is used for the initial sync. After that, then it will receive blocks as its nodes relay them.

proline1 (OP)
Newbie
*
Offline Offline

Activity: 17
Merit: 0


View Profile
November 19, 2015, 11:21:49 PM
 #26

This whole thing doesn't add up.  LTC works, BTC and Doge do not get above 8 connections.
Why do you care so much? 8 Connections means that you probably have 8 outgoing connections which is the maximum number of outgoing connections you can have. If people don't connect to your node, then you won't have any incoming connections. I myself, with Bitcoin Core, rarely have more than 8 connections even though I have upnp enabled and have port forwarding enabled.

You might want to read the WHOLE threat and you might understand.
I do understand. You think that not having more than 8 connections will make the syncing slow. BUT Bitcoin Core syncs through ONLY ONE NODE. It doesn't matter how many connections you have. Bitcoin Core will CHOOSE ONE OF THEM and do ALL of the initial syncing through that node. It doesn't matter how many you are connected to, ONLY ONE is used for the initial sync. After that, then it will receive blocks as its nodes relay them.

Now that we have cleared that up.

Why is it taking so long to sync?Huh
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
November 20, 2015, 01:42:32 AM
 #27

Why is it taking so long to sync?Huh
Your internet speed and the internet speed of the node that Bitcoin core happens to choose as its download peer is a large factor of the speed. Also part of it is the speed of your CPU and how much RAM you have in order to quickly process the data that you receive.

shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1520


No I dont escrow anymore.


View Profile WWW
November 20, 2015, 12:03:38 PM
 #28

Why is it taking so long to sync?Huh
Your internet speed and the internet speed of the node that Bitcoin core happens to choose as its download peer is a large factor of the speed. Also part of it is the speed of your CPU and how much RAM you have in order to quickly process the data that you receive.

Core synchs from all (capable) nodes since 0.10. A single node is usually faster enough to synch a constantly running node within a few minutes though. Maybe 3 full nodes on the same machine put too much strain on the connections so it cant hold more than a certain number and since doge and LTC have less traffic (less TX/block size)[1] the BTC connections are dropped first.


[1] this is just an assumption and might be completly wrong.

Im not really here, its just your imagination.
cr1776
Legendary
*
Offline Offline

Activity: 4032
Merit: 1301


View Profile
November 20, 2015, 02:13:29 PM
 #29

This whole thing doesn't add up.  LTC works, BTC and Doge do not get above 8 connections.
Why do you care so much? 8 Connections means that you probably have 8 outgoing connections which is the maximum number of outgoing connections you can have. If people don't connect to your node, then you won't have any incoming connections. I myself, with Bitcoin Core, rarely have more than 8 connections even though I have upnp enabled and have port forwarding enabled.

You might want to read the WHOLE threat and you might understand.
I do understand. You think that not having more than 8 connections will make the syncing slow. BUT Bitcoin Core syncs through ONLY ONE NODE. It doesn't matter how many connections you have. Bitcoin Core will CHOOSE ONE OF THEM and do ALL of the initial syncing through that node. It doesn't matter how many you are connected to, ONLY ONE is used for the initial sync. After that, then it will receive blocks as its nodes relay them.

With headers first, Bitcoin Core can sync through multiple nodes (0.10.0 and up).

As a test, if you go here:
https://bitnodes.21.co

where it says "Join the Network" and enter your IP, does it show that you are accepting connections from other nodes?

Are you unreachable or reachable? 
proline1 (OP)
Newbie
*
Offline Offline

Activity: 17
Merit: 0


View Profile
November 20, 2015, 04:01:15 PM
 #30

This whole thing doesn't add up.  LTC works, BTC and Doge do not get above 8 connections.
Why do you care so much? 8 Connections means that you probably have 8 outgoing connections which is the maximum number of outgoing connections you can have. If people don't connect to your node, then you won't have any incoming connections. I myself, with Bitcoin Core, rarely have more than 8 connections even though I have upnp enabled and have port forwarding enabled.

You might want to read the WHOLE threat and you might understand.
I do understand. You think that not having more than 8 connections will make the syncing slow. BUT Bitcoin Core syncs through ONLY ONE NODE. It doesn't matter how many connections you have. Bitcoin Core will CHOOSE ONE OF THEM and do ALL of the initial syncing through that node. It doesn't matter how many you are connected to, ONLY ONE is used for the initial sync. After that, then it will receive blocks as its nodes relay them.

With headers first, Bitcoin Core can sync through multiple nodes (0.10.0 and up).

As a test, if you go here:
https://bitnodes.21.co

where it says "Join the Network" and enter your IP, does it show that you are accepting connections from other nodes?

Are you unreachable or reachable? 



unreachable

cr1776
Legendary
*
Offline Offline

Activity: 4032
Merit: 1301


View Profile
November 20, 2015, 05:18:04 PM
 #31

...

unreachable


Are you sure that port forwarding is working properly?  e.g. forwarding port 8333 from the router to port 8333 on your internal machine? 

Can you connect to the admin control panel on the 2wire modem?  Many of the 2wires have a firewall built in which could be (and probably is) blocking that port.  (It's login page should be something like one of these.  If you know your internal IP address of the computer, that will give a hint: 10.0.0.138, 192.168.0.1,192.168.1.0 ,192.168.1.1, 192.168.1.254, gateway.2wire.net ,http://gateway.2Wire.net  )

You'll need the username and password for the router.  If you haven't changed them, it could be both blank for both or "admin" and "2wire" (or "Wireless")...varies.

Then in there, you'd need to look for the port forwarding section and update that.  If you put a router in between the modem and the computer, you'd need to set it up there too.

You'd want the 2wire (and router if you have on there too) to say something like allow all incoming connections from the WAN on port 8333 to go to port 8333 on the internal IP address (e.g. something like 192.168.1.55 -- whatever the local IP of the bitcoin server is, you'd want to set that to something static and not use DHCP to set the IP for that machine.  And assuming you are still on 8333.)



Once you check that, if you use a tool like this:
http://www.yougetsignal.com/tools/open-ports/

It should show that it is open if forward is working so that it connects to your local computer.  Bitnodes gives similar info, but will check not just the port.  If the port gets opened, then bitnodes should show it working too.

If you have another machine on your local network, can you check and see from that machine if port 8333 is accessible?  I bet it is, but if not, then it could be the firewall on the machine vs on the modem.

:-)
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!