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
|
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 <mh.in.england@gmail.com>) id 1Qoa8b-0002GW-EO
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Aug 2011 12:01:25 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175; envelope-from=mh.in.england@gmail.com;
helo=mail-vx0-f175.google.com;
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Qoa8a-0000GT-DT
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Aug 2011 12:01:25 +0000
Received: by vxh2 with SMTP id 2so811397vxh.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 03 Aug 2011 05:01:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.116.67 with SMTP id ju3mr5581251vdb.63.1312372851235; Wed,
03 Aug 2011 05:00:51 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.158.233 with HTTP; Wed, 3 Aug 2011 05:00:51 -0700 (PDT)
In-Reply-To: <1312371499.2322.14.camel@Desktop666>
References: <CANEZrP1-BaNmKhSPXSe2sjH0-DPm62_=OQ_S6aCT3-nLdFLLGA@mail.gmail.com>
<1312371499.2322.14.camel@Desktop666>
Date: Wed, 3 Aug 2011 14:00:51 +0200
X-Google-Sender-Auth: SbJiHfINKvBcrqQwRFrHxoudDx0
Message-ID: <CANEZrP1k6QQKYUWKOyayWaySMnVrMgpbePX-9HpSq54DvNZCyA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Matt Corallo <bitcoin-list@bluematt.me>
Content-Type: multipart/alternative; boundary=bcaec548aa599c5b1d04a9989d51
X-Spam-Score: 1.3 (+)
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: bluematt.me]
-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
0.0 NORMAL_HTTP_TO_IP URI: Uses a dotted-decimal IP address in URL
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
0.1 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Qoa8a-0000GT-DT
Cc: bitcoin-development@lists.sourceforge.net
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: <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: Wed, 03 Aug 2011 12:01:25 -0000
--bcaec548aa599c5b1d04a9989d51
Content-Type: text/plain; charset=UTF-8
Yeah, the limited number of slots doesn't help either. I wonder if the
current settings are too conservative.
Your seed returns quite a few IPs that don't respond to ICMP pings - not
sure what is happening there.
03:01:53 scott:~$ for ip in `dig +short dnsseed.bluematt.me`; do echo -n -e
"Testing $ip: "; ping -c 1 $ip|grep 'packet loss'; done
Testing 24.7.158.162: 1 packets transmitted, 1 received, 0% packet loss,
time 0ms
*Testing 50.19.225.254: 1 packets transmitted, 0 received, 100% packet
loss, time 0ms
Testing 67.242.10.199: 1 packets transmitted, 0 received, 100% packet
loss, time 0ms
Testing 72.223.56.138: 1 packets transmitted, 0 received, 100% packet
loss, time 0ms
Testing 76.92.171.255: 1 packets transmitted, 0 received, 100% packet
loss, time 0ms
Testing 76.123.10.117: 1 packets transmitted, 0 received, 100% packet
loss, time 0ms
Testing 80.3.173.28: 1 packets transmitted, 0 received, 100% packet loss,
time 0ms
*Testing 80.101.109.52: 1 packets transmitted, 1 received, 0% packet loss,
time 0ms
Testing 93.186.32.117: 1 packets transmitted, 1 received, 0% packet loss,
time 0ms
*Testing 94.19.17.167: 1 packets transmitted, 0 received, 100% packet
loss, time 0ms
*Testing 97.86.39.50: 1 packets transmitted, 1 received, 0% packet loss,
time 0ms
Testing 113.255.177.241: 1 packets transmitted, 1 received, 0% packet
loss, time 0ms
Testing 118.208.226.66: 1 packets transmitted, 1 received, 0% packet loss,
time 0ms
Testing 173.180.141.86: 1 packets transmitted, 1 received, 0% packet loss,
time 0ms
*Testing 174.119.14.66: 1 packets transmitted, 0 received, 100% packet
loss, time 0ms
*Testing 178.18.129.133: 1 packets transmitted, 1 received, 0% packet
loss, time 0ms
*Testing 193.86.163.77: 1 packets transmitted, 0 received, 100% packet
loss, time 0ms
Testing 206.255.99.164: 1 packets transmitted, 0 received, 100% packet
loss, time 0ms
Testing 216.8.180.85: 1 packets transmitted, 0 received, 100% packet loss,
time 0ms
Testing 24.1.117.3: 1 packets transmitted, 0 received, 100% packet loss,
time 0ms*
--bcaec548aa599c5b1d04a9989d51
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Yeah, the limited number of slots doesn't help either. I wonder if the =
current settings are too conservative. <br><br>Your seed returns quite a fe=
w IPs that don't respond to ICMP pings - not sure what is happening the=
re.<br>
<br>03:01:53 scott:~$ for ip in `dig +short <a href=3D"http://dnsseed.bluem=
att.me">dnsseed.bluematt.me</a>`; do echo -n -e "Testing $ip: =C2=A0 &=
quot;; ping -c 1 $ip|grep 'packet loss'; done<br>Testing <a href=3D=
"http://24.7.158.162">24.7.158.162</a>: =C2=A0 1 packets transmitted, 1 rec=
eived, 0% packet loss, time 0ms<br>
<b>Testing <a href=3D"http://50.19.225.254">50.19.225.254</a>: =C2=A0 1 pac=
kets transmitted, 0 received, 100% packet loss, time 0ms<br>Testing <a href=
=3D"http://67.242.10.199">67.242.10.199</a>: =C2=A0 1 packets transmitted, =
0 received, 100% packet loss, time 0ms<br>
Testing <a href=3D"http://72.223.56.138">72.223.56.138</a>: =C2=A0 1 packet=
s transmitted, 0 received, 100% packet loss, time 0ms<br>Testing <a href=3D=
"http://76.92.171.255">76.92.171.255</a>: =C2=A0 1 packets transmitted, 0 r=
eceived, 100% packet loss, time 0ms<br>
Testing <a href=3D"http://76.123.10.117">76.123.10.117</a>: =C2=A0 1 packet=
s transmitted, 0 received, 100% packet loss, time 0ms<br>Testing <a href=3D=
"http://80.3.173.28">80.3.173.28</a>: =C2=A0 1 packets transmitted, 0 recei=
ved, 100% packet loss, time 0ms<br>
</b>Testing <a href=3D"http://80.101.109.52">80.101.109.52</a>: =C2=A0 1 pa=
ckets transmitted, 1 received, 0% packet loss, time 0ms<br>Testing <a href=
=3D"http://93.186.32.117">93.186.32.117</a>: =C2=A0 1 packets transmitted, =
1 received, 0% packet loss, time 0ms<br>
<b>Testing <a href=3D"http://94.19.17.167">94.19.17.167</a>: =C2=A0 1 packe=
ts transmitted, 0 received, 100% packet loss, time 0ms<br></b>Testing <a hr=
ef=3D"http://97.86.39.50">97.86.39.50</a>: =C2=A0 1 packets transmitted, 1 =
received, 0% packet loss, time 0ms<br>
Testing <a href=3D"http://113.255.177.241">113.255.177.241</a>: =C2=A0 1 pa=
ckets transmitted, 1 received, 0% packet loss, time 0ms<br>Testing <a href=
=3D"http://118.208.226.66">118.208.226.66</a>: =C2=A0 1 packets transmitted=
, 1 received, 0% packet loss, time 0ms<br>
Testing <a href=3D"http://173.180.141.86">173.180.141.86</a>: =C2=A0 1 pack=
ets transmitted, 1 received, 0% packet loss, time 0ms<br><b>Testing <a href=
=3D"http://174.119.14.66">174.119.14.66</a>: =C2=A0 1 packets transmitted, =
0 received, 100% packet loss, time 0ms<br>
</b>Testing <a href=3D"http://178.18.129.133">178.18.129.133</a>: =C2=A0 1 =
packets transmitted, 1 received, 0% packet loss, time 0ms<br><b>Testing <a =
href=3D"http://193.86.163.77">193.86.163.77</a>: =C2=A0 1 packets transmitt=
ed, 0 received, 100% packet loss, time 0ms<br>
Testing <a href=3D"http://206.255.99.164">206.255.99.164</a>: =C2=A0 1 pack=
ets transmitted, 0 received, 100% packet loss, time 0ms<br>Testing <a href=
=3D"http://216.8.180.85">216.8.180.85</a>: =C2=A0 1 packets transmitted, 0 =
received, 100% packet loss, time 0ms<br>
Testing <a href=3D"http://24.1.117.3">24.1.117.3</a>: =C2=A0 1 packets tran=
smitted, 0 received, 100% packet loss, time 0ms</b><br>
--bcaec548aa599c5b1d04a9989d51--
|
