📅 Original date posted:2015-08-31
📝 Original message: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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150831/a9145edf/attachment.html>;
hurricanewarn1 at aol.com [ARCHIVE] /
npub12j…h9d3k
2023-06-07 17:38:49
in reply to nevent1q…uny3
Author Public Key
npub12j6laxzzlnvudnvrkkm0fj6e2d9rgkfzwnylvrxsd2n74awmgf6qlh9d3kPublished at
2023-06-07 17:38:49Event JSON
{
"id": "cc1cda87ec253d8e181601675b3b3ab7e76dfd0d1d1f0cce1fc1b80be779bd1f",
"pubkey": "54b5fe9842fcd9c6cd83b5b6f4cb59534a34592274c9f60cd06aa7eaf5db4274",
"created_at": 1686159529,
"kind": 1,
"tags": [
[
"e",
"0bb14b1dc5a256e6026e426ff4cd5dede2ef74b0a579aeee84e58647c3f1acec",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2015-08-31\n📝 Original message: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.\n\nAfter hours of phone calls and messaging AT\u0026T 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.\n\nPerhaps 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. \n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150831/a9145edf/attachment.html\u003e",
"sig": "056f4b2083d4392bbcb12174fc0ce0da339dcb5ac890e5e28ab0a95346fa93808eec8235ce7a4d50a91886d8f0595b5e7995b3fe793e44104e2882036a2dec04"
}