Title: Any reason to allow multiple incoming connections from same peer?
Post by: zvs on September 01, 2014, 09:55:45 AM
I just had to change my firewall to limit it to *two (might change it to one later), as I didn't want to block all of Linode, re: 2014-09-01 07:09:21 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=242 2014-09-01 07:09:53 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=243 2014-09-01 07:10:00 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=244 2014-09-01 07:10:11 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=245 2014-09-01 07:10:15 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=246 2014-09-01 07:37:47 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=274 2014-09-01 07:46:48 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=284 2014-09-01 07:46:51 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=286 2014-09-01 07:46:53 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=287 2014-09-01 07:46:57 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=288 2014-09-01 07:46:59 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=290 2014-09-01 07:47:24 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=293 2014-09-01 07:47:27 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=294 2014-09-01 07:47:31 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=295 2014-09-01 07:47:38 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=296 2014-09-01 07:47:43 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=297 2014-09-01 07:48:08 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=298 2014-09-01 07:48:49 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=299 2014-09-01 07:48:53 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=300 2014-09-01 07:48:57 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=301 2014-09-01 07:49:02 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=302 2014-09-01 07:49:30 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=303 2014-09-01 07:49:38 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=304 2014-09-01 07:49:47 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=305 2014-09-01 08:02:12 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=323 2014-09-01 08:02:28 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=324 2014-09-01 08:02:32 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=325 2014-09-01 08:02:34 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=326 2014-09-01 08:03:16 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=330 2014-09-01 08:13:43 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=347 2014-09-01 08:13:49 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=348 2014-09-01 08:13:54 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=349 2014-09-01 08:13:58 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=350 2014-09-01 08:14:02 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=351 2014-09-01 08:20:18 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=359 2014-09-01 08:20:25 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=360 2014-09-01 08:20:38 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=361 2014-09-01 08:20:45 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=362 2014-09-01 08:20:52 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=363 2014-09-01 08:21:36 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=369 2014-09-01 08:30:04 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=384 2014-09-01 08:30:07 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=385 2014-09-01 08:30:12 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=386 2014-09-01 08:30:26 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=387 2014-09-01 08:33:08 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=391 2014-09-01 08:33:14 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=392 2014-09-01 08:33:21 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=393 2014-09-01 08:33:25 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=394 2014-09-01 08:33:31 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=395 2014-09-01 08:33:35 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=396 2014-09-01 08:33:42 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=397 2014-09-01 08:34:14 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=398 2014-09-01 08:34:17 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=399 2014-09-01 08:34:21 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=400 2014-09-01 08:34:21 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=401 2014-09-01 08:34:27 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=402 2014-09-01 08:34:28 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=403 2014-09-01 08:52:51 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=430 2014-09-01 08:58:31 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=437 2014-09-01 09:07:57 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=452 2014-09-01 09:08:25 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=454 2014-09-01 09:08:32 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=456 2014-09-01 09:08:38 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=458 2014-09-01 09:20:20 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=474 2014-09-01 09:20:27 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=475 2014-09-01 09:20:31 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=476 2014-09-01 09:20:32 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=477 2014-09-01 09:20:33 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=478 2014-09-01 09:20:36 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=480 2014-09-01 09:20:46 receive version message: /Mothership:Aiur/: version 70001, blocks=318554, us=xx.xx.xx.xx:8333, peer=481 2014-09-01 09:21:10 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=484 2014-09-01 09:21:15 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=485 2014-09-01 09:21:17 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=486 2014-09-01 09:21:17 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=487 2014-09-01 09:21:19 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=488 2014-09-01 09:21:38 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=489 2014-09-01 09:21:39 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=490 2014-09-01 09:21:49 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=492 2014-09-01 09:21:49 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=493 2014-09-01 09:21:52 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=494 2014-09-01 09:21:53 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=495 2014-09-01 09:22:03 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=496 2014-09-01 09:22:08 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=497 2014-09-01 09:22:23 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=498 2014-09-01 09:22:29 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=499 2014-09-01 09:22:30 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=500 2014-09-01 09:22:32 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=501 2014-09-01 09:22:37 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=502 2014-09-01 09:22:38 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=503 2014-09-01 09:23:02 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=506 2014-09-01 09:23:10 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=507 2014-09-01 09:23:10 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=508 2014-09-01 09:23:16 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=509 2014-09-01 09:23:32 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=510 2014-09-01 09:23:47 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=511 2014-09-01 09:23:52 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=512 2014-09-01 09:24:02 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=513 2014-09-01 09:24:07 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=514 2014-09-01 09:24:12 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=515 2014-09-01 09:24:12 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=516 2014-09-01 09:24:20 receive version message: /Mothership:Aiur/: version 70001, blocks=318564, us=xx.xx.xx.xx:8333, peer=517 2014-09-01 09:24:24 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=518 2014-09-01 09:24:25 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=519 2014-09-01 09:24:25 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=520 2014-09-01 09:24:35 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=521 2014-09-01 09:24:46 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=524 2014-09-01 09:24:50 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=526 2014-09-01 09:24:54 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=527 2014-09-01 09:25:11 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=528
a small sampling of some tcpkills 2014-09-01 09:37:45 disconnecting peer=547 2014-09-01 09:37:45 disconnecting peer=515 2014-09-01 09:37:45 disconnecting peer=516 2014-09-01 09:37:45 disconnecting peer=519 2014-09-01 09:37:45 disconnecting peer=521 2014-09-01 09:37:45 disconnecting peer=524 2014-09-01 09:37:45 disconnecting peer=527 2014-09-01 09:37:45 disconnecting peer=528 2014-09-01 09:37:59 disconnecting peer=498 2014-09-01 09:37:59 disconnecting peer=499 2014-09-01 09:37:59 disconnecting peer=500 2014-09-01 09:37:59 disconnecting peer=501 2014-09-01 09:37:59 disconnecting peer=502 2014-09-01 09:37:59 disconnecting peer=503 2014-09-01 09:37:59 disconnecting peer=506 2014-09-01 09:38:13 disconnecting peer=474 2014-09-01 09:38:13 disconnecting peer=475 2014-09-01 09:38:13 disconnecting peer=476 2014-09-01 09:38:13 disconnecting peer=477 2014-09-01 09:38:13 disconnecting peer=478 2014-09-01 09:38:13 disconnecting peer=480 2014-09-01 09:38:13 disconnecting peer=481 2014-09-01 09:39:26 disconnecting peer=511 2014-09-01 09:39:26 disconnecting peer=512 2014-09-01 09:39:26 disconnecting peer=513 2014-09-01 09:39:26 disconnecting peer=514 2014-09-01 09:39:26 disconnecting peer=518 2014-09-01 09:39:26 disconnecting peer=520 2014-09-01 09:39:41 disconnecting peer=484 2014-09-01 09:39:41 disconnecting peer=485 2014-09-01 09:39:41 disconnecting peer=486 2014-09-01 09:39:41 disconnecting peer=487 2014-09-01 09:39:41 disconnecting peer=488 2014-09-01 09:39:41 disconnecting peer=490 2014-09-01 09:39:41 disconnecting peer=497 2014-09-01 09:39:57 disconnecting peer=489 2014-09-01 09:39:57 disconnecting peer=492 2014-09-01 09:39:57 disconnecting peer=493 2014-09-01 09:39:57 disconnecting peer=494 2014-09-01 09:39:57 disconnecting peer=495 2014-09-01 09:39:57 disconnecting peer=496
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: zvs on September 01, 2014, 10:30:57 AM
2014-09-01 10:28:18 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=106.187.41.230:31177, peer=683 2014-09-01 10:28:18 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=683 2014-09-01 10:28:18 disconnecting peer=683 2014-09-01 10:28:25 Added connection to 212.71.232.172:38923 peer=684 2014-09-01 10:28:25 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=212.71.232.172:38923, peer=684 2014-09-01 10:28:25 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=684 2014-09-01 10:28:26 disconnecting peer=684 2014-09-01 10:28:29 Added connection to 212.71.232.172:43145 peer=685 2014-09-01 10:28:29 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=212.71.232.172:43145, peer=685 2014-09-01 10:28:29 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=685 2014-09-01 10:28:29 disconnecting peer=685 2014-09-01 10:28:30 Added connection to 212.71.232.172:44375 peer=686 2014-09-01 10:28:30 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=212.71.232.172:44375, peer=686 2014-09-01 10:28:30 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=686 2014-09-01 10:28:30 disconnecting peer=686 2014-09-01 10:28:35 Added connection to 212.71.232.172:51607 peer=687 2014-09-01 10:28:35 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=212.71.232.172:51607, peer=687 2014-09-01 10:28:35 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=687 2014-09-01 10:28:36 disconnecting peer=687 2014-09-01 10:28:43 Added connection to 212.71.232.172:59603 peer=688 2014-09-01 10:28:43 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=212.71.232.172:59603, peer=688 2014-09-01 10:28:43 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=688 2014-09-01 10:28:43 disconnecting peer=688 2014-09-01 10:28:45 Added connection to 106.186.114.132:36468 peer=689 2014-09-01 10:28:45 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=106.186.114.132:36468, peer=689 2014-09-01 10:28:45 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=689 2014-09-01 10:28:53 Added connection to 106.186.114.132:48815 peer=690 2014-09-01 10:28:53 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=106.186.114.132:48815, peer=690 2014-09-01 10:28:53 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=690 2014-09-01 10:28:59 disconnecting peer=689 2014-09-01 10:28:59 disconnecting peer=690 2014-09-01 10:29:03 Added connection to 191.238.246.64:1131 peer=691 2014-09-01 10:29:03 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=191.238.246.64:1131, peer=691 2014-09-01 10:29:03 receive version message: /Satoshi:0.8.5/: version 70001, blocks=1, us=xx.xx.xx.xx:8333, peer=691 2014-09-01 10:29:20 Added connection to 106.186.114.132:11244 peer=692 2014-09-01 10:29:20 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=106.186.114.132:11244, peer=692 2014-09-01 10:29:20 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=692 2014-09-01 10:29:20 disconnecting peer=692 2014-09-01 10:29:20 Added connection to 106.186.114.132:11612 peer=693 2014-09-01 10:29:20 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=106.186.114.132:11612, peer=693 2014-09-01 10:29:20 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=693 2014-09-01 10:29:21 disconnecting peer=693 2014-09-01 10:29:25 Added connection to 199.127.225.214:58323 peer=694 2014-09-01 10:29:25 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=199.127.225.214:58323, peer=694 2014-09-01 10:29:25 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=xx.xx.xx.xx:8333, peer=694 2014-09-01 10:29:26 disconnecting peer=694 2014-09-01 10:29:30 Added connection to 106.187.41.230:35709 peer=695 2014-09-01 10:29:30 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=106.187.41.230:35709, peer=695 2014-09-01 10:29:30 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=695 2014-09-01 10:29:30 disconnecting peer=695 2014-09-01 10:29:31 Added connection to 106.186.114.132:20623 peer=696 2014-09-01 10:29:31 send version message: version 70002, blocks=318587, us=xx.xx.xx.xx:8333, them=106.186.114.132:20623, peer=696 2014-09-01 10:29:31 receive version message: /Mothership:Aiur/: version 70001, blocks=318572, us=xx.xx.xx.xx:8333, peer=696 2014-09-01 10:29:31 disconnecting peer=696
k d'oh, removed my IP. in any case... no reason to have more than one incoming connection from one peer, eh?
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: JWU42 on September 01, 2014, 11:13:00 AM
Noticed this "Mothership:Aiur" in my logs today as well... :-\
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: Newar on September 01, 2014, 11:20:10 AM
Seems they are missing this bit: ## If you run multiple nodes on a LAN, there's no need for ## ## all of them to open lots of connections. Instead ## ## 'connect' them all to one node that is port forwarded ## ## and has lots of connections. ## https://en.bitcoin.it/wiki/Running_Bitcoin#Sample_Bitcoin.conf
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: wumpus on September 01, 2014, 11:20:51 AM
I've noticed this as well, collected some information here: https://gist.github.com/laanwj/2a89da909bf161c7e4c2
* It appears that all the hosts are from Linode, and that they open multiple connections (about 5-6) * They claim NODE_NETWORK, but none of them has a sync height, so they're not actually requesting blocks (and will probably also not respond to getblocks requests, although I haven't tried) * I've enabled verbose logging for them, and from what I've seen they don't ever emit any commands apart from pong and version. They just listen for invs. * They do not accept incoming connections at least on the standard ports.
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: amaclin on September 01, 2014, 11:27:55 AM
Crazy bot >:( Of course, owners of full-nodes have to limit such connections. At least everyone has a right to do it.
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: zvs on September 01, 2014, 11:38:21 AM
I've noticed this as well, collected some information here: https://gist.github.com/laanwj/2a89da909bf161c7e4c2
* It appears that all the hosts are from Linode, and that they open multiple connections (about 5-6) * They claim NODE_NETWORK, but none of them has a sync height, so they're not actually requesting blocks (and will probably also not respond to getblocks requests, although I haven't tried) * I've enabled verbose logging for them, and from what I've seen they don't ever emit any commands apart from pong and version. They just listen for invs. * They do not accept incoming connections at least on the standard ports.
Yeah, I noticed that also, w/ tcpdump. Doesn't seem *especially* malicious, though I assume it has an impact on the 'anonymity' of it all. At least it's not like those 'BQS' or other randoms that spam out the: 2014-08-27 16:16:47 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length 2014-08-27 16:16:47 ProcessMessage(ping, 0 bytes) FAILED peer=1124 2014-08-27 16:25:49 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length 2014-08-27 16:25:49 ProcessMessage(ping, 0 bytes) FAILED peer=1124 2014-08-27 16:34:50 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length 2014-08-27 16:34:50 ProcessMessage(ping, 0 bytes) FAILED peer=1124 2014-08-27 16:43:51 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length 2014-08-27 16:43:51 ProcessMessage(ping, 0 bytes) FAILED peer=1124 Either way, someone must be monitoring them.... since it took about an hour for activity to resume once I removed my firewall & they have stopped attempting to connect to my IP now after about an hour of having a constant tcpkill going, which I'm going to stop now.. I went ahead and just limited 8333 to one connection per IP, but they could still connect 11 times. It was; 178.79.154.55 106.186.114.132 66.228.48.107 106.187.41.230 106.185.29.252 212.71.232.172 69.164.193.247 198.58.100.65 178.79.136.72 106.187.41.230 23.239.28.53 all Linode
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: gmaxwell on September 01, 2014, 11:42:05 AM
We should certantly prioritize bumping duplicate source IPs when we implement doing that— (I have a long list of criteria written up for that).
The reason we really shouldn't just ban is because there often are many independent nodes behind a NAT and it would be impolite to unnecessarily deny them connectivity. In at least one case there is a whole country behind a single IP.
Opening up multiple connections is really only the first and most boring of abusive behaviors people can / have been engaging in... there are quite a few parties which are now trying to connect constantly to every reachable host on the network and wasting a lot of connectivity. If we implement measures to address the bulk resource consumption more generally the repeats on one IP will also be approved as a side effect.
Free cookie to someone who can figure out what these specific ones are attempting to do in any case.
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: amaclin on September 01, 2014, 11:56:55 AM
In at least one case there is a whole country behind a single IP. Is it a difference between small country and big ISP? Free cookie to someone who can figure out what these specific ones are attempting to do in any case. Don't promise free cookies that people have to carry out free of charge. Otherwise will be temptation to violate rules only for the sake of buns.
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: 2112 on September 01, 2014, 07:14:57 PM
In at least one case there is a whole country behind a single IP. Is it a difference between small country and big ISP? Here's an example: entire USA customer base of Virgin Broadband (a CDMA wireless carrier) was (maybe still is, this is device-dependent) behind a couple of IPv4 addresses geolocating to Sandy,UT. http://en.wikipedia.org/wiki/Carrier-grade_NAT Depending on the internal mechanics of the CGN two connections from the same IP on the internal IP space could show as coming from the same or different address on the global IP space. There were special provisions for correct handling of legacy protocols like FTP and RSH.
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: amaclin on September 01, 2014, 08:50:31 PM
Here's an example: entire USA customer base of Virgin Broadband (a CDMA wireless carrier) was (maybe still is, this is device-dependent) behind a couple of IPv4 addresses geolocating to Sandy,UT. I think that in this case Virgin Broadband should take care of all their users.
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: 2112 on September 01, 2014, 09:09:46 PM
I think that in this case Virgin Broadband should take care of all their users.
What do you mean by "take care"? Virgin is just a retail brand that resells the wireless bandwidth provided by Sprint, which it turn uses equipment developed/installed/maintained by Alcatel/Lucent/Ericsson.
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: amaclin on September 02, 2014, 03:25:13 AM
What do you mean by "take care"? Oups. Sorry. My bad English. Not care, but responsibility. We see all users behind the NAT as one user and kick/ban him We can't distinguish with guarantee a situation of one or several users. Each node has a right to kick connection or ban IP, even it is IP for whole continent
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: 2112 on September 02, 2014, 03:52:42 AM
Oups. Sorry. My bad English. Not care, but responsibility. We see all users behind the NAT as one user and kick/ban him We can't distinguish with guarantee a situation of one or several users. Each node has a right to kick connection or ban IP, even it is IP for whole continent
Obviously they have the "right to kick/ban". The question: is do they really want to do it? Stupid anti-DoS defenses are actually quite common way how people loose market reach of their web portals when their target audience moves to a different way of accessing the Internet.
Title: Re: Any reason to allow multiple incoming connections from same peer?
Post by: amaclin on September 02, 2014, 04:25:49 AM
Obviously they have the "right to kick/ban". The question: is do they really want to do it? We can not force owners to do it. We can not prevent them to do this. It is not the layer of bitcoin protocol. Everybody is free to allow/disallow such connections. No other rules. Point.
|