Geth continuously attempts to connect to other nodes on the network until it has peers.If you have UPnP enabled on your router or run ethereum on an Internet-facing server, it will also accept connections from other nodes.Geth finds peers through something called the discovery protocol.In the discovery protocol, nodes are gossipping with each other to find out about other nodes on the network.In order to get going initially, geth uses a set of bootstrap nodes whose endpoints are recorded in the source code.To change the bootnodes on startup, use the --bootnodes option and separate the nodes by commas.For example: Sometimes you just can't get connected.The most common reasons are as follows: To start geth without the discovery protocol, you can use the --nodiscover parameter.You only want this is you are running a test node or an experimental test network with fixed nodes.To check how many peers the client is connected to in the interactive console, the net module has two attributes give you info about the number of peers and whether you are a listening node.

To get more information about the connected peers, such as IP address and port number, supported protocols, use the peers() function of the admin object.admin.peers() returns the list of currently connected peers.To check the ports used by geth and also find your enode URI run: Sometimes you might not need to connect to the live public network, you can instead choose to create your own private testnet.This is very useful if you don't need to test external contracts and want just to test the technology, because you won't have to compete with other miners and will easily generate a lot of test ether to play around (replace 12345 with any non-negative number): It is also possible to run geth with a custom genesis block from a JSON file by supplying the --genesis flag.The genesis JSON file should have the following format: Geth also supports a feature called static nodes if you have certain peers you always want to connect to.Static nodes are re-connected on disconnects.

You can configure permanent static nodes by putting something like the following into /static-nodes.json: You can also add static nodes at runtime via the js console using admin.addPeer(): Caveat: Currently the console is lacking support for removing a peer, increasing peercount or adding a non-static peer but not to keep try reconnecting.Ethereum Sign up or log in to customize your list._ Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top up vote 8 down vote favorite 1 I'm running an Ethereum node using geth and it can't find any peers.I've already tried the time sync command suggested on the wiki.My bandwidth is good.go-ethereum synchronization network peers up vote 9 down vote By default, geth uses port 30303 for connection to other nodes.You may need to modify your firewall to allow traffic over this port.You can check your peer count as well as getting a list of peers when attached to the javascript console (geth attach).

instance: Geth/v1.3.2/darwin/go1.5.1 datadir: /Users/home/Library/Ethereum coinbase: 0xd3cda913deb6f67967b99d67acdfa1712c293601 at block: 864339 (Sun, 17 Jan 2016 16:00:07 MST) modules: admin:1.0 db:1.0 debug:1.0 eth:1.0 miner:1.0 net:1.0 personal:1.0 shh:1.0 txpool:1.0 web3:1.0 > net.peerCount 5 > admin.peers [{ caps: ["eth/61", "eth/62"], id: "03743aa20db17dc12d2e355f32b75964653408eaab2c6e0fad7b2600fef49b3c2ec938d436fc48e86582d732d8eb64935edddee7d5c9caf726261add05cf46fe", name: "Geth/v1.2.2/linux/go1.5", network: { localAddress: "10.0.1.48:30303", remoteAddress: "87.106.88.35:35646" }, protocols: { eth: { difficulty: 2283869820384174300, head: "d0d57a2f8fea1c834ce277d031727fecc1baf617b69e4d169f87f7e2d56f04c6", version: 62 } }, ... ] If you have a healthy geth node running somewhere else you can try bootstrapping your peer connection with the admin.addPeer function.gerar bitcoin

The function should be called with an enode address in the format of admin.addNode("enode://@:") where the ip_address and port values come from the remoteAddress portion of the peer information and the id is the big long hex string under the id key for the peer info.For the peer above, this would be: admin.addPeer("enode://03743aa20db17dc12d2e355f32b75964653408eaab2c6e0fad7b2600fef49b3c2ec938d436fc48e86582d732d8eb64935edddee7d5c9caf726261add05cf46fe@87.106.88.35:35646") This can be useful if you somehow lose connection to all of your peers through some non-network based mechanism.bitcoin pool profit calculatorHowever, not having any peers is likely to be a networking issue and manually adding peers will potentially only server as a stop-gap solution at best.bitcoin wiki difficulty

up vote 4 down vote Good you checked the time, but the most common reason for failing to find peers is firewall and network configuration.If a firewall is running, try disabling it.up vote 3 down vote I use this script if my node is acting odd ... obviously you need to modify it to suite your situation... #!/usr/bin/env bash trap "exit" INT LOCALIP=(192.168.10.11) (put your machines IP here) @) echo "Local IP: $LOCALIP" echo "Public IP: $IP" echo "Starting eth" eth --bootstrap --peers 50 --remote 52.16.188.185:30303 --mining off --public-ip $IP --listen-ip $LOCALIP -- listen 30303 Warning - this is not something you should use as a default .. it will burn up internet bandwidth like crazy.bitcoin check hashrateBrowse other questions tagged go-ethereum synchronization network peers or ask your own question.bitcoin ppt template