From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E51BE1593 for ; 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 ; 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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