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
|
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 271D11339
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 00:26:21 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from omr-a001.mx.aol.com (omr-a001e.mx.aol.com [204.29.186.53])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AD086138
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 00:26:20 +0000 (UTC)
Received: from mtaomg-aae01.mx.aol.com (mtaomg-aae01.mx.aol.com [172.27.1.99])
by omr-a001.mx.aol.com (Outbound Mail Relay) with ESMTP id
ADBB0380005C for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 31 Aug 2015 20:26:19 -0400 (EDT)
Received: from core-ada01c.mail.aol.com (core-ada01.mail.aol.com [172.27.0.1])
by mtaomg-aae01.mx.aol.com (OMAG/Core Interface) with ESMTP id
6626138000084 for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 31 Aug 2015 20:26:19 -0400 (EDT)
Received: from 162.227.126.201 by webprd-a67.mail.aol.com (10.72.57.81) with
HTTP (WebMailUI); Mon, 31 Aug 2015 20:26:17 -0400
Date: Mon, 31 Aug 2015 20:26:17 -0400
From: hurricanewarn1@aol.com
To: bitcoin-dev@lists.linuxfoundation.org
Message-Id: <14f864c1631-3abb-a855@webprd-a67.mail.aol.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_52037_1591138928.1441067177519"
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=1441067179;
bh=38jQkPuXFBEEkJifDax+xb7ejaVtS0YnaIug+B9xlIo=;
h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type;
b=YFeArsi97rypbn+2EJpC36+xfdiRyMkQT90PI31vSEZWAgjeCODqWOCJjEgFW+aZy
B6eY834DwYO1SZ/DFTxd8Uxo8wa+7zxbnzZMVTyd7B6xKEsufKMbZ/XwbqGJ4zHs7f
bSoEd7UTEF1LyGEI5xuHoCUynqFe7gUsNRhonBLQ=
x-aol-sid: 3039ac1b016355e4f0ab6545
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED,
DKIM_VALID,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,
RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: [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 00:26:21 -0000
------=_Part_52037_1591138928.1441067177519
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
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.
------=_Part_52037_1591138928.1441067177519
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<font color='black' size='2' face='arial'><font size="2">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.<br>
<br>
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.<br>
<br>
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. <br>
</font>
</font>
------=_Part_52037_1591138928.1441067177519--
|
