twisterarmy/dnsseeder
1
0
Fork 0
mirror of https://github.com/twisterarmy/dnsseeder.git synced 2025-08-26 05:31:56 +00:00
Code Issues Projects Releases Wiki Activity

Receive multiple peers per crawl

Browse Source
This commit is contained in:
Jeremy Rand 2021-11-09 12:07:43 +00:00
parent d6d09aa925
commit 0a20b45d6d
No known key found for this signature in database
GPG Key ID: EB03139A459DD06E
1 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
crawler.go
View File

@ -128,6 +128,7 @@ func crawlIP(s *dnsseeder, r *result) ([]*wire.NetAddress, *crawlError) {
c := 0
dowhile := true
peers := []*wire.NetAddress{}
for dowhile == true {
// 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 {
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:
if config.debug {
log.Printf("%s - debug - %s - ignoring message - %v\n", s.name, r.node, msg.Command())