If at&t does not provide any official explanation, what's your opinion on how people should respond. The first thing that came to mind for me is to switch over to Xfinity on my next contract cycle.
AT&T updates firmware to block access to 1.1.1.1
91–100 of 382 posts
Re: AT&T updates firmware to block access to 1.1.1.1
#92I'd say there is a 98% chance this is a bug in some firmware and a 2% chance AT&T is intentionally trying to block Cloudflare DNS. I get why people are paranoid about ISPs blocking content and net neutrality, but let's not cry wolf prematurely. The technical details here strongly suggest a bug rather than intentional blocking of 1.1.1.1 DNS traffic.
A university I went to used 1.1.1.1 for its WiFi loginpage
Re: AT&T updates firmware to block access to 1.1.1.1
#93Earlier quoted context omitted.
They started blocking 1.0.0.1 and CF ipv6 DNS too. This has to be intentional.
Hmmm that's a fair point. But then why not also block 8.8.8.8?
Everyone has heard of google, attacking them would cause back lash. Non technical people haven't heard of cloudflare so it is a softer target.
Re: AT&T updates firmware to block access to 1.1.1.1
#94I wonder if anyone has considered some sort of legislation whereby internet service providers are not allowed to block or disrupt service to certain parts of the internet in order to promote their own business model.
NN seems like probably a good idea, but it's crazy to me how the whole internet went crazy over something with at-most marginal effects, but barely a peep over FOSTA which has already taken out vast swathes of valuable websites, craigslist personals perhaps most notably.
It's very unfortunate that people are simply fatigued of fighting this fight.
Also see the UK as well for an example of how previously unregulated speech has become regulated because the authorities have pushed over and over again, backing off every time there's a loud enough protest, but trying again after a short time.
Re: AT&T updates firmware to block access to 1.1.1.1
#95I'd say there is a 98% chance this is a bug in some firmware and a 2% chance AT&T is intentionally trying to block Cloudflare DNS. I get why people are paranoid about ISPs blocking content and net neutrality, but let's not cry wolf prematurely. The technical details here strongly suggest a bug rather than intentional blocking of 1.1.1.1 DNS traffic.
1.1.1.1 was working for me on AT&T after Cloudflare released 1.1.1.1, then shortly after that it ceased working.
Maybe the firmware update has a bug, but it's very suspiciously timed. Notice that the OP is dated April 2, while 1.1.1.1 was released April 1.
Re: AT&T updates firmware to block access to 1.1.1.1
#96I'd say there is a 98% chance this is a bug in some firmware and a 2% chance AT&T is intentionally trying to block Cloudflare DNS. I get why people are paranoid about ISPs blocking content and net neutrality, but let's not cry wolf prematurely. The technical details here strongly suggest a bug rather than intentional blocking of 1.1.1.1 DNS traffic.
You're absolutely right about this. This is almost certainly just there to block people who mistakenly paste in an example configuration somewhere. Back in 2010 there were problems that came up when IANA started allocating out of 1.0.0.0/8 (e.g. [1]). Things that were once assumed to be unused started being used, leading to strange issues. Also, why on earth would AT&T block 1.1.1.1 and not Google DNS and OpenDNS? [1…
According to the thread the timing on this looks pretty bad since those DNS IPs were previously working on the earlier firmware.
Re: AT&T updates firmware to block access to 1.1.1.1
#97I'd say there is a 98% chance this is a bug in some firmware and a 2% chance AT&T is intentionally trying to block Cloudflare DNS. I get why people are paranoid about ISPs blocking content and net neutrality, but let's not cry wolf prematurely. The technical details here strongly suggest a bug rather than intentional blocking of 1.1.1.1 DNS traffic.
Then the odds appear to not be in our favor. CF CEO tweets that 1.0.0.1 is also blocked. https://twitter.com/eastdakota/status/991718955021623296 Others have confirmed that the ipv6 address belonging to CF appears to be blocked.
Do you have a reference for the ipv6 address being blocked? That would be a much bigger smoking gun
Re: AT&T updates firmware to block access to 1.1.1.1
#98I'd say there is a 98% chance this is a bug in some firmware and a 2% chance AT&T is intentionally trying to block Cloudflare DNS. I get why people are paranoid about ISPs blocking content and net neutrality, but let's not cry wolf prematurely. The technical details here strongly suggest a bug rather than intentional blocking of 1.1.1.1 DNS traffic.
You could swap out those two odds and you would be just as right...
Re: AT&T updates firmware to block access to 1.1.1.1
#99What is the likelihood of obtaining net neutrality through the courts? I.E. Cloudflare sues -> judicial process -> decision that establishes a "right to access"?
Unlikely through the courts, although state utility regulators (i.e. the California Public Utilities Commission) might take interest. Democrat members of the FCC also might be interested.
Re: AT&T updates firmware to block access to 1.1.1.1
#100Earlier quoted context omitted.
That’s what I want to know. I’ll save the soapbox speech and just leave it at isn’t this why monopoly laws exist?
Unenforced laws might as well not exist. See: Monopoly/duopoly of telecom in the USA, net neutrality protections, and the speed limit signs on 280.
> Unenforced laws might as well not exist.
until they are selectively enforced.