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 A43AEEF2 for ; Wed, 2 Sep 2015 20:31:10 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from omr-m016.mx.aol.com (omr-m016e.mx.aol.com [204.29.186.16]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C20A8146 for ; Wed, 2 Sep 2015 20:31:07 +0000 (UTC) Received: from mtaomg-aaa01.mx.aol.com (unknown [172.27.1.227]) by omr-m016.mx.aol.com (Outbound Mail Relay) with ESMTP id E61B938001FD for ; Wed, 2 Sep 2015 16:31:06 -0400 (EDT) Received: from core-ada01c.mail.aol.com (core-ada01.mail.aol.com [172.27.0.1]) by mtaomg-aaa01.mx.aol.com (OMAG/Core Interface) with ESMTP id D145438000082 for ; Wed, 2 Sep 2015 16:31:05 -0400 (EDT) Received: from 162.227.126.201 by webprd-a78.mail.aol.com (10.72.92.217) with HTTP (WebMailUI); Wed, 02 Sep 2015 16:31:05 -0400 Date: Wed, 2 Sep 2015 16:31:05 -0400 From: hurricanewarn1@aol.com To: bitcoin-dev@lists.linuxfoundation.org Message-Id: <14f8fc177d4-1774-117a9@webprd-a78.mail.aol.com> In-Reply-To: <2439331.T3Lg2rgENG@crushinator> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_86217_2001908369.1441225865170" 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=1441225866; bh=41zeyra58EkoYysjSR5EPFt/Lg9y35oc/kZCcGiOFuo=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=DEmUUrPgxoluNXkdjEi18JOwcXoLpfjlcyTaU/o1S0nWsBAnlexMvvIworGFL4qeL 2LsKQBvqtnhLT+VAMk9rUbY6TEhlmbVqCz4DdRdhA+oLCSnpsmfxNRpafjT6jHan3B KGVcbCAKU6k7F1MUKv82FmT3r+zrt9R9Qxbl1uKE= x-aol-sid: 3039ac1b01e355e75c89663c X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,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: Re: [bitcoin-dev] AT&T has effectively banned Bitcoin nodes via utilizing private subnets. 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: Wed, 02 Sep 2015 20:31:10 -0000 ------=_Part_86217_2001908369.1441225865170 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit When you assume you make an ass out of you and me. That page doesn't even exist in my router, I don't have 2wire. The router I have is the one everyone is getting from uverse. Literally everything you said is incorrect. It is completely on topic as it pertains to Bitcoin Core functionality, 42 connections is nothing, and that's not how you fix it. If you're gonna call me out for being wrong at least be correct! I spent a lot of time fixing this and the info is useful cause this problem happens to a lot of people, so why obfuscate it with this nonsense. AT&T u-verse as it is now is near impossible for bitcoin nodes, 42 in the world is absolutely pathetic considering they are among the top 2 ISPs in the USA. Thanks for proving my point. -----Original Message----- From: Matt Whitlock To: hurricanewarn1 Cc: bitcoin-dev Sent: Wed, Sep 2, 2015 3:21 pm Subject: Re: [bitcoin-dev] AT&T has effectively banned Bitcoin nodes via utilizing private subnets. I've been trying to keep our discussion off-list because it is off-topic, but you keep adding the list back on in your replies. http://steamforge.net/wiki/images/2/29/Settings-Firewall-Advanced.png Settings > Firewall > Advanced Configuration > Outbound Protocol Control > All Other Protocols That's all you had to do. On Wednesday, 2 September 2015, at 9:44 am, Zach G via bitcoin-dev wrote: > 42 in the whole world, and I'm one of them. Clearly that is a problem, do you even know about AT&T or are you in another country? Cause that statement is utterly ridiculous given the fact there are hundreds of millions of people using AT&T. I was simply sharing my knowledge on this issue since it poses a threat to the health of the bitcoin network, no need for personal attacks. > > None of my accusations were false, there is a firewall in the DVR that is uncontrolled and all ports are blocked via private subnets and no fixed public IP allowed unless you pay. I confirmed every one of these details with AT&T technicians or I wouldn't be saying them. > > > > > > > > -----Original Message----- > From: Matt Whitlock > To: hurricanewarn1 > Sent: Wed, Sep 2, 2015 5:34 am > Subject: Re: [bitcoin-dev] AT&T has effectively banned Bitcoin nodes via utilizing private subnets. > > > According to BitNodes, 42 Bitcoin nodes are running on AT&T's > network: > > https://getaddr.bitnodes.io/nodes/?q=AT%26T > > So I'm thinking > there's nothing wrong with AT&T's default network configuration. > > Frankly, the > things you've been writing strongly suggest that you aren't very knowledgeable > about computer networking. Instead of jumping right into making wild accusations > about AT&T, you probably should find someone knowledgeable to verify your > claims. > > > On Wednesday, 2 September 2015, at 5:20 am, Zach G via bitcoin-dev > wrote: > > First off I couldn't synch the wallet, it said no block source > available and there was zero connections. Bitcoin was literally getting thottled > every second. It would not even allow the connection to get block source. EVERY > port was blocked, making exceptions in the router firewall did nothing. I was > forced to use Blockchain.info which is a major security risk. > > > > Secondly, I > am developing a program using Bitcoin Python modules, so I login to my computer > like it's a server and it was flat out rejecting the connection. I could not run > any code until this got fixed, and of course needed the block source to even do > anything. > > > > If Bitcoin Core worked but 8333 was blocked I would not be > emailing the list. Bitcoin Core was crippled and unusable due to the AT&T > settings, and they tried hard to get me to buy monthly subscriptions to get the > answer. This makes it likely that Bitcoin Core is unusable for most AT&T > customers and other ISPs, hence the massive node decline. I'm sure this disrupts > alot of other people besides Bitcoiners too, hence the monthly subscriptions > geared towards people who can't figure out their connection situation. > > > > > AT&T literally blocked access to static IP if you don't buy one, so it wasn't a > normal network setup. Unfortunately the same security used to stop hackers and > viruses stops Bitcoin too, so this is probably the settings for almost every > router in the country. Nodes are in fact declining worldwide, down 15% in the > past year alone. Community needs to speak up and also educate before this gets > completely out of control. https://getaddr.bitnodes.io/dashboard/?days=365 6,000 > nodes is pathetic as it is and it's constantly declining. ------=_Part_86217_2001908369.1441225865170 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit When you assume you make an ass out of you and me. That page doesn't even exist in my router, I don't have 2wire. The router I have is the one everyone is getting from uverse.

Literally everything you said is incorrect. It is completely on topic as it pertains to Bitcoin Core functionality, 42 connections is nothing, and that's not how you fix it. If you're gonna call me out for being wrong at least be correct! I spent a lot of time fixing this and the info is useful cause this problem happens to a lot of people, so why obfuscate it with this nonsense.

AT&T u-verse as it is now is near impossible for bitcoin nodes, 42 in the world is absolutely pathetic considering they are among the top 2 ISPs in the USA. Thanks for proving my point.


-----Original Message-----
From: Matt Whitlock <bip@mattwhitlock.name>
To: hurricanewarn1 <hurricanewarn1@aol.com>
Cc: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Sent: Wed, Sep 2, 2015 3:21 pm
Subject: Re: [bitcoin-dev] AT&T has effectively banned Bitcoin nodes via utilizing private subnets.

I've been trying to keep our discussion off-list because it is off-topic, but
you keep adding the list back on in your
replies.

http://steamforge.net/wiki/images/2/29/Settings-Firewall-Advanced.png

Settings
> Firewall > Advanced Configuration > Outbound Protocol Control > All Other
Protocols

That's all you had to do.


On Wednesday, 2 September 2015, at
9:44 am, Zach G via bitcoin-dev wrote:
> 42 in the whole world, and I'm one of
them. Clearly that is a problem, do you even know about AT&T or are you in
another country? Cause that statement is utterly ridiculous given the fact there
are hundreds of millions of people using AT&T. I was simply sharing my knowledge
on this issue since it poses a threat to the health of the bitcoin network, no
need for personal attacks. 
> 
> None of my accusations were false, there is a
firewall in the DVR that is uncontrolled and all ports are blocked via private
subnets and no fixed public IP allowed unless you pay. I confirmed every one of
these details with AT&T technicians or I wouldn't be saying them.
> 
>  
>

>  
> 
>  
> 
> -----Original Message-----
> From: Matt Whitlock
<bip@mattwhitlock.name>
> To: hurricanewarn1 <hurricanewarn1@aol.com>
> Sent:
Wed, Sep 2, 2015 5:34 am
> Subject: Re: [bitcoin-dev] AT&T has effectively
banned Bitcoin nodes via utilizing private subnets.
> 
> 
> According to
BitNodes, 42 Bitcoin nodes are running on AT&T's
> network:
> 
>
https://getaddr.bitnodes.io/nodes/?q=AT%26T
> 
> So I'm thinking
> there's
nothing wrong with AT&T's default network configuration.
> 
> Frankly, the
>
things you've been writing strongly suggest that you aren't very
knowledgeable
> about computer networking. Instead of jumping right into making
wild accusations
> about AT&T, you probably should find someone knowledgeable
to verify your
> claims.
> 
> 
> On Wednesday, 2 September 2015, at 5:20 am,
Zach G via bitcoin-dev
> wrote:
> > First off I couldn't synch the wallet, it
said no block source
> available and there was zero connections. Bitcoin was
literally getting thottled
> every second. It would not even allow the
connection to get block source. EVERY
> port was blocked, making exceptions in
the router firewall did nothing. I was
> forced to use Blockchain.info which is
a major security risk.
> > 
> > Secondly, I
> am developing a program using
Bitcoin Python modules, so I login to my computer
> like it's a server and it
was flat out rejecting the connection. I could not run
> any code until this
got fixed, and of course needed the block source to even do
> anything. 
> >

> > If Bitcoin Core worked but 8333 was blocked I would not be
> emailing the
list. Bitcoin Core was crippled and unusable due to the AT&T
> settings, and
they tried hard to get me to buy monthly subscriptions to get the
> answer.
This makes it likely that Bitcoin Core is unusable for most AT&T
> customers
and other ISPs, hence the massive node decline. I'm sure this disrupts
> alot
of other people besides Bitcoiners too, hence the monthly subscriptions
>
geared towards people who can't figure out their connection situation.
> > 
>
>
> AT&T literally blocked access to static IP if you don't buy one, so it
wasn't a
> normal network setup. Unfortunately the same security used to stop
hackers and
> viruses stops Bitcoin too, so this is probably the settings for
almost every
> router in the country. Nodes are in fact declining worldwide,
down 15% in the
> past year alone. Community needs to speak up and also educate
before this gets
> completely out of control.
https://getaddr.bitnodes.io/dashboard/?days=365 6,000
> nodes is pathetic as it
is and it's constantly declining.
------=_Part_86217_2001908369.1441225865170--