From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: References: Date: Wed, 3 Aug 2011 09:28:59 -0500 X-Google-Sender-Auth: JBN4g95063Ss21lo8GqXdx8T4sw Message-ID: From: Douglas Huff To: Rick Wesson 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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" 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 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 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

There's a bigger problem here honestly. The p2p network is just star= ved for connectable slots.

You can start up a bitcoind, on a host with sufficient connectivity, wit= h -maxconnections=3D512 and they will fill in <15 minutes.

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.

--
Douglas Huff

On Aug 3, 2011 9:18 AM, "Rick Wesson" = <rick@support-intellige= nce.com> wrote:
> Starting from bitcoinj,= I have plenty of ways to publish DNS. Why sort them
> by version? Ordering from highest to lowest?
>
> how abou= t 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:
>
&g= t;> There's no project currently :-)
>>
>> Startin= g 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 dro= p-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
>> &g= t; wrote:
>>
>>> Mike,
>>>
>>> I think I ca= n contribute to your DNS seeding project. Could you help
>>> de= fine long-lived peers?
>>>
>>> -rick
>>>= ;
>>>
>>> On Wed, Aug 3, 2011 at 3:04 AM, Mike Hearn <= ;mike@plan99.net> wrote:
>&= gt;>
>>>> 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 833= 3 `dig +short bitseed.bitcoin.org= .uk
>>>> dnsseed.bluematt.me= bitseed.xf2.org`
>>>= ;> ...
>>>> Nmap done: 48 IP addresses (25 hosts up) scan= ned in 9.80 seconds
>>>>
>>>> $ grep -c 'closed' /tmp/x
&= gt;>>> 6
>>>>
>>>> So of 48 IPs retu= rned only 19 are actually usable. This is slowing down
>>>> = peer bringup for the Android apps, which don't currently save the addre= sses
>>>> of last-used peers (yes, I know we should fix this).
&g= t;>>>
>>>> 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 pee= rs that run the
>>>> latest version would be helpful for res= olving this kind of thing.
>>>>
>>>>
>&= gt;>> ---------------------------------------------------------------= ---------------
>>>> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Franc= isco, CA
>>>> The must-attend event for mobile developers. C= onnect with experts.
>>>> Get tools for creating Super Apps.= See the latest technologies.
>>>> Sessions, hands-on labs, demos & much more. Register e= arly & 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--