blob: e050ba6bf8bc0ba1f7147305727f2e1f91b03691 (
plain)
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
|
Return-Path: <milly@bitcoins.info>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id E51BE1593
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 01:05:04 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.help.org (mail.help.org [70.90.2.18])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 01ECC11D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 01:05:03 +0000 (UTC)
Received: from [10.1.10.25] (B [10.1.10.25]) by mail.help.org with ESMTPA
; Mon, 31 Aug 2015 21:04:55 -0400
To: bitcoin-dev@lists.linuxfoundation.org
References: <14f864c1631-3abb-a855@webprd-a67.mail.aol.com>
From: Milly Bitcoin <milly@bitcoins.info>
Message-ID: <55E4F9BB.5070902@bitcoins.info>
Date: Mon, 31 Aug 2015 21:04:59 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <14f864c1631-3abb-a855@webprd-a67.mail.aol.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] AT&T has effectively banned Bitcoin nodes by
closing port 8333 via a hidden firewall in the cable box
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 01:05:05 -0000
> 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
|
