AT&T updates firmware to block access to 1.1.1.1

Post by technion » Thu, May 03, 2018, 10:12 AM UTC

timmytim wrote: post #206

userbinator wrote: post #55

Earlier quoted context omitted.

Net neutrality started disappearing long before it was even called "net neutrality" --- a lot of residential ISPs won't even let others send packets to the full 64K port range of TCP/UDP to the IP it gives you, blocking some of them for "security reasons", throttling/cutting off certain protocols like BitTorrent, censoring "malicious" sites, etc. If we want true Internet connections we're going to have to fight a lot…

I would guess it has something to do with cisco asking them to help alleviate issues with their 1.1.1.1 squatting on a bunch of devices. I tested it when it came out, and if I set my DNS to 1.1.1.1, then logged into a hotel wireless network (that I knew was running those devices), as soon as a request was made, I was logged out of the captive portal. I would have expected 1.1.1.1 to already be blocked if anyone filte…

Post by csomar » Thu, May 03, 2018, 10:14 AM UTC

jaas wrote: post #71

I'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.

Post by jonathanstrange » Thu, May 03, 2018, 10:27 AM UTC

technion wrote: post #248

userbinator wrote: post #55

Earlier quoted context omitted.

Net neutrality started disappearing long before it was even called "net neutrality" --- a lot of residential ISPs won't even let others send packets to the full 64K port range of TCP/UDP to the IP it gives you, blocking some of them for "security reasons", throttling/cutting off certain protocols like BitTorrent, censoring "malicious" sites, etc. If we want true Internet connections we're going to have to fight a lot…

You can't be too mad about the full port range. Residential ISPs blocking port 25 outbound (spam malware) and inbound (people installing mailer services as an open relay by default) contributed to tonnes of unwanted traffic. I know there was an amount of collateral damage, but if you think about it, it's been many years since malware would get in user desktops and just send spam, largely due to this.

Post by fuzzy2 » Thu, May 03, 2018, 10:51 AM UTC

exabrial wrote: post #240

Klathmon wrote: post #239

Earlier quoted context omitted.

No your parent company needs to stop abusing that IP. Cloudflare is using a conventional IP, you are the one that isn't.

I wasn't disagreeing...? They're using an IP that wasn't assigned by IANA.

Post by kchr » Thu, May 03, 2018, 11:10 AM UTC

PinkMilkshake wrote: post #178

This is going to reveal my lack of networking knowledge but how does a company get an IP like 1.1.1.1? A bucket load of cash?