Bitcoin Forum
April 26, 2024, 09:30:35 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 ... 143 »
321  Bitcoin / Development & Technical Discussion / Re: Any reason to allow multiple incoming connections from same peer? 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
322  Bitcoin / Development & Technical Discussion / Re: Any reason to allow multiple incoming connections from same peer? on: September 01, 2014, 10:30:57 AM
Code:
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?
323  Bitcoin / Development & Technical Discussion / Any reason to allow multiple incoming connections from same peer? 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:

Code:
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

Code:
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

324  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.9.2.1 has been released on: September 01, 2014, 03:39:06 AM
Turns out my ISP had suddenly blocked port 8333. The addnode worked with a nonstandard port. Other alt coin wallets work just fine so I guess they use a different port. In future, it seems like a good idea to add nodes that have non-standard ports for the bitcoin default node list, to prevent connection errors. Also this would makes it more difficult for ISP's to censor bitcoin traffic.

ISP?  or some crappy antivirus software?
325  Bitcoin / Bitcoin Discussion / Re: [ANN] Bitcoin blockchain data torrent on: September 01, 2014, 03:32:45 AM
How much time I need to sync the blockchain from zero using bitcoin-qt and how much with torrent?
I have a 7mb adsl.

Downloading bootstrap.dat will take some hours and syncing will take a few hours more. Smiley It might go upto 1-2 days.

~~MZ~~
'7mb' is pretty fast.  I'm going to assume that's 7Mbps and not, hrm, 56Mbps.  I had bonded DSL that was 25Mbps, supposedly being increased up to 60 soon...

Anyway, I can fully reindex the blockchain in an hour or so on an i7-4770, w/ the blockchain all being stored in RAM.  On a 7Mbps link, it'd probably be faster to download it from a fast node and sync it as it downloads, if you have anything faster than an i7-2600 or so.
326  Bitcoin / Development & Technical Discussion / Re: Running a full node is starting to be a pain on: August 31, 2014, 03:52:43 AM
Someone downloading the blockchain shouldn't make your computer unresponsive.  If you don't have enough upstream bandwidth, it could make your internet really slow.

If you really want to run one, just use something like this:

https://vpsdime.com/cart.php?a=add&pid=41

6GB RAM
30GB SSD space
4 vCPU cores
2TB traffic
10Gbps uplink
1x IPv4
OpenVZ/Custom
$7/month

... wouldn't do the annual billing tho, since 30GB won't be enough for a year.
327  Other / Beginners & Help / Re: Any good Bitcoin earning games? on: August 28, 2014, 07:16:48 AM
Yeah, look up on huntercoin.
yeah, huntercoin would qualify for sure.

re: primedice faucet, the amount goes up to a max of 5000, I think...  though you have to bet quite a bit to get it to that amount. 
328  Other / Beginners & Help / Re: sync wallet qt on: August 28, 2014, 07:14:20 AM
hello any fast way to sync my new Bitcoin wallet?
thanks

if you're in windows, after DLing the aforementioned bootstrap file,

run bitcoin-qt as bitcoin-qt -maxconnections=1 -connect=nogleg.com     

then it should catch up the last couple of hundred (?) blocks as fast as your CPU can process
329  Bitcoin / Bitcoin Technical Support / Re: configure does not work on: August 28, 2014, 07:04:09 AM
Try  

Code:
./autogen.sh
./configure
make



yeah, oops, had something else posted, but it's def the ./configure.ac .. not the file you want to run
330  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core stopped connecting??? on: August 28, 2014, 06:58:53 AM
possibly reasons:

antivirus software
task offloading
faulty router
wrong/old network driver (esp. for a virtual machine)
bitcoin.conf configured to only connect to one host, that's not taking connections anymore

I don't think it is the router because other wallets are working fine. Also not a driver issue because the problem is on two seperate computers.

There is no bitcoin.conf file

Antivirus/firewall and all security software is off.

What is task offloading?

Also, if I call my ISP, what am I suppose to explain? What port does bitcoin use? Maybe they have closed it or something...

I just edited post to include one that's running on non standard port... that'd probably be the first thing to try

if you're on windows, you can either use netsh from the command prompt or use the control panel -> device manager -> network -> properties, then it should have offloading options there, amongst other things.  for linux you can use ethtool, https://www.kernel.org/pub/software/network/ethtool/ethtool-3.15.tar.gz .. compile & install then ethtool -k eth0 (or w/e) will show options, ethtool -K eth0 <xx> to change..

i wouldnt mess with those until checking everything else though.

the whole other side closing connection is typically what would happen when a server that is already at its max number of connections is being connected to, afaik (it closes immediately after opening)

try going into console and doing addnode 5.9.24.81 onetry also, if the other one doesnt work (or in linux bitcoin-cli addnode xxx onetry)
331  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core stopped connecting??? on: August 28, 2014, 06:40:00 AM
possibly reasons:

antivirus software
task offloading
faulty router
wrong/old network driver (esp. for a virtual machine)
bitcoin.conf configured to only connect to one host, that's not taking connections anymore

ed: also you could try going into console and do addnode 205.186.129.90:46331 onetry

(connecting to a node that's not using standard port)
332  Bitcoin / Bitcoin Discussion / Re: 9 Most Useful Bitcoin Data Resources on: August 27, 2014, 06:38:08 AM
You forget bitcoinwisdom.
Didn't used them before. What services can they do for us?

never heard of it either, til this thread

Quote
As well, Zeroblock is now free i think: https://zeroblock.com/

people paid for this?

... and wizbit is at http://blocks.wizb.it/ , had to waste 30 seconds or so with google to find that.  i guess they are using blockchain.info for their IP information ?
333  Bitcoin / Bitcoin Technical Support / Re: 0.5 BTC Bounty to whoever helps me recover my BTC on: August 27, 2014, 06:15:20 AM
Unmount it, read only, use scalpel or extundelete on wallet.dat.  never used/heard of keyhunter.  

ed: like this http://linuxpoison.blogspot.com/2010/09/utility-to-recover-deleted-files-from.html       (it seems not to have mentioned it, but obv you wouldnt want to download *extundelete on the disk you're trying to recover files from)
334  Bitcoin / Bitcoin Technical Support / Re: Sent transaction over 8 hours ago. Still hasn't confirmed. Over 6k! Help!! on: August 27, 2014, 06:04:25 AM
Fee is 0.0001, transaction is over 1kb, should be 0.0002
335  Economy / Services / Re: [PrimeDice] [Highest Paid Signature] Earn Bitcoins Simply By Posting on: August 26, 2014, 11:23:56 AM
I haven't been paid, either.  Already sent a PM on Thursday

Same situation. 2 PM but no one respose.
I guess I'll wait until Wednesday or Thursday before another nag message, heh.
336  Economy / Services / Re: win88.me - signatures - 0.15 BTC paid up front on: August 26, 2014, 11:22:51 AM
I'm interested...  send me a PM?

thanks,
337  Economy / Services / Re: BTCJAM - need some info from someone else with an account on: August 26, 2014, 11:15:32 AM
What info are you looking for? If someone wasn't approved they don't get anything that you don't have.

I'm looking to find out if 1) everyone with unapproved identification has had it stored on a machine accessible to the public, and 2) if your ID is approved, if there is a full sized image that is accessible to the public (well, I'm damn near positive there is a full size image available, but I haven't figured out the formatting).

I won't link my picture ID (drivers license), but I suppose it won't hurt to link this, since (unlike my DL) you can't make out any of the information:

https://btcjam.s3.amazonaws.com/addr_checks/img/6616_ins.thumb.jpg

ed:  oh, i've been back and forth with them for the last 5-6 weeks or so about removing these images via the 2nd and 4th clause of their privacy policy.  i didnt realize until i checked the link urls that they were publically available, anyway.  it'd only be worth retaining an attorney if something like a full size DL is out there.  right now all there is is breach of contract, but i couldnt detail any financial losses
338  Economy / Computer hardware / Re: WTS Radeon HD 7970 (powercolor) - $100 shipped (to continental 48) on: August 26, 2014, 11:12:40 AM
I guess this isn't a great place to list video cards anymore.  =p

I'll give it 24hrs, then I'm going to list it as parts on ebay.   (with $125 buy it now and 'free shipping' probably)
339  Economy / Computer hardware / WTS Radeon HD 7970 (powercolor) - $100 shipped (to continental 48) on: August 26, 2014, 04:08:11 AM
$100 shipped is if you just want the card.  This is about $60-$100+ less than the 7970's selling on eBay, because, well, I'd have to list it as 'parts' on eBay. Oh, I'm excluding the person that listed a ton of sapphire 7970 cards in a row, auction style.  that's just an example of someone that doesn't know how to sell stuff properly on eBay (always buy-it-now)

http://www.ebay.com/sch/i.html?_from=R40&_sacat=0&_nkw=7970+radeon&LH_Complete=1&LH_Sold=1&rt=nc

It has a stripped screw that presumably one could fix rather easily with a drill or maybe even some bondo or epoxy.  

I have the box, CD, manual, etc.  The two things I'm not sure of are if it came with a crossfire cable or not (it won't have one if I send the box out), and whether or not I have the original antistatic bag it came in (it'll have one on it regardless, just no clue which bag belongs to which card).

The images (not hard to miss, but just in case, I circled the stripped screw & what I did to "fix" it):





and, yes, it runs fine.  it was my main vid card until I bought my geforce gtx 780.  it has maybe a month or two of 'mining' on it.  i think it maxed out at around 76o or 77oC midday (back in April or so)...  so, no, didn't run it at 80oC + for extended periods (if at all).

I bought it from newegg on 11/30/2013.  It was "open box";

http://www.newegg.com/Product/Product.aspx?Item=N82E16814131468R

It also doesn't come w/ a backplate, as you can see from those Newegg pics.  Anyway, as soon as I got it, I redid the thermal paste, stripping off that screw in the process (maybe "broke off that screw" is more proper, not sure).

PM me please, don't read this forum regularly.  I'm only interested in shipping to US, alaska & hawaii would cost a bunch more.  I'd want the payment first, before shipping... and no escrow BS
340  Economy / Services / Re: Need a Permenant Seed Node? on: August 26, 2014, 03:31:14 AM
Tripppn put up a seed node for IFC. Thanks.
My pleasure.  I've had enough interest in my little project i rented a second VPS so I have room for more if there's anyone else looking to get a seednode going for their coin or just want to support the coin they invested in with a permanent node.
Any chance you have a server or could get one in Asia?
I could get a server anywhere.  I didn't realize people were actually paying for this though.  Boggle.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 ... 143 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!