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
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
Return-Path: <hurricanewarn1@aol.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id C7ACF12C9
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Sep 2015 09:55:47 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from omr-a003.mx.aol.com (omr-a003e.mx.aol.com [204.29.186.57])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9CECE2AD
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Sep 2015 09:55:35 +0000 (UTC)
Received: from mtaomg-mbc02.mx.aol.com (mtaomg-mbc02.mx.aol.com
[172.26.221.144])
by omr-a003.mx.aol.com (Outbound Mail Relay) with ESMTP id A41873800292
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Sep 2015 05:55:34 -0400 (EDT)
Received: from core-ada09g.mail.aol.com (core-ada09.mail.aol.com [172.27.0.9])
by mtaomg-mbc02.mx.aol.com (OMAG/Core Interface) with ESMTP id
6032838000084 for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Sep 2015 05:55:34 -0400 (EDT)
Received: from 162.227.126.201 by webprd-a78.mail.aol.com (10.72.92.217) with
HTTP (WebMailUI); Fri, 04 Sep 2015 05:55:33 -0400
Date: Fri, 4 Sep 2015 05:55:33 -0400
From: hurricanewarn1@aol.com
To: bitcoin-dev@lists.linuxfoundation.org
Message-Id: <14f97c85622-1774-173a8@webprd-a78.mail.aol.com>
In-Reply-To: <2439331.T3Lg2rgENG@crushinator>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_114632_91401638.1441360533024"
X-MB-Message-Source: WebUI
X-MB-Message-Type: User
X-Mailer: JAS STD
X-Originating-IP: [162.227.126.201]
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com;
s=20150623; t=1441360534;
bh=pSmbRjV4SzyRPN0rhGw5CHvNFYS5AG+mSxs0UAbqx/c=;
h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type;
b=l+9HyfVDsadizaHLXGK4R0s0pd7n/NPoJLYzR1BC6ksWje6C7Jw+IVE2UKJCP0NX7
oUZEv3P5g776G5GmxbvgOh0Qyd+mT5BQjWuUdt74Bn/wz8YBK03EwjPYmDRbQ6sFaI
5V4y9uiny6TvOK6B5g6ISQYfU9NLyaDDgx832J5w=
x-aol-sid: 3039ac1add9055e96a9622c9
X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_50,DKIM_SIGNED,
DKIM_VALID,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,
RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=no version=3.3.1
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: [bitcoin-dev] AT&T/ISPs making Bitcoin Core near impossible to use
as a full node via hidden private dynamic IPs,
not by specifically blocking 8333 or Bitcoin as stated in original email
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: Fri, 04 Sep 2015 09:55:47 -0000
------=_Part_114632_91401638.1441360533024
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
I sent out an email after 48 hours of dealing with trying to open up my ports for Bitcoin, I was quite frustrated and angry since I had to call like 10 times and I was making zero progress. Most of the AT&T people didn't give me any helpful clues on how to fix the situation. The original email described how there is a firewall in the DVR, and I thought it was blocking the ports. It is true there is a uncontrollable firewall in the DVR, it is false this blocks 8333.
The actual problem is due to AT&T Uverse customers being forced to use a private dynamic IP, the IP is literally hidden from the internet, so it isn't possible to send any requests at it. It will literally ignore pings across all ports. So the solution is to switch to public static IP and make sure you allow incoming traffic.
It's not so simple though, AT&T will not let you have a public static IP without paying. I've had my router reset 10 times today by AT&T (probably automatically) and it comes back with a private dynamic IP. Then I have to reset it to use public IP and that lasts less than an hour. It literally went from open to closed while typing this email... the IP address went from public to private dynamic.
https://i.gyazo.com/3c732687fc3d21acb7d62f6d0e23a346.png
This is making using Bitcoin Core almost impossible. I'm at least getting some synch now but maybe a few days of blocks the entire day, cause I can't sit here all day with the computer and keep fixing it.
The proof is in the pudding, there are 37 nodes using AT&T in the ENTIRE world. AT&T is a massive ISP so this is strong evidence that using Bitcoin Core as a full node on AT&T is extremely difficult and actually just about impossible.
https://i.gyazo.com/90beebe056f5fc338165e8d200536c06.png
The other big ISPs have pathetic numbers also due to the same sort've things that AT&T does, but at least Comcast has 400 nodes. AT&T is much harder to use than any other ISP I've dealt with when it comes to Bitcoin Core.
I apologize for sending out the wrong info the first time, although it is still worth noting the DVR firewall is out of your control, which might be a problem if not now then in the future. In any case AT&T has effectively blocked full nodes for Bitcoin Core via the private subnet, and the disability to change it to public without paying $15 more per month, and buying a $15 connection service so they will give you that info (if you dont pay the connection 'specialists' hang up on you).
It is important to note this is not Bitcoin specific, but effects every program that depends on freely open ports. I don't think AT&T has anything against Bitcoin, it's just their security settings and policies have disabled Bitcoin Core for most customers. Also important to note this isn't a problem specific to AT&T, all the big ISPs are doing similar things. I believe the changes in ISP protocol are the main driving force behind the massive decline in Bitcoin nodes. Another big factor is firewalls, most people can't even remove the firewalls enough to open ports at will. The community needs to educate people on how to use Bitcoin Core when facing these intensifying security measures, or the decline of node numbers will continue.
------=_Part_114632_91401638.1441360533024
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<font color='black' size='2' face='arial'><font size="2">I sent out an email after 48 hours of dealing with trying to open up my ports for Bitcoin, I was quite frustrated and angry since I had to call like 10 times and I was making zero progress. Most of the AT&T people didn't give me any helpful clues on how to fix the situation. The original email described how there is a firewall in the DVR, and I thought it was blocking the ports. It is true there is a uncontrollable firewall in the DVR, it is false this blocks 8333.<br>
<br>
The actual problem is due to AT&T Uverse customers being forced to use a private dynamic IP, the IP is literally hidden from the internet, so it isn't possible to send any requests at it. It will literally ignore pings across all ports. So the solution is to switch to public static IP and make sure you allow incoming traffic. <br>
<br>
It's not so simple though, AT&T will not let you have a public static IP without paying. I've had my router reset 10 times today by AT&T (probably automatically) and it comes back with a private dynamic IP. Then I have to reset it to use public IP and that lasts less than an hour. It literally went from open to closed while typing this email... the IP address went from public to private dynamic. <br>
<br>
https://i.gyazo.com/3c732687fc3d21acb7d62f6d0e23a346.png<br>
<br>
This is making using Bitcoin Core almost impossible. I'm at least getting some synch now but maybe a few days of blocks the entire day, cause I can't sit here all day with the computer and keep fixing it.<br>
<br>
The proof is in the pudding, there are 37 nodes using AT&T in the ENTIRE world. AT&T is a massive ISP so this is strong evidence that using Bitcoin Core as a full node on AT&T is extremely difficult and actually just about impossible.<br>
<br>
https://i.gyazo.com/90beebe056f5fc338165e8d200536c06.png<br>
<br>
The other big ISPs have pathetic numbers also due to the same sort've things that AT&T does, but at least Comcast has 400 nodes. AT&T is much harder to use than any other ISP I've dealt with when it comes to Bitcoin Core.<br>
<br>
I apologize for sending out the wrong info the first time, although it is still worth noting the DVR firewall is out of your control, which might be a problem if not now then in the future. In any case AT&T has effectively blocked full nodes for Bitcoin Core via the private subnet, and the disability to change it to public without paying $15 more per month, and buying a $15 connection service so they will give you that info (if you dont pay the connection 'specialists' hang up on you). <br>
<br>
It is important to note this is not Bitcoin specific, but effects every program that depends on freely open ports. I don't think AT&T has anything against Bitcoin, it's just their security settings and policies have disabled Bitcoin Core for most customers. Also important to note this isn't a problem specific to AT&T, all the big ISPs are doing similar things. I believe the changes in ISP protocol are the main driving force behind the massive decline in Bitcoin nodes. Another big factor is firewalls, most people can't even remove the firewalls enough to open ports at will. The community needs to educate people on how to use Bitcoin Core when facing these intensifying security measures, or the decline of node numbers will continue.<br>
</font>
<div> </div>
<div style="font-family:arial,helvetica;font-size:10pt;color:black">
<div id="AOLMsgPart_1_41056f83-e0a9-4631-a7b9-033ed8c17379" style="margin: 0px;font-family: Tahoma, Verdana, Arial, Sans-Serif;font-size: 12px;color: #000;background-color: #fff;">
</div>
<!-- end of AOLMsgPart_1_41056f83-e0a9-4631-a7b9-033ed8c17379 -->
</div>
</font>
------=_Part_114632_91401638.1441360533024--
|
