By default, Bitcoin clients connect to other bitcoin nodes on TCP port 8333. If a user wants their Bitcoin client to connect to other nodes, they will need to allow outgoing TCP connections on port 8333, and also will need to have the ability to accept connections on that same port.
After spending an entire day effortlessly trying to get a bitcoin client working from a home computer, one AT&T Uverse customer called customer support.
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.
AT&T Uverse is a bundled package similar to what many of the other nationally known Cable Companies / ISPs are offering. Home Internet service along with your TV channels in one, with added benefits such as DVRs, streaming music, games, and much more.
The issue arises when the ISP is in full control of the hardware from your house to their router to the Internet. Many big name providers will intentionally close a slew of connection ports in order to provide what the company deems to be the best level of service.
“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.”, the disgruntled AT&T Uverse customer concluded.
Fear not, for all hope is not lost. While some ISP may indeed be blocking port 8333, they’re not singling that specific port out. The ISP are simply blocking ports en masse.
If users are unsure whether their ISPs are blocking Bitcoin, they may opt to perform an inbound port test. There are several web based services that will test an inbound connection on a specific port for you. A web search of “port testing” will give users a few different free services to choose from. Performing a port scan on port 8333 on your own connection will let you know if your ISP is blocking it or not.
If the user’s ISP does happen to block port 8333, there are a few solutions they can turn to, all of which require a little bit of effort and technical ability on the end users part.
For starters, users can ask their ISP’s to put the router into “Bridge Mode”. This turns the ISPs hardware into nothing more than a simple connection to the Internet. The user would be required to provide their own router, and to handle the configuration and maintenance of that hardware. The downside is that many ISPs limit technical support when a home user requests their router be put into Bridge Mode.
A second option, very similar to Bridge Mode, is to get a business account with the ISP. While these typically cost more money per month, they do come with additional benefits such as static IP Addresses, and higher bandwidth. Depending on the provider, business account may or may not come with their own Router, so users must be prepared to manage their own hardware with this scenario as well.
If users are concerned with telling their ISPs that they’re running a Bitcoin client, it just so happens that a few other well known services use port 8333. Instead of revealing any information about Bitcoin, users may tell their ISPs they’re running the VMWare Server Management User Interface, or the Y-Cam Wireless IP Camera.
Are ISPs Intentionally Blocking Bitcoin? Probably not. It’s safer to assume the ISPs are simply protecting their own network by limiting open ports to the ones the vast majority of consumer level people are using. There are options available to users of all levels to work around any perceived limitations ISPs place on connections, and there is a fantastic bitcoin community eager to help in any way they can.
Images from Shutterstock.
Last modified: May 21, 2020 11:02 AM UTC