Browse Source

Merge pull request #11 from JeremyRand/multiple-peers

Receive multiple peers per crawl
master
Lyndsay Roger 3 years ago committed by GitHub
parent
commit
6318ce59b5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 16
      crawler.go

16
crawler.go

@ -128,6 +128,7 @@ func crawlIP(s *dnsseeder, r *result) ([]*wire.NetAddress, *crawlError) {
c := 0 c := 0
dowhile := true dowhile := true
peers := []*wire.NetAddress{}
for dowhile == true { for dowhile == true {
// Using the Bitcoin lib for the some networks means it does not understand some // Using the Bitcoin lib for the some networks means it does not understand some
@ -141,8 +142,19 @@ func crawlIP(s *dnsseeder, r *result) ([]*wire.NetAddress, *crawlError) {
if config.debug { if config.debug {
log.Printf("%s - debug - %s - received valid addr message\n", s.name, r.node) log.Printf("%s - debug - %s - received valid addr message\n", s.name, r.node)
} }
dowhile = false
return msg.AddrList, nil peers = append(peers, msg.AddrList...)
// Bitcoin nodes typically return two Addr messages: one with
// only one peer, and another with many peers. This is
// probably because ancient protocol versions (pver < 209) only
// allowed one peer per Addr mesage, so returning a one-peer
// Addr message first improves backward-compatibility. Anyway,
// this means we need to wait for the second Addr message.
if len(peers) > 1 {
dowhile = false
return msg.AddrList, nil
}
default: default:
if config.debug { if config.debug {
log.Printf("%s - debug - %s - ignoring message - %v\n", s.name, r.node, msg.Command()) log.Printf("%s - debug - %s - ignoring message - %v\n", s.name, r.node, msg.Command())

Loading…
Cancel
Save