I need some guidance. I'm trying to connect to the network with Geth, but I never seem to get any peers.
I have enabled port forwarding on my router, and I have checked that the outside world can see Geth running on port 30303 using
http://www.canyouseeme.org/I have build Geth on Debian Jessie x64 from source (commit )
I am running Geth like so:
[email protected]:~/Downloads/go-ethereum/build/bin$ ./geth --vmodule=udp=6,server=6,downloader=6 console
I0522 17:04:55.176755 3224 backend.go:255] Protocol Version: 60, Network Id: 0
I0522 17:04:55.225140 3224 backend.go:265] Blockchain DB Version: 2
I0522 17:04:55.239048 3224 chain_manager.go:247] Last block (#2613) 3d8a8414246615f8fbcc41b7086d83864f9925f1959b1af9edfe1079766346d8 TD=685345077
I0522 17:04:55.528568 3224 cmd.go:137] Starting Geth/v0.9.23-054abe20/linux/go1.3.3
I0522 17:04:55.556155 3224 server.go:209] Starting Server
I0522 17:04:57.172563 3224 udp.go:189] Listening, enode://6bfddf14ca19acdd0c285bd32a8950ea1ae54e2f085b1a583cbbb9d616a9701d8
[email protected]71.176.111.194:30303
I0522 17:04:57.172707 3224 server.go:349] Listening on [::]:30303
I0522 17:04:57.172728 3224 backend.go:479] Server started
I0522 17:04:57.195990 3224 nat.go:95] mapped network port tcp:30303 -> 30303 (ethereum p2p) using UPNP IGDv1-IP1
I0522 17:04:57.212385 3224 udp.go:397] >>> 52.16.188.185:30303 discover.ping
I0522 17:04:57.212477 3224 udp.go:397] >>> 5.1.83.226:30303 discover.ping
I0522 17:04:57.212652 3224 udp.go:397] >>> 54.207.93.166:30303 discover.ping
net
{
listening: true,
getListening: [Function],
peerCount: 0,
getPeerCount: [Function]
}
>
From this point on, nothing happens; I never see any connections, I never get any peers, I never see any printouts. I let it sit like this overnight, nothing.
I tried individually pinging each of those addresses, thinking that they were related to the bootstrap nodes:
[email protected]:~/Downloads$ ping 52.16.188.185
PING 52.16.188.185 (52.16.188.185) 56(84) bytes of data.
^C
--- 52.16.188.185 ping statistics ---
15 packets transmitted, 0 received, 100% packet loss, time 14007ms
[email protected]:~/Downloads$ ping 5.1.83.226
PING 5.1.83.226 (5.1.83.226) 56(84) bytes of data.
64 bytes from 5.1.83.226: icmp_seq=2 ttl=52 time=101 ms
64 bytes from 5.1.83.226: icmp_seq=4 ttl=52 time=100 ms
64 bytes from 5.1.83.226: icmp_seq=5 ttl=52 time=97.7 ms
64 bytes from 5.1.83.226: icmp_seq=6 ttl=52 time=103 ms
64 bytes from 5.1.83.226: icmp_seq=7 ttl=52 time=96.7 ms
64 bytes from 5.1.83.226: icmp_seq=8 ttl=52 time=99.8 ms
64 bytes from 5.1.83.226: icmp_seq=9 ttl=52 time=98.0 ms
64 bytes from 5.1.83.226: icmp_seq=10 ttl=52 time=129 ms
64 bytes from 5.1.83.226: icmp_seq=11 ttl=52 time=98.0 ms
^C
--- 5.1.83.226 ping statistics ---
11 packets transmitted, 9 received, 18% packet loss, time 10006ms
rtt min/avg/max/mdev = 96.782/102.699/129.414/9.625 ms
[email protected]:~/Downloads$ ping 54.207.93.166
PING 54.207.93.166 (54.207.93.166) 56(84) bytes of data.
^C
--- 54.207.93.166 ping statistics ---
15 packets transmitted, 0 received, 100% packet loss, time 14029ms
As you can see, only one of the three respond, but if that is a bootstrap node, it should be enough to get me started, right?
I can't seem to find any enodes to manually add on the command line, is there a list of enodes somewhere, or the enodes of the bootstrap nodes?
Please give me advice on what to try next, I'd really like to be a part of the network and mining!
Thank you for your time.
Comments
Try connecting to some of these and let me know how it goes:
net
{
listening: true,
getListening: [Function],
peerCount: 7,
getPeerCount: [Function]
}
>
Do I need to increase the number of peers, or is this amount fine?
I0523 13:39:42.521238 3224 server.go:512] Handshake with 50.136.197.236:30303 failed: Too many peers
Thanks again!
My win64 rpc-node has only 2-3 current active peers to eth-net.