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
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1QocA6-0001Rc-BK
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Aug 2011 14:11:06 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=mh.in.england@gmail.com;
helo=mail-vw0-f47.google.com;
Received: from mail-vw0-f47.google.com ([209.85.212.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QocA2-0008Hv-3j
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Aug 2011 14:11:04 +0000
Received: by vws2 with SMTP id 2so771007vws.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 03 Aug 2011 07:10:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.23.1 with SMTP id i1mr7061485vdf.398.1312380656520; Wed, 03
Aug 2011 07:10:56 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.158.233 with HTTP; Wed, 3 Aug 2011 07:10:56 -0700 (PDT)
In-Reply-To: <CAJ1JLtuRhqwcCWjv+H2XUjsX-Za9ZkSkOsH3t=JaUu1581RGUA@mail.gmail.com>
References: <CANEZrP1-BaNmKhSPXSe2sjH0-DPm62_=OQ_S6aCT3-nLdFLLGA@mail.gmail.com>
<CAJ1JLtuRhqwcCWjv+H2XUjsX-Za9ZkSkOsH3t=JaUu1581RGUA@mail.gmail.com>
Date: Wed, 3 Aug 2011 16:10:56 +0200
X-Google-Sender-Auth: zWYdbVk3VyPNtBvg-RXg4SfWTpQ
Message-ID: <CANEZrP2Cr1mVcj3CQQNx6BeWSb=hzxawva2Lz=sAbjx4AwYdmw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Rick Wesson <rick@support-intelligence.com>
Content-Type: multipart/alternative; boundary=20cf307cfc80d78e6b04a99a6ea8
X-Spam-Score: 1.3 (+)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.7 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist
[URIs: bitcoin.org.uk]
1.0 HTML_MESSAGE BODY: HTML included in message
0.3 HTML_FONT_FACE_BAD BODY: HTML font face is not a word
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
-0.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QocA2-0008Hv-3j
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds returning gone peers
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: Wed, 03 Aug 2011 14:11:06 -0000
--20cf307cfc80d78e6b04a99a6ea8
Content-Type: text/plain; charset=UTF-8
There's no project currently :-)
Starting from Matts code is probably the way to go. It's written in PHP.
Alternatively, you could write a Java app for it, as there are drop-in DNS
serving libraries you could link with BitCoinJ+sqlite. It probably wouldn't
be that hard. You'd want to sort nodes by version, how long they've been
observed to exist, the last polling time, etc.
On Wed, Aug 3, 2011 at 4:00 PM, Rick Wesson
<rick@support-intelligence.com>wrote:
> Mike,
>
> I think I can contribute to your DNS seeding project. Could you help define
> long-lived peers?
>
> -rick
>
>
> On Wed, Aug 3, 2011 at 3:04 AM, Mike Hearn <mike@plan99.net> wrote:
>
>> This is expected to happen from time to time of course as it's inherently
>> racy, but there are a *lot* of bad nodes appearing in the DNS seeds.
>>
>> $ nmap -oG /tmp/x -p 8333 `dig +short bitseed.bitcoin.org.uk
>> dnsseed.bluematt.me bitseed.xf2.org`
>> ...
>> Nmap done: 48 IP addresses (25 hosts up) scanned in 9.80 seconds
>>
>> $ grep -c 'closed' /tmp/x
>> 6
>>
>> So of 48 IPs returned only 19 are actually usable. This is slowing down
>> peer bringup for the Android apps, which don't currently save the addresses
>> of last-used peers (yes, I know we should fix this).
>>
>> I was talking to a friend a few days ago about Bitcoin, he seemed
>> interested. I'm hoping he might take on DNS seeding as a project. A custom
>> DNS server that watches the network to find long-lived peers that run the
>> latest version would be helpful for resolving this kind of thing.
>>
>>
>> ------------------------------------------------------------------------------
>> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
>> The must-attend event for mobile developers. Connect with experts.
>> Get tools for creating Super Apps. See the latest technologies.
>> Sessions, hands-on labs, demos & much more. Register early & save!
>> http://p.sf.net/sfu/rim-blackberry-1
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>
--20cf307cfc80d78e6b04a99a6ea8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
There's no project currently :-)=C2=A0<div><br></div><div>Starting from=
Matts code is probably the way to go. It's written in PHP. Alternative=
ly, you could write a Java app for it, as there are drop-in DNS serving lib=
raries you could link with BitCoinJ+sqlite. It probably wouldn't be tha=
t hard. You'd want to sort nodes by version, how long they've been =
observed to exist, the last polling time, etc.</div>
<div><br><div class=3D"gmail_quote">On Wed, Aug 3, 2011 at 4:00 PM, Rick We=
sson <span dir=3D"ltr"><<a href=3D"mailto:rick@support-intelligence.com"=
>rick@support-intelligence.com</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
Mike,<div><br></div><div>I think I can=C2=A0contribute=C2=A0to your DNS see=
ding project. Could you help define long-lived peers?=C2=A0</div><div><br><=
/div><div>-rick</div><div><br><br><div class=3D"gmail_quote"><div><div></di=
v><div class=3D"h5">
On Wed, Aug 3, 2011 at 3:04 AM, Mike Hearn <span dir=3D"ltr"><<a href=3D=
"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span> w=
rote:<br>
</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class=3D"h5=
">This is expected to happen from time to time of course as it's inhere=
ntly racy, but there are a <i>lot</i>=C2=A0of bad nodes appearing in the DN=
S seeds.<div>
<br></div><div><div><div><font face=3D"'courier new', monospace">$ =
nmap -oG /tmp/x -p 8333 `dig +short <a href=3D"http://bitseed.bitcoin.org.u=
k" target=3D"_blank">bitseed.bitcoin.org.uk</a> <a href=3D"http://dnsseed.b=
luematt.me" target=3D"_blank">dnsseed.bluematt.me</a> <a href=3D"http://bit=
seed.xf2.org" target=3D"_blank">bitseed.xf2.org</a>`</font></div>
</div></div><div><font face=3D"'courier new', monospace">...</font>=
</div><div><div><font face=3D"'courier new', monospace">Nmap done: =
48 IP addresses (25 hosts up) scanned in 9.80 seconds</font></div>
</div><div><font face=3D"'courier new', monospace"><br></font></div=
><div><font face=3D"'courier new', monospace">$ grep -c 'closed=
' /tmp/x</font></div>
<div><font face=3D"'courier new', monospace">6<br></font><br></div>=
<div>So of 48 IPs returned only 19 are actually usable. This is slowing dow=
n peer bringup for the Android apps, which don't currently save the add=
resses of last-used peers (yes, I know we should fix this).</div>
<div><br></div><div>I was talking to a friend a few days ago about Bitcoin,=
he seemed interested. I'm hoping he might take on DNS seeding as a pro=
ject. A custom DNS server that watches the network to find long-lived peers=
that run the latest version would be helpful for resolving this kind of th=
ing.</div>
<br></div></div><div class=3D"im">-----------------------------------------=
-------------------------------------<br>
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA<br>
The must-attend event for mobile developers. Connect with experts.<br>
Get tools for creating Super Apps. See the latest technologies.<br>
Sessions, hands-on labs, demos & much more. Register early & save!<=
br>
<a href=3D"http://p.sf.net/sfu/rim-blackberry-1" target=3D"_blank">http://p=
.sf.net/sfu/rim-blackberry-1</a><br>_______________________________________=
________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></div></blockquote></div><br></div>
</blockquote></div><br></div>
--20cf307cfc80d78e6b04a99a6ea8--
|
