public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "William Miller" <olinzodd@gmail.com>
To: <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Message: 5
Date: Mon, 31 Aug 2015 21:21:08 -0400	[thread overview]
Message-ID: <004601d0e454$7bd225e0$737671a0$@gmail.com> (raw)


Message: 5
Date: Mon, 31 Aug 2015 20:26:17 -0400
From: hurricanewarn1@aol.com
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] AT&T has effectively banned Bitcoin nodes by
	closing port 8333 via a hidden firewall in the cable box
Message-ID: <14f864c1631-3abb-a855@webprd-a67.mail.aol.com>
Content-Type: text/plain; charset="utf-8"

I have been struggling to get port 8333 open all year, I gave up and was
using blockchain for months despite a strong desire to stay on Bitcoin Core,
but now the issue has reached critical mass since I'm using the python
Bitcoin server module. I have literally spent my entire day trying to open
8333, I thoroughly made sure it was open on the router and computer and it's
still closed. Strangely enough I got it open for 30 seconds once today but
something closed it immediately.

After hours of phone calls and messaging AT&T finally told me the truth of
what was going on, and only because I noticed it myself and demanded an
answer. The internet is being routed through a DVR/cable box, and they
confirmed the DVR also has a firewall. To make this even more absurd they
refused to turn the firewall off because it is their equipment. So
effectively they can firewall any port they want even if the customer asks
them not to, in the unlikely event the customer figures it out.

Perhaps this is the driving force behind the inexplicable and massive
decline in Bitcoin nodes. Bitcoin is being censored by the ISPs themselves,
and they won't even tell you that. I had to get in touch with headquarters
and threaten to rip it out of the wall to get a proper answer.


I am grateful that, as of this current moment, Time Warner doesn't seem to
mind. I am aware of what you're saying, because a friend had me look at
their AT&T system one day, and I discovered all their equipment is now
running over IP. I was not aware, however, that they wouldn't unblock a
port.

I run a bitcoin node, miners ,all sort of other stuff (like Video, etc.) and
it runs pretty good, even with me myself having everything 'double
firewalled'. Time Warner seems the way to go!



                 reply	other threads:[~2015-09-01  1:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='004601d0e454$7bd225e0$737671a0$@gmail.com' \
    --to=olinzodd@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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