3 ms·
My guess is this is just incompetence and not intentionally made to block CloudFlare. I have one of those routers, and I couldn't use 1.1.1.1 because it was ro
by jedberg 9y ago
My guess is this is just incompetence and not intentionally made to block CloudFlare.
I have one of those routers, and I couldn't use 1.1.1.1 because it was routing to an internal interface on the router. I confirmed this with ping, I was getting microsecond response times from 1.1.1.1.
Under the new firmware, 1.1.1.1 is just dead. So it's probably still connected to the local interface, and nothing is listening.
- alex_young 9y agoThey started blocking 1.0.0.1 and CF ipv6 DNS too. This has to be intentional.
- jedberg 9y agoHmmm that's a fair point. But then why not also block 8.8.8.8?
- stonemetal 9y agoEveryone has heard of google, attacking them would cause back lash. Non technical people haven't heard of cloudflare so it is a softer target.
- sjwright 9y agoProbably because they know they would never be able to convince anyone that it was a technical bug and not malice. A surprising number of people seem to be convinced this was unintentional.
- anti_cf 9y agoAt least google doesn't block rarbg or thepiratebay. Good riddance to CF.