From: Milly Bitcoin <milly@bitcoins•info>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] AT&T has effectively banned Bitcoin nodes by closing port 8333 via a hidden firewall in the cable box
Date: Mon, 31 Aug 2015 21:04:59 -0400 [thread overview]
Message-ID: <55E4F9BB.5070902@bitcoins.info> (raw)
In-Reply-To: <14f864c1631-3abb-a855@webprd-a67.mail.aol.com>
> I have been struggling to get port 8333 open all year,
>
> After hours of phone calls and messaging AT&T finally told me the truth
> of what was going on,
I went through this Comcast involving another port. When they blocked
the port I asked them the reason (I referenced their privacy policy that
they are supposed to disclose my account info to me). they told me it
didn't matter what their privacy policy said, they weren't going to tell
me. I then showed up in federal court and testified as to what they
were doing. It was a class action lawsuit against them for people who
tried to get refunds over bandwidth throttling and I was one of members
of the class.
In any event the solution for me was to get a business account rather
than a residential account. You get a gateway that you can configure
yourself and you can turn off the firewall. As far as I can tell no
ports are blocked like residential accounts. The cost was an extra
$10/month (unless you get other options like fixed IP and/or increased
bandwidth). maybe you can get the data from bitnodes.io to see if any
ISP is blocking nodes. Maybe stats could be posted based on ISP. I
have been running a node through that account for awhile now
https://getaddr.bitnodes.io/nodes/70.90.2.18-8333/
Russ
next prev parent reply other threads:[~2015-09-01 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 0:26 hurricanewarn1
2015-09-01 1:04 ` Milly Bitcoin [this message]
2015-09-01 1:16 ` James Hilliard
2015-09-01 7:16 ` odinn
2015-09-01 14:44 ` Dan Bryant
2015-09-02 7:20 ` [bitcoin-dev] AT&T has effectively banned Bitcoin nodes via utilizing private subnets hurricanewarn1
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=55E4F9BB.5070902@bitcoins.info \
--to=milly@bitcoins$(echo .)info \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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