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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pieter.wuille@gmail.com>) id 1SYGpS-0000Wa-Iz
for bitcoin-development@lists.sourceforge.net;
Sat, 26 May 2012 13:14:46 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.175 as permitted sender)
client-ip=209.85.160.175; envelope-from=pieter.wuille@gmail.com;
helo=mail-gh0-f175.google.com;
Received: from mail-gh0-f175.google.com ([209.85.160.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1SYGpR-0002zr-TU
for bitcoin-development@lists.sourceforge.net;
Sat, 26 May 2012 13:14:46 +0000
Received: by ghbz2 with SMTP id z2so977815ghb.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 26 May 2012 06:14:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.77.164 with SMTP id d24mr2134875yhe.129.1338038080516;
Sat, 26 May 2012 06:14:40 -0700 (PDT)
Received: by 10.236.157.106 with HTTP; Sat, 26 May 2012 06:14:40 -0700 (PDT)
In-Reply-To: <CAPg+sBgf0uS9ua9kGcLraq_vQ+vx7o7XHfEdVRAEbYSG_6ibdQ@mail.gmail.com>
References: <CA+8xBpfdN4QNwvkeU3z+oFybf9Z0DyHnVLF=AVA2gyfh65Gqeg@mail.gmail.com>
<CAPg+sBgf0uS9ua9kGcLraq_vQ+vx7o7XHfEdVRAEbYSG_6ibdQ@mail.gmail.com>
Date: Sat, 26 May 2012 15:14:40 +0200
Message-ID: <CAPg+sBhK+7eM6a60dVH4m=Kxd_SqqiEo4mybOXR+2o6uhfHUsQ@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.6 (-)
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
(pieter.wuille[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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
X-Headers-End: 1SYGpR-0002zr-TU
Subject: [Bitcoin-development] IPv6 bitcoin support now live
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: Sat, 26 May 2012 13:14:46 -0000
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) =A0also
crawls the IPv6 network, and returns corresponding AAAA records.
Hopefully this helps IPv6 nodes to find eachother.
--
Pieter
|
