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
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1Wp3Yy-0006cl-FL
for bitcoin-development@lists.sourceforge.net;
Mon, 26 May 2014 22:40:12 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.161 as permitted sender)
client-ip=62.13.148.161; envelope-from=pete@petertodd.org;
helo=outmail148161.authsmtp.com;
Received: from outmail148161.authsmtp.com ([62.13.148.161])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1Wp3Yw-0001Yp-JO for bitcoin-development@lists.sourceforge.net;
Mon, 26 May 2014 22:40:12 +0000
Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237])
by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s4QMe452072661;
Mon, 26 May 2014 23:40:04 +0100 (BST)
Received: from [10.212.89.202] ([95.35.52.202]) (authenticated bits=0)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s4QMdwac013526
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Mon, 26 May 2014 23:39:59 +0100 (BST)
User-Agent: K-9 Mail for Android
In-Reply-To: <lm0e7m$thg$1@ger.gmane.org>
References: <20140523221726.GA30143@petertodd.org> <lltfaa$2lv$1@ger.gmane.org>
<20140526163753.GA18693@petertodd.org> <lm0e7m$thg$1@ger.gmane.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
charset=UTF-8
From: Peter Todd <pete@petertodd.org>
Date: Tue, 27 May 2014 01:39:54 +0300
To: Andreas Schildbach <andreas@schildbach.de>,
bitcoin-development@lists.sourceforge.net
Message-ID: <b6884e2a-42b7-4c3f-a034-3a466aeec751@email.android.com>
X-Server-Quench: ab66ebbc-e526-11e3-9f74-002590a135d3
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdAQUFVQNAgsB AmIbWVdeU1R7XGo7 Yg9PbgBDZ0hQXQVo
T0xPR01TWkZsYGFV QU9NUhhxcgdANnhw bUcsDyJdWhEoJxVg
F0tWE3AHZDJjdWlJ V0RFdwNWdQpKLx5G bwR8GhFYa3VsFCMk
FAgyOXU9MCtSLCNN RwwLMWdaXUsQAjgx W1UZEDgjW0cEWy40
LhpgMlMAEVwNNUk+ d1w7VhoZKFcPEmxX EEhMBkcA
X-Authentic-SMTP: 61633532353630.1024:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 95.35.52.202/465
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1Wp3Yw-0001Yp-JO
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is
up again
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 26 May 2014 22:40:12 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 27 May 2014 01:12:05 GMT+03:00, Andreas Schildbach <andreas@schildbach.de> wrote:
>You're very quick to point at others. Especially since they run
>software
>that had the time to mature for about 30 years, and the protocol didn't
>really change since then...
>
>The last time it didn't work, the bug -- non RFC-conformance -- was on
>the bitcoin seeders side. ISPs do weird things with DNS, but usually
>they stay within the RFC.
>
>Anyway, without logs we don't have a chance to debug this issue. Any
>chance you could add simple logging to the seeder?
>
>DNS via HTTP? Never heard of that, at least it sounds weird as well.
Hey, really sorry I don't have the time to fix this issue, been travelling for a few weeks for my consulting job. If you want to step up and volunteer please feel free.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQFQBAEBCAA6BQJTg8K6MxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhUWgCADCNe4CjWondwDCovkv
+Cq7Yl3gLixvsTt5L9nllYc63/wt3GYliSIkR9baJ1QdPhckEjsvJV51XtdXPmJ5
EwTEbkJe6gflVwprvXB+w7eJtwMgZy5UoaWIYIZAIGsGKtJA8sngU1t638ywm68a
UEAcq/xACU47l2wPK/WU3uPY8ctGutCtXW2XDlDlCZOugqSc/8yaA76S5ogBicXw
xXvf95uMPVPCqit6B8FHCG/DH7akKGcnv6lIBTfx25KjgpyMwaroPt6EkPuz96MK
YbkQin0T0iW+X5WvXblO1mgq4fDrLE6J5x8sULFx/QKC9lgGB+cOQNKdyhxKOzF9
jtX7
=SUP4
-----END PGP SIGNATURE-----
|
