From: Mike Hearn <mike@plan99.net>
To: Johannes Henninger <blaubaer@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] DNS seeds returning gone peers
Date: Wed, 3 Aug 2011 14:17:48 +0200 [thread overview]
Message-ID: <CANEZrP1T=4DTWcAYMG9FQbWP-=N7ix-8r3X81c1fCybnb6vdKA@mail.gmail.com> (raw)
In-Reply-To: <4E393BCB.20904@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
OK, but, <50% show as port open .... maybe a bug in the seed?
05:16:52 scott:~$ nmap -p 8333 `dig +short dnsseed.bluematt.me`
Starting Nmap 5.00 ( http://nmap.org ) at 2011-08-03 14:17 CEST
Interesting ports on 83.220.45.22:
PORT STATE SERVICE
8333/tcp open unknown
Interesting ports on
c-6de0e055.27-2-64736c11.cust.bredbandsbolaget.se(85.224.224.109):
PORT STATE SERVICE
8333/tcp open unknown
Interesting ports on mackila.com (88.168.105.251):
PORT STATE SERVICE
8333/tcp open unknown
Interesting ports on 93-81-112-85.broadband.corbina.ru (93.81.112.85):
PORT STATE SERVICE
8333/tcp open unknown
Interesting ports on kons-5f710a2a.pool.mediaWays.net (95.113.10.42):
PORT STATE SERVICE
8333/tcp open unknown
Interesting ports on 173-218-216-132.atw.suddenlink.net (173.218.216.132):
PORT STATE SERVICE
8333/tcp open unknown
Interesting ports on
dynamicip-188-232-23-24.pppoe.omsk.ertelecom.ru(188.232.23.24):
PORT STATE SERVICE
8333/tcp open unknown
Interesting ports on c-71-229-116-166.hsd1.fl.comcast.net (71.229.116.166):
PORT STATE SERVICE
8333/tcp filtered unknown
Interesting ports on c-76-25-209-23.hsd1.co.comcast.net (76.25.209.23):
PORT STATE SERVICE
8333/tcp open unknown
Nmap done: 20 IP addresses (9 hosts up) scanned in 3.50 seconds
[-- Attachment #2: Type: text/html, Size: 2412 bytes --]
next prev parent reply other threads:[~2011-08-03 12:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 10:04 [Bitcoin-development] DNS seeds returning gone peers Mike Hearn
2011-08-03 11:38 ` Matt Corallo
2011-08-03 12:00 ` Mike Hearn
2011-08-03 12:15 ` Johannes Henninger
2011-08-03 12:17 ` Mike Hearn [this message]
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='CANEZrP1T=4DTWcAYMG9FQbWP-=N7ix-8r3X81c1fCybnb6vdKA@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=blaubaer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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