I suspect it is something that is going to have to be dealt with in the
future (I just don't know how yet).
The web has managed to survive despite constant fast crawls being the norm
for the past 10 years or so. I wouldn't worry too much about this unless
you can prove that a big chunk of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I may be able to provide some insight regarding request volume / abuse via my
public node at http://statoshi.info
My node receives a 'getaddr' request about every 50 seconds:
http://i.imgur.com/XEpnWfG.png
In terms of the 'addr' messages that it
Seeing this on one of my public nodes:
2014-07-30 13:13:26 receive version message:
/getaddr.bitnodes.io:0.1/: version 70001, blocks=313169,
us=162.219.2.72:8333, peer=11847
2014-07-30 13:13:33 receive version message:
/getaddr.bitnodes.io:0.1/: version 70001, blocks=29,
us=162.219.2.72:8333,
The version message helpfully tells me my own IP address but not theirs ;p
Try -logips. Logging peer IPs was disabled by default after #3764.
BTW I'm seeing the same abusive behavior. Who is running these? Why do
the requests need to be so frequent?
Wladimir
At least my crawler (bitcoin-seeder:0.01) software shouldn't reconnect
more frequently than once every 15 minutes. But maybe the two
connections you saw were instances?
On Wed, Jul 30, 2014 at 3:50 PM, Wladimir laa...@gmail.com wrote:
The version message helpfully tells me my own IP address but
I am also seeing these quite bit on my p2pool box.
Right now it is just a bit of (mostly) harmless spam but in the future I
can see this kind of thing being used in DDOS attacks and deep scans to
gather information to be used to harm the bitcoin network. We could easily
block them but then they
I believe the requests Jeff is seeing came from my crawler although anyone
could be running it (https://github.com/ayeowch/bitnodes) since there is no
IP address in the log to confirm the source of the requests.
This is a sample log of an actual request from my crawler at 148.251.238.178
:
7 matches
Mail list logo
