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
|
Return-Path: <olinzodd@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 74B7011D2
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 01:20:47 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f182.google.com (mail-io0-f182.google.com
[209.85.223.182])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DA71C12E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 01:20:46 +0000 (UTC)
Received: by ioeu67 with SMTP id u67so36620628ioe.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 31 Aug 2015 18:20:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=from:to:subject:date:message-id:mime-version:content-type
:content-transfer-encoding:thread-index:content-language;
bh=6zwcHJP4mK9Nc/fF4DXzZEbh9++fzaG6GV5xlAzaB5Y=;
b=J05hzpQFMWpmKf5qkVo1CukP6qhbvuPSkLnKyOPgd9b86not3dumoj8eq7WXbLWyUB
fnO1odJ0HC88SsTBKdNUUZFqupWybquXAz4If0rTCcGFRsWT4GeyQaPuEMlnSz/HEVS1
QoWl9NlquZvSrwtvprVtUaTdHJU54TUNGrawiiaXGKn5UiJSsnjTBKvLxPj5sVLhhjIW
/IQoTx+uQ9s9V9Cld9htj1V0FoA48bjDqbF4bskgzG8ZqWz28RO8ovGFLnhg0k9C2vj9
sxKw2PgnMHLmDdmI4KtANjN/2jpB9vjVf4mWpYC/mAAhM9CFxM5QkMA4l+dAiNrDKR1L
m5Kw==
X-Received: by 10.107.46.154 with SMTP id u26mr31348247iou.124.1441070446289;
Mon, 31 Aug 2015 18:20:46 -0700 (PDT)
Received: from BigBone (cpe-24-29-26-191.cinci.res.rr.com. [24.29.26.191])
by smtp.gmail.com with ESMTPSA id 3sm192090igy.10.2015.08.31.18.20.44
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
Mon, 31 Aug 2015 18:20:45 -0700 (PDT)
From: "William Miller" <olinzodd@gmail.com>
To: <bitcoin-dev@lists.linuxfoundation.org>
Date: Mon, 31 Aug 2015 21:21:08 -0400
Message-ID: <004601d0e454$7bd225e0$737671a0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdDkU8GOtQXjY8gKTwK4lxzaGBXIUQ==
Content-Language: en-us
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
RCVD_IN_DNSWL_LOW 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] Message: 5
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:20:47 -0000
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!
|
