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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YxCPl-0004VH-Tx
for bitcoin-development@lists.sourceforge.net;
Tue, 26 May 2015 10:48:53 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.47 as permitted sender)
client-ip=74.125.82.47; envelope-from=mh.in.england@gmail.com;
helo=mail-wg0-f47.google.com;
Received: from mail-wg0-f47.google.com ([74.125.82.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YxCPk-0000G1-A4
for bitcoin-development@lists.sourceforge.net;
Tue, 26 May 2015 10:48:53 +0000
Received: by wgbgq6 with SMTP id gq6so93315896wgb.3
for <bitcoin-development@lists.sourceforge.net>;
Tue, 26 May 2015 03:48:46 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.212.3 with SMTP id ng3mr38641196wic.92.1432637326247;
Tue, 26 May 2015 03:48:46 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.194.143.9 with HTTP; Tue, 26 May 2015 03:48:46 -0700 (PDT)
In-Reply-To: <2558087.GVnsa68lBj@crushinator>
References: <CANe1mWwi+fxFU43_2mq-yd_qRsmCwMu_c5wWOpvFS4Un_FoT+Q@mail.gmail.com>
<23111107.dfGN69SrR9@crushinator>
<20150526051546.GB23502@savin.petertodd.org>
<2558087.GVnsa68lBj@crushinator>
Date: Tue, 26 May 2015 12:48:46 +0200
X-Google-Sender-Auth: eEnUhAUGe0xP2V4Up8kju28djak
Message-ID: <CANEZrP3tR-PTHnrAj4ptZnLh0PuWO_TWZ0FqpYe2TLNJC5C+xQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: multipart/alternative; boundary=001a11c356f4ec4ec40516f9de87
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1YxCPk-0000G1-A4
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Zero-Conf for Full Node Discovery
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: Tue, 26 May 2015 10:48:54 -0000
--001a11c356f4ec4ec40516f9de87
Content-Type: text/plain; charset=UTF-8
Very interesting Matt.
For what it's worth, in future bitcoinj is very likely to bootstrap from
Cartographer nodes (signed HTTP) rather than DNS, and we're also steadily
working towards Tor by default. So this approach will probably stop working
at some point. As breaking PorcFest would kind of suck, we might want a
ZeroConf/Rendezvous solution in place so local LANs can capture Bitcoin
traffic away from Tor (with some notification to the user, presumably).
On Tue, May 26, 2015 at 7:47 AM, Matt Whitlock <bip@mattwhitlock.name>
wrote:
> On Tuesday, 26 May 2015, at 1:15 am, Peter Todd wrote:
> > On Tue, May 26, 2015 at 12:52:07AM -0400, Matt Whitlock wrote:
> > > On Monday, 25 May 2015, at 11:48 pm, Jim Phillips wrote:
> > > > Do any wallets actually do this yet?
> > >
> > > Not that I know of, but they do seed their address database via DNS,
> which you can poison if you control the LAN's DNS resolver. I did this for
> a Bitcoin-only Wi-Fi network I operated at a remote festival. We had well
> over a hundred lightweight wallets, all trying to connect to the Bitcoin
> P2P network over a very bandwidth-constrained Internet link, so I poisoned
> the DNS and rejected all outbound connection attempts on port 8333, to
> force all the wallets to connect to a single local full node, which had
> connectivity to a single remote node over the Internet. Thus, all the
> lightweight wallets at the festival had Bitcoin network connectivity, but
> we only needed to backhaul the Bitcoin network's transaction traffic once.
> >
> > Interesting!
> >
> > What festival was this?
>
> The Porcupine Freedom Festival ("PorcFest") in New Hampshire last summer.
> I strongly suspect that it's the largest gathering of Bitcoin users at any
> event that is not specifically Bitcoin-themed. There's a lot of overlap
> between the Bitcoin and liberty communities. PorcFest draws somewhere
> around 1000-2000 attendees, a solid quarter of whom have Bitcoin wallets on
> their mobile devices.
>
> The backhaul was a 3G cellular Internet connection, and the local Bitcoin
> node and network router were hosted on a Raspberry Pi with some Netfilter
> tricks to restrict connectivity. The net result was that all Bitcoin nodes
> (lightweight and heavyweight) on the local Wi-Fi network were unable to
> connect to any Bitcoin nodes except for the local node, which they
> discovered via DNS. I also had provisions in place to allow outbound
> connectivity to the API servers for Mycelium, Blockchain, and Coinbase
> wallets, by feeding the DNS resolver's results in real-time into a
> whitelisting Netfilter rule utilizing IP Sets.
>
> For your amusement, here's the graphic for the banner that I had made to
> advertise the network at the festival (*chuckle*):
> http://www.mattwhitlock.com/bitcoin_wifi.png
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11c356f4ec4ec40516f9de87
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Very interesting Matt.<div><br></div><div>For what it'=
s worth, in future bitcoinj is very likely to bootstrap from Cartographer n=
odes (signed HTTP) rather than DNS, and we're also steadily working tow=
ards Tor by default. So this approach will probably stop working at some po=
int. As breaking PorcFest would kind of suck, we might want a ZeroConf/Rend=
ezvous solution in place so local LANs can capture Bitcoin traffic away fro=
m Tor (with some notification to the user, presumably).</div><div><br></div=
><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Tue, May 26, 2015 at 7:47 AM, Matt Whitlock <span dir=3D"ltr"><<=
a href=3D"mailto:bip@mattwhitlock.name" target=3D"_blank">bip@mattwhitlock.=
name</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"=
HOEnZb"><div class=3D"h5">On Tuesday, 26 May 2015, at 1:15 am, Peter Todd w=
rote:<br>
> On Tue, May 26, 2015 at 12:52:07AM -0400, Matt Whitlock wrote:<br>
> > On Monday, 25 May 2015, at 11:48 pm, Jim Phillips wrote:<br>
> > > Do any wallets actually do this yet?<br>
> ><br>
> > Not that I know of, but they do seed their address database via D=
NS, which you can poison if you control the LAN's DNS resolver. I did t=
his for a Bitcoin-only Wi-Fi network I operated at a remote festival. We ha=
d well over a hundred lightweight wallets, all trying to connect to the Bit=
coin P2P network over a very bandwidth-constrained Internet link, so I pois=
oned the DNS and rejected all outbound connection attempts on port 8333, to=
force all the wallets to connect to a single local full node, which had co=
nnectivity to a single remote node over the Internet. Thus, all the lightwe=
ight wallets at the festival had Bitcoin network connectivity, but we only =
needed to backhaul the Bitcoin network's transaction traffic once.<br>
><br>
> Interesting!<br>
><br>
> What festival was this?<br>
<br>
</div></div>The Porcupine Freedom Festival ("PorcFest") in New Ha=
mpshire last summer. I strongly suspect that it's the largest gathering=
of Bitcoin users at any event that is not specifically Bitcoin-themed. The=
re's a lot of overlap between the Bitcoin and liberty communities. Porc=
Fest draws somewhere around 1000-2000 attendees, a solid quarter of whom ha=
ve Bitcoin wallets on their mobile devices.<br>
<br>
The backhaul was a 3G cellular Internet connection, and the local Bitcoin n=
ode and network router were hosted on a Raspberry Pi with some Netfilter tr=
icks to restrict connectivity. The net result was that all Bitcoin nodes (l=
ightweight and heavyweight) on the local Wi-Fi network were unable to conne=
ct to any Bitcoin nodes except for the local node, which they discovered vi=
a DNS. I also had provisions in place to allow outbound connectivity to the=
API servers for Mycelium, Blockchain, and Coinbase wallets, by feeding the=
DNS resolver's results in real-time into a whitelisting Netfilter rule=
utilizing IP Sets.<br>
<br>
For your amusement, here's the graphic for the banner that I had made t=
o advertise the network at the festival (*chuckle*): <a href=3D"http://www.=
mattwhitlock.com/bitcoin_wifi.png" target=3D"_blank">http://www.mattwhitloc=
k.com/bitcoin_wifi.png</a><br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
One dashboard for servers and applications across Physical-Virtual-Cloud<br=
>
Widest out-of-the-box monitoring support with 50+ applications<br>
Performance metrics, stats and reports that give you Actionable Insights<br=
>
Deep dive visibility with transaction tracing using APM Insight.<br>
<a href=3D"http://ad.doubleclick.net/ddm/clk/290420510;117567292;y" target=
=3D"_blank">http://ad.doubleclick.net/ddm/clk/290420510;117567292;y</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--001a11c356f4ec4ec40516f9de87--
|
