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
|
Return-Path: <james.hilliard1@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id C295C144D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 01:16:33 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-la0-f54.google.com (mail-la0-f54.google.com
[209.85.215.54])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1686C12E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 01:16:33 +0000 (UTC)
Received: by labnh1 with SMTP id nh1so57491340lab.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 31 Aug 2015 18:16:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=gDIJEj/S1Hd+E9YD7Tx/x5VwttQRpzikYi6CBGPbvgw=;
b=NbmNBl447ql4uTo6c8cITyEa2xXTCQ5EVYUGgRe7Nlr0HqKf20iZMh2Y1d4pHDmQrw
4FE0e++tpBdHYKpdFczHMW2QOXFtDORx83JR4eI0P6AGxA0fC1ZaPCTytpD4f/k1YAaN
U2UH/zP7Iu+V0uYcb+AjJ3Vu/7RLlxs/erCyu2SeYddfgIK8JfhkjCodLeBDRpLghum3
1oKt4q4xOTUghfcjCD60sYUnMd/qptD2OnRq6xNDI+mYjqgUeP4h++mOZ/4hWRXuB0xf
WLQSw+dChHU3bcTVEQTNMqYFZmVViXgGq3IlsrpARu5//NxSbq6O84s+3FmDtCmYJdZz
my9w==
MIME-Version: 1.0
X-Received: by 10.152.23.38 with SMTP id j6mr11572504laf.47.1441070191432;
Mon, 31 Aug 2015 18:16:31 -0700 (PDT)
Received: by 10.112.220.8 with HTTP; Mon, 31 Aug 2015 18:16:31 -0700 (PDT)
In-Reply-To: <14f864c1631-3abb-a855@webprd-a67.mail.aol.com>
References: <14f864c1631-3abb-a855@webprd-a67.mail.aol.com>
Date: Mon, 31 Aug 2015 20:16:31 -0500
Message-ID: <CADvTj4rRVf89zU8dLROhyGopJNg2vLDg-9oviOLye_VcvuAy7A@mail.gmail.com>
From: James Hilliard <james.hilliard1@gmail.com>
To: hurricanewarn1@aol.com
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,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
Cc: 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
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:16:33 -0000
You should tell AT&T that you want the DVR/cable box put into what is
usually referred to as "bridge mode" or sometimes "true bridge mode"
depending on your ISP and then use your own router, look under
"Bridged Mode" at the bottom of this page for AT&T
http://www.att.com/gen/general?pid=23697 . You want your own router to
have the external IP, if it does not it is not configured correctly.
In general one should never use a router provided by their ISP for
anything other than modem functionality since it is typically only the
ISP that can change the firmware on it, it also makes troubleshooting
problems like this more difficult.
On Mon, Aug 31, 2015 at 7:26 PM, Zach G via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> 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.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
|
