Topic: max 8 connections to Bitcoin Network (Read 7772 times)

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.

:-)

unreachable

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? 

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.

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.

Now that we have cleared that up.

Why is it taking so long to sync?

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.

You might want to read the WHOLE threat and you might understand.

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.

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.

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

or

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



Does your ISP force IP changes by disconnect?


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?


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?

If that were the case then there would be thousands of other people having problems, too, but there's not.

The one thing missing from your list is port forwarding, which is what you have to do to get more than 8 connections as has been stated many times in this thread already.  Did you forward the port on your router to the computer running core?

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

- 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

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

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

He just helped you and you insult him    Typical XT troll, all ego no substance

No, I don't necessarily have to assign a static IP just for the sake of trying it out. I just have to make sure, that I forward the port to the currently assigned IP of my device.
I am aware, that the next time it could be different. It actually works now.

I know very well what I am doing, believe me. Unfortunately its you that is harmful to bitcoin.

Yes, I address both of those things. 200 is fairly high in the range of 2-254 that is typically valid for a client device on such a network. However, setting the DHCP server to give a static address to a given machine has been flaky for me across multiple routers.

You can also leave it as dynamic dns and set the renewal time to something really long, then your computer will basically have a static local ip.  Regardless, unless you have hundreds of devices on your local network when your local ip lease is up it usually renews with the same address.

So as has been mentioned, make sure the appropriate ports are open in your firewall and that those ports are forwarded to the local ip of the machine running core and you'll start seeing >8 connections immediately.

No, it's not dependent upon the router.  You can certainly tell your machine to give itself a static IP address.  However, that won't prevent the DHCP server from attempting to assign that same IP address to another machine on the network.  You try to get around that by giving a relatively high value for the last bit.  My solution avoids the problem altogether by telling the DHCP server (i.e. your router) to always assign IP of x.x.x.x to the machine.  No conflicts.

In any case, the point is that the machine needs a static IP address in your home network so that you can properly forward traffic from your router to that machine.

You will need to forward port 8333 and assign a static local ip to your machine.
Don't use XT it is harmful to bitcoin btw.

I have the same problem actually, although I am running bitcoinXT client.
I have forwarded the port to the maschin's IP, when I go to canyouseeme.org it says port is open.
In the windows firewall I have enabled inbound and outbound connections for that program.
Still I can see only 8 connections in the client.