📅 Original date posted:2015-08-31
📝 Original message: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 at 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 at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
James Hilliard [ARCHIVE] /
npub10r…kgk2d
2023-06-07 17:38:49
in reply to nevent1q…jafd
Author Public Key
npub10r9d6edmnrljk59wsf06zqp494l3qtjpa3w245hy6t5euqxlzw2qdkgk2dPublished at
2023-06-07 17:38:49Event JSON
{
"id": "b0f0c326b7c871fe298c86c3c29dca0d58f149652cf0f92e432dc482bb0bf577",
"pubkey": "78cadd65bb98ff2b50ae825fa100352d7f102e41ec5caad2e4d2e99e00df1394",
"created_at": 1686159529,
"kind": 1,
"tags": [
[
"e",
"0bb14b1dc5a256e6026e426ff4cd5dede2ef74b0a579aeee84e58647c3f1acec",
"",
"root"
],
[
"e",
"d453fbc6a78c355ff03a1a7f9d512af909a779e5a3059eb45b674fab9bad5810",
"",
"reply"
],
[
"p",
"1b29d94ee81e1ee0479f1db4bc4ac887407bd470a0d7060e76f8ab27fdd57e50"
]
],
"content": "📅 Original date posted:2015-08-31\n📝 Original message:You should tell AT\u0026T that you want the DVR/cable box put into what is\nusually referred to as \"bridge mode\" or sometimes \"true bridge mode\"\ndepending on your ISP and then use your own router, look under\n\"Bridged Mode\" at the bottom of this page for AT\u0026T\nhttp://www.att.com/gen/general?pid=23697 . You want your own router to\nhave the external IP, if it does not it is not configured correctly.\nIn general one should never use a router provided by their ISP for\nanything other than modem functionality since it is typically only the\nISP that can change the firmware on it, it also makes troubleshooting\nproblems like this more difficult.\n\nOn Mon, Aug 31, 2015 at 7:26 PM, Zach G via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e I have been struggling to get port 8333 open all year, I gave up and was\n\u003e using blockchain for months despite a strong desire to stay on Bitcoin Core,\n\u003e but now the issue has reached critical mass since I'm using the python\n\u003e Bitcoin server module. I have literally spent my entire day trying to open\n\u003e 8333, I thoroughly made sure it was open on the router and computer and it's\n\u003e still closed. Strangely enough I got it open for 30 seconds once today but\n\u003e something closed it immediately.\n\u003e\n\u003e After hours of phone calls and messaging AT\u0026T finally told me the truth of\n\u003e what was going on, and only because I noticed it myself and demanded an\n\u003e answer. The internet is being routed through a DVR/cable box, and they\n\u003e confirmed the DVR also has a firewall. To make this even more absurd they\n\u003e refused to turn the firewall off because it is their equipment. So\n\u003e effectively they can firewall any port they want even if the customer asks\n\u003e them not to, in the unlikely event the customer figures it out.\n\u003e\n\u003e Perhaps this is the driving force behind the inexplicable and massive\n\u003e decline in Bitcoin nodes. Bitcoin is being censored by the ISPs themselves,\n\u003e and they won't even tell you that. I had to get in touch with headquarters\n\u003e and threaten to rip it out of the wall to get a proper answer.\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e",
"sig": "528ea03d5cb8c64c3ee4fd1e02ac2867fd175dcf291d1117a957352c62974b6aad378c3d211672be854e45c8e252c16f8efc68a52fac84d2edae8ba44bb60380"
}