From: Mike Hearn <mike@plan99•net>
To: Matt Corallo <bitcoin-list@bluematt•me>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] DNS seeds returning gone peers
Date: Wed, 3 Aug 2011 14:00:51 +0200 [thread overview]
Message-ID: <CANEZrP1k6QQKYUWKOyayWaySMnVrMgpbePX-9HpSq54DvNZCyA@mail.gmail.com> (raw)
In-Reply-To: <1312371499.2322.14.camel@Desktop666>
[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]
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*
[-- Attachment #2: Type: text/html, Size: 2981 bytes --]
next prev parent reply other threads:[~2011-08-03 12:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 10:04 Mike Hearn
2011-08-03 11:38 ` Matt Corallo
2011-08-03 12:00 ` Mike Hearn [this message]
2011-08-03 12:15 ` Johannes Henninger
2011-08-03 12:17 ` Mike Hearn
2011-08-03 12:27 ` Caleb James DeLisle
2011-08-03 12:40 ` Mike Hearn
2011-08-03 14:00 ` Rick Wesson
2011-08-03 14:10 ` Mike Hearn
2011-08-03 14:18 ` Rick Wesson
2011-08-03 14:28 ` Douglas Huff
2011-08-03 14:39 ` Mike Hearn
2011-08-03 14:48 ` Gregory Maxwell
2011-08-03 15:32 ` Matt Corallo
2011-08-03 14:37 ` Christian Decker
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=CANEZrP1k6QQKYUWKOyayWaySMnVrMgpbePX-9HpSq54DvNZCyA@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@bluematt$(echo .)me \
/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