search

decred / dcrd

Decred daemon in Go (golang).
https://decred.org
ISC License
739 stars 292 forks source link

Why am I not seeing outgoing connections? #621

Closed taoeffect closed 7 years ago

taoeffect commented 7 years ago

dcrctl getpeerinfo and dcrctl getconnectioncount show 8 outgoing connections, but my network monitoring tools show dcrd connected to only mainnet-seed.decred.netpurgatory.com, mainnet.decredseed.org, one other server (an IP address), and the DNS server.

This would make sense if the connections were UDP based and not TCP based. But if they're TCP based, then that would probably indicate a bug?

jcvernaleo commented 7 years ago

Are you on mainnet or testnet?

What os are you using and what are you using to monitor the network connections. When I try on linux (with a mainnet dcrd) I get:

jcv@triforce ~ $ lsof | grep dcrd | grep TCP
dcrd      18391                    jcv   19u     IPv4             426585       0t0        TCP triforce:50376->104-159-251-219.static.sgnw.mi.charter.com:19108 (ESTABLISHED)
dcrd      19161                    jcv   31u     IPv4             345421       0t0        TCP triforce:44748->61.244.102.46.static.intovps.com:9108 (ESTABLISHED)
dcrd      19161                    jcv   32u     IPv4             342832       0t0        TCP triforce:52472->155.94.137.8.static.quadranet.com:9108 (ESTABLISHED)
dcrd      19161                    jcv   33u     IPv4             342833       0t0        TCP triforce:38144->backend3.dcrstakes.com:9108 (ESTABLISHED)
dcrd      19161                    jcv   35u     IPv4             348353       0t0        TCP triforce:54476->c-67-169-35-31.hsd1.ca.comcast.net:9108 (ESTABLISHED)
dcrd      19161                    jcv   37u     IPv4             342834       0t0        TCP triforce:45148->188.26.197.104.bc.googleusercontent.com:9108 (ESTABLISHED)
dcrd      19161 19162              jcv   27u     IPv4             413785       0t0        TCP triforce:44622->therapysloths.com:9108 (ESTABLISHED)
dcrd      19161 19162              jcv   31u     IPv4             345421       0t0        TCP triforce:44748->61.244.102.46.static.intovps.com:9108 (ESTABLISHED)
dcrd      19161 19162              jcv   32u     IPv4             342832       0t0        TCP triforce:52472->155.94.137.8.static.quadranet.com:9108 (ESTABLISHED)
dcrd      19161 19162              jcv   33u     IPv4             342833       0t0        TCP triforce:38144->backend3.dcrstakes.com:9108 (ESTABLISHED)
dcrd      19161 19162              jcv   35u     IPv4             348353       0t0        TCP triforce:54476->c-67-169-35-31.hsd1.ca.comcast.net:9108 (ESTABLISHED)
dcrd      19161 19162              jcv   37u     IPv4             342834       0t0        TCP triforce:45148->188.26.197.104.bc.googleusercontent.com:9108 (ESTABLISHED)
dcrd      19161 19163              jcv   27u     IPv4             413785       0t0        TCP triforce:44622->therapysloths.com:9108 (ESTABLISHED)
dcrd      19161 19163              jcv   31u     IPv4             345421       0t0        TCP triforce:44748->61.244.102.46.static.intovps.com:9108 (ESTABLISHED)

plus a lot more that I'm leaving out so this is at least a little readable.

taoeffect commented 7 years ago

I'm on OS X and was using Little Snitch's network monitor. When testing out a different blockchain I would see in the network monitor the node connecting to tons of various IPs. Not so with dcrd, the monitor only showed 4 outgoing connections, and only one of them (the mainnet) was shown as having activity.

jcvernaleo commented 7 years ago

There is a PR with significant improvements to the peer handling going in very soon. You might want to check that out #631

davecgh commented 7 years ago

The aforementioned PR has been merged. That said, please keep in mind that dcrd currently only syncs from a single peer. This is something that will be improved in the future, but that very likely explains while you only saw activity on one peer.

dajohi commented 7 years ago

@taoeffect is this still an issue?

dajohi commented 7 years ago

Please reopen if still an issue.