Felix Lange ed97517ff4 p2p/discover: bump failure counter only if no nodes were provided (#19362) ... This resolves a minor issue where neighbors responses containing less than 16 nodes would bump the failure counter, removing the node. One situation where this can happen is a private deployment where the total number of extant nodes is less than 16. Issue found by @jsying.		2019-04-08 14:35:11 +03:00
..
node.go	p2p/discover, p2p/enode: rework endpoint proof handling, packet logging (#18963)	2019-01-29 17:39:20 +01:00
ntp.go	p2p, p2p/discover, p2p/nat: rework logging using context keys	2017-02-28 10:20:29 +01:00
table_test.go	p2p/discover: remove unused function	2019-02-19 13:29:19 +01:00
table_util_test.go	p2p/discover: remove unused function	2019-02-19 13:29:19 +01:00
table.go	p2p/discover: bump failure counter only if no nodes were provided (#19362)	2019-04-08 14:35:11 +03:00
udp_test.go	p2p/discover, p2p/enode: rework endpoint proof handling, packet logging (#18963)	2019-01-29 17:39:20 +01:00
udp.go	p2p/discover: make maximum packet size a constant (#19061)	2019-02-19 12:27:29 +01:00