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
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mith@jrbobdobbs.org>) id 1Qocmk-0003e8-Bv
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Aug 2011 14:51:02 +0000
X-ACL-Warn:
Received: from mail-wy0-f175.google.com ([74.125.82.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Qocmj-0002yQ-3E
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Aug 2011 14:51:02 +0000
Received: by wyg30 with SMTP id 30so928793wyg.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 03 Aug 2011 07:50:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.151.196 with SMTP id d4mr8754946wbw.102.1312381740058;
Wed, 03 Aug 2011 07:29:00 -0700 (PDT)
Sender: mith@jrbobdobbs.org
Received: by 10.216.134.132 with HTTP; Wed, 3 Aug 2011 07:28:59 -0700 (PDT)
Received: by 10.216.134.132 with HTTP; Wed, 3 Aug 2011 07:28:59 -0700 (PDT)
In-Reply-To: <CAJ1JLttf+h5J8ehmx1j5P1GiGYAUiLN=fGjSV_dLoy72XQohfA@mail.gmail.com>
References: <CANEZrP1-BaNmKhSPXSe2sjH0-DPm62_=OQ_S6aCT3-nLdFLLGA@mail.gmail.com>
<CAJ1JLtuRhqwcCWjv+H2XUjsX-Za9ZkSkOsH3t=JaUu1581RGUA@mail.gmail.com>
<CANEZrP2Cr1mVcj3CQQNx6BeWSb=hzxawva2Lz=sAbjx4AwYdmw@mail.gmail.com>
<CAJ1JLttf+h5J8ehmx1j5P1GiGYAUiLN=fGjSV_dLoy72XQohfA@mail.gmail.com>
Date: Wed, 3 Aug 2011 09:28:59 -0500
X-Google-Sender-Auth: JBN4g95063Ss21lo8GqXdx8T4sw
Message-ID: <CAPiTikUc5At5r8XH_5paQ2odx_bib0FGO4OqhGCeQEZ_VRkz0w@mail.gmail.com>
From: Douglas Huff <dhuff@jrbobdobbs.org>
To: Rick Wesson <rick@support-intelligence.com>
Content-Type: multipart/alternative; boundary=0016e64c1f746d0b2804a99aaffb
X-Spam-Score: 2.7 (++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
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
X-Headers-End: 1Qocmj-0002yQ-3E
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:51:02 -0000
--0016e64c1f746d0b2804a99aaffb
Content-Type: text/plain; charset=ISO-8859-1
There's a bigger problem here honestly. The p2p network is just starved for
connectable slots.
You can start up a bitcoind, on a host with sufficient connectivity, with
-maxconnections=512 and they will fill in <15 minutes.
As to why sort by version: <=3.23 has problems serving the blocks from the
last 2 months. It can take days to weeks to get the whole chain if you're
connecting to those nodes.
--
Douglas Huff
On Aug 3, 2011 9:18 AM, "Rick Wesson" <rick@support-intelligence.com> wrote:
> Starting from bitcoinj, I have plenty of ways to publish DNS. Why sort
them
> by version? Ordering from highest to lowest?
>
> how about publishing addresses under version.example.com if you version
has
> a perfrence?
>
> -rick
>
>
> On Wed, Aug 3, 2011 at 7:10 AM, Mike Hearn <mike@plan99.net> wrote:
>
>> 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
>>>>
>>>>
>>>
>>
--0016e64c1f746d0b2804a99aaffb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<p>There's a bigger problem here honestly. The p2p network is just star=
ved for connectable slots.</p>
<p>You can start up a bitcoind, on a host with sufficient connectivity, wit=
h -maxconnections=3D512 and they will fill in <15 minutes.</p>
<p>As to why sort by version: <=3D3.23 has problems serving the blocks f=
rom the last 2 months. It can take days to weeks to get the whole chain if =
you're connecting to those nodes.</p>
<p>-- <br>
Douglas Huff</p>
<div class=3D"gmail_quote">On Aug 3, 2011 9:18 AM, "Rick Wesson" =
<<a href=3D"mailto:rick@support-intelligence.com">rick@support-intellige=
nce.com</a>> wrote:<br type=3D"attribution">> Starting from bitcoinj,=
I have plenty of ways to publish DNS. Why sort them<br>
> by version? Ordering from highest to lowest?<br>> <br>> how abou=
t publishing addresses under <a href=3D"http://version.example.com">version=
.example.com</a> if you version has<br>> a perfrence?<br>> <br>> -=
rick<br>
> <br>> <br>> On Wed, Aug 3, 2011 at 7:10 AM, Mike Hearn <<a hr=
ef=3D"mailto:mike@plan99.net">mike@plan99.net</a>> wrote:<br>> <br>&g=
t;> There's no project currently :-)<br>>><br>>> Startin=
g from Matts code is probably the way to go. It's written in PHP.<br>
>> Alternatively, you could write a Java app for it, as there are dro=
p-in DNS<br>>> serving libraries you could link with BitCoinJ+sqlite.=
It probably wouldn't<br>>> be that hard. You'd want to sort =
nodes by version, how long they've been<br>
>> observed to exist, the last polling time, etc.<br>>><br>>=
> On Wed, Aug 3, 2011 at 4:00 PM, Rick Wesson <<a href=3D"mailto:rick=
@support-intelligence.com">rick@support-intelligence.com</a><br>>> &g=
t; wrote:<br>
>><br>>>> Mike,<br>>>><br>>>> I think I ca=
n contribute to your DNS seeding project. Could you help<br>>>> de=
fine long-lived peers?<br>>>><br>>>> -rick<br>>>>=
;<br>
>>><br>>>> On Wed, Aug 3, 2011 at 3:04 AM, Mike Hearn <=
;<a href=3D"mailto:mike@plan99.net">mike@plan99.net</a>> wrote:<br>>&=
gt;><br>>>>> This is expected to happen from time to time of=
course as it's inherently<br>
>>>> racy, but there are a *lot* of bad nodes appearing in the =
DNS seeds.<br>>>>><br>>>>> $ nmap -oG /tmp/x -p 833=
3 `dig +short <a href=3D"http://bitseed.bitcoin.org.uk">bitseed.bitcoin.org=
.uk</a><br>
>>>> <a href=3D"http://dnsseed.bluematt.me">dnsseed.bluematt.me=
</a> <a href=3D"http://bitseed.xf2.org">bitseed.xf2.org</a>`<br>>>>=
;> ...<br>>>>> Nmap done: 48 IP addresses (25 hosts up) scan=
ned in 9.80 seconds<br>
>>>><br>>>>> $ grep -c 'closed' /tmp/x<br>&=
gt;>>> 6<br>>>>><br>>>>> So of 48 IPs retu=
rned only 19 are actually usable. This is slowing down<br>>>>> =
peer bringup for the Android apps, which don't currently save the addre=
sses<br>
>>>> of last-used peers (yes, I know we should fix this).<br>&g=
t;>>><br>>>>> I was talking to a friend a few days ago=
about Bitcoin, he seemed<br>>>>> interested. I'm hoping he=
might take on DNS seeding as a project. A custom<br>
>>>> DNS server that watches the network to find long-lived pee=
rs that run the<br>>>>> latest version would be helpful for res=
olving this kind of thing.<br>>>>><br>>>>><br>>&=
gt;>> ---------------------------------------------------------------=
---------------<br>
>>>> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Franc=
isco, CA<br>>>>> The must-attend event for mobile developers. C=
onnect with experts.<br>>>>> Get tools for creating Super Apps.=
See the latest technologies.<br>
>>>> Sessions, hands-on labs, demos & much more. Register e=
arly & save!<br>>>>> <a href=3D"http://p.sf.net/sfu/rim-bla=
ckberry-1">http://p.sf.net/sfu/rim-blackberry-1</a><br>>>>> ___=
____________________________________________<br>
>>>> Bitcoin-development mailing list<br>>>>> <a hr=
ef=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development=
@lists.sourceforge.net</a><br>>>>> <a href=3D"https://lists.sou=
rceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.=
net/lists/listinfo/bitcoin-development</a><br>
>>>><br>>>>><br>>>><br>>><br></div>
--0016e64c1f746d0b2804a99aaffb--
|
