Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXzWq-000739-Vf for bitcoin-development@lists.sourceforge.net; Wed, 09 Apr 2014 20:55:29 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of heliacal.net designates 91.234.48.203 as permitted sender) client-ip=91.234.48.203; envelope-from=laszlo@heliacal.net; helo=mail3.heliacal.net; Received: from mail3.heliacal.net ([91.234.48.203]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WXzWp-0003zz-Ob for bitcoin-development@lists.sourceforge.net; Wed, 09 Apr 2014 20:55:28 +0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Laszlo Hanyecz In-Reply-To: Date: Wed, 9 Apr 2014 20:55:18 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <9A72087C-BE4D-492F-AB82-859C64DFA8EE@heliacal.net> References: <53456B99.9010207@monetize.io> <00b77560-d7ed-4ed4-a4e5-eb1f00467a06@email.android.com> <0509477C-89F9-47C7-8820-29ACAD4A4A8E@bitsofproof.com> <534592E2.7040800@gmail.com> <5345986C.3040901@gmail.com> To: slush X-Mailer: Apple Mail (2.1510) X-Spam-Score: -1.9 (-) 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 SPF_PASS SPF: sender matches SPF record -0.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -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: 1WXzWp-0003zz-Ob Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV wallets 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, 09 Apr 2014 20:55:31 -0000 On Apr 9, 2014, at 8:12 PM, slush wrote: >=20 > These days IPv6 is slowly deploying to server environments, but maybe = there's some simple way how to bundle ipv6 tunnelling into bitcoind so = any instance will become ipv6-reachable automatically? >=20 Teredo is available by default on Microsoft systems and it's actually = very common to see Teredo addresses as peers in torrents - this should = work for bitcoin too, though I'm not sure if an app needs to set special = flags to gain access to it.. there are probably some security settings = around it. In the US, AT&T/CenturyLink provide IPv6 by way of 6RD for = DSL customers, Comcast has native IPv6 on residential (but not business) = cable modems, and of course those who want to can always set up with a = tunnel broker like Hurricane Electric - they even let you use your own = IPv6 addresses. IPv6 is great, but having an application running its = own tunnels would not be a good way to leverage it. Probably what's keeping a lot of them from being reachable is that most = people just plug their CPE into a NAT router (without IPv6). Teredo can = help here though. Putting an IPv6 checkbox in the settings with a link to an explanation = might help with education and result in smarter operators who can make = their nodes reachable. A built in checker would be even better - = something like a checklist showing red/green for different aspects of = reachability (v4/teredo/v6). -Laszlo