Topic: "zombie" nodes (Read 1634 times)
nice input, thanks, will try it out!
I didnt expect to need this list any more.
I assume your router is forwarding a port, this can only be done to a single machine, thats normal. Shut down one of the nodes and get one synced, the other can sync via lan once the first is done. You can force a connection to a certain node by starting bitcoin core/qt with
-connect, e.g. for Windows7 (8.1 might be slightly different) you open run (Win + R) and enter (replace IP and path as needed):
You can use this command to make sure your LAN node #1 (e.g. Debian) is connected to your LAN #2 (e.g. Win) and you can use this command to make sure that you get connections to sync proberly.
Here is a list of IPs I collected for slow syncing nodes before 0.10.0, apparently its still useful. Since 0.10.0 can use multiple nodes to synch you can connect to all of the, just seperate the IPs by commas, e.g.
Full list:
I assume your router is forwarding a port, this can only be done to a single machine, thats normal. Shut down one of the nodes and get one synced, the other can sync via lan once the first is done. You can force a connection to a certain node by starting bitcoin core/qt with
-connect, e.g. for Windows7 (8.1 might be slightly different) you open run (Win + R) and enter (replace IP and path as needed):
Code:
c:\Program Files\Bitcoin\bitcoin-qt.exe -connect=10.10.1.11
You can use this command to make sure your LAN node #1 (e.g. Debian) is connected to your LAN #2 (e.g. Win) and you can use this command to make sure that you get connections to sync proberly.
Here is a list of IPs I collected for slow syncing nodes before 0.10.0, apparently its still useful. Since 0.10.0 can use multiple nodes to synch you can connect to all of the, just seperate the IPs by commas, e.g.
Code:
c:\Program Files\Bitcoin\bitcoin-qt.exe -connect=10.10.1.11,185.45.192.129,46.4.65.207
Full list:
Code:
last updated 2015.02.14
---------------------------------------------------------------------------------------------------
IP - location - owner[1] - speed - info/stats page[2] - testnet
---------------------------------------------------------------------------------------------------
185.45.192.129 - Amsterdam, NL, EU - anon - 1000 mbit/s - /node.php[3] - yes
84.200.34.113 - Freinsheim, DE, EU - Newar - 1000 mbit/s - yes - no
46.4.65.207 - Falkenstein, DE, EU - zvs - 500 mbit/s - no - no
94.23.146.127 - NL, EU - anon - 200 mbit/s - /status - no
213.165.91.169 - Germany, EU - shorena - 100 mbit/s - yes - no
191.236.50.217 - Virgina, US - grue - 100 mbit/s - no - no
23.92.214.123 [5] - Rochester, USA - Newar - 100 mbit/s - no - no
---------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[4] be down!!
---------------------------------------------------------------------------------------------------
-
---------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
[4] or reached max connections at the time of testing. Nodes failing 3 tests in a row will
be removed (Number of failed test is noted behind the IP)
[5] Runs BTCD (alternative full node implementation with GO)
hi.
I recently upgraded to Bitcoin Core 0.10.0.
I am running it on two computers. one is debian wheezy x64 and the other windows 8.1 pro x64
according to https://getaddr.bitnodes.io/, i am on the network. And I know the network is kinda slow but: for now a week my blockchain ETA hasnt moved. Windows says 39 weeks to go (and synchronizing with network), and debian says 2 years 11 weeks (and no block sources available)
they both show some traffic activity but it is reaaaally low. Like 10 megas sent and 139 megas received on debian.
UPnP on my nobel prize for shittiest router firmware(belgacom BBox 3, look it up, if you want nightmares) ever opened 8333 for windows, and wont let me open the same port on debian.
Both computers are 24/7.
Any ideas?
Thanks in advance.
I recently upgraded to Bitcoin Core 0.10.0.
I am running it on two computers. one is debian wheezy x64 and the other windows 8.1 pro x64
according to https://getaddr.bitnodes.io/, i am on the network. And I know the network is kinda slow but: for now a week my blockchain ETA hasnt moved. Windows says 39 weeks to go (and synchronizing with network), and debian says 2 years 11 weeks (and no block sources available)
they both show some traffic activity but it is reaaaally low. Like 10 megas sent and 139 megas received on debian.
UPnP on my nobel prize for shittiest router firmware(belgacom BBox 3, look it up, if you want nightmares) ever opened 8333 for windows, and wont let me open the same port on debian.
Both computers are 24/7.
Any ideas?
Thanks in advance.
Jump to: