public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd•org>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] IPv6 bitcoin support now live
Date: Sun, 27 May 2012 13:02:06 -0400	[thread overview]
Message-ID: <20120527170206.GA22582@savin> (raw)
In-Reply-To: <CAPg+sBhK+7eM6a60dVH4m=Kxd_SqqiEo4mybOXR+2o6uhfHUsQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

On Sat, May 26, 2012 at 03:14:40PM +0200, Pieter Wuille wrote:
> On Sat, May 12, 2012 at 3:42 AM, Jeff Garzik <jgarzik@exmulti•com> wrote:
> > sipa just pushed out IPv6 support to bitcoin/bitcoin.git, and we have
> > a few IPv6 nodes live on the network already.
> >
> > If you have IPv6, please pull the latest bitcoin and test!
> 
> Since yesterday, my DNS seeder (running at seed.bitcoin.sipa.be)  also
> crawls the IPv6 network, and returns corresponding AAAA records.
> Hopefully this helps IPv6 nodes to find eachother.

I can confirm this seems to work quite well now. I tried running an
IPv6-only node a few days ago, and with the default seeds it couldn't
start up and sync with the network unless I manually created a dual-net
node and manually added it. Now things work just fine out of the box and
last I checked I had 5 peers.

-- 
'peter'[:-1]@petertodd.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2012-05-27 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12  1:42 Jeff Garzik
     [not found] ` <CAPg+sBgf0uS9ua9kGcLraq_vQ+vx7o7XHfEdVRAEbYSG_6ibdQ@mail.gmail.com>
2012-05-26 13:14   ` Pieter Wuille
2012-05-27 17:02     ` Peter Todd [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120527170206.GA22582@savin \
    --to=pete@petertodd$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=pieter.wuille@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox