News for hackers. Stuff that matters.
Re:AT&T updates firmware to block access to 1.1.1.1 by thaumasiotes on Wednesday May 02, 2018 @07:41PM (#16982122)
Are they blocking 8.8.8.8? Why do you think they're blocking 1.1.1.1?
Re:AT&T updates firmware to block access to 1.1.1.1 by harshreality on Wednesday May 02, 2018 @07:58PM (#16982201)
They were blocking 1.1.1.1 on some firmwares long before cloudflare's dns service started. From what I've read, the routers use it on some internal interface.

It's likely incompetence, not malice. If they didn't want people using other DNS, and were willing to fuck with ip addresses they don't own to accomplish that, they'd be blackholing google's and opendns's public caching nameservers too.

It might even have been a conscious decision. Even though it's horrible and the people involved in developing the firmware need re-education. The decision probably went like this: we need an internal address to do something. We can't use 10, 172.16, or 192.168 ranges because those might conflict with internal LANs. 1.x is safe because we all know nobody uses them. The correct decision obviously would have been to get at&t corporate to commit to never using some tiny corner of their address space, and use that. Or 127.a.b.c if that works on the OS. Those options are only needed if they really need an extra IP address. They might not need one after all if they designed their firmware better.

Re:AT&T updates firmware to block access to 1.1.1.1 by derekp7 on Wednesday May 02, 2018 @08:23PM (#16982330)
Whenever I've needed IP ranges for similar purposes (i.e., default IPs for container or VM internal / private networks) I've used ranges from RFC 5737 (192.0.2.0/24, 198.51.100.0/24, and 203.0.213.0/24). These are for reserved for documentation purposes, so it is highly unlikely that a customer would have these going in their own internal network. Not the best solution, but better than tying up a public /24 that we own.
Re:AT&T updates firmware to block access to 1.1.1.1 by wrigby on Wednesday May 02, 2018 @08:49PM (#16982444)
We used to use RFC1918 (172.16/12 IIRC) addresses for the communication between internal nodes in a cluster-in-box system that I worked on, which worked great until we had a subnet collision on a customer's network. Leaves me wondering if link-local (169.254/16, fe80::/10) would have been a better option - while technically the customer could decide to make the external (customer-facing) network have a link-local interface, the chances of that configuration actually happening are pretty slim.

I'm still not entirely sure what the best option is there. Maybe some clever use of network namespaces, with a named pipe to bridge between the "internal" and "external" universes? Just typing up that idea makes me cringe though.

Re:AT&T updates firmware to block access to 1.1.1.1 by derekp7 on Wednesday May 02, 2018 @09:03PM (#16982524)
BTW, for those wondering what this particular failure scenario is: Let's use Docker's default 172.17.0.0/16 subnet as an example. So your docker host has iptable DNAT rules that routes a given "external" IP address (10.0.1.15) to a given docker container (172.17.25.92). That works great, unless you have a workstation on a subnet such as 172.17.81.0/24. When that workstation sends a packet to 10.0.1.15, that packet gets routed to the destination container 172.17.25.92. That container goes to reply, but the reply packet never makes it out to the original workstation because the container host thinks it is bound for something else on its version of the 172.17 subnet.

One workaround to this is to have the container host also put in an SNAT rule, so that anything that it forwards to a container would have the source IP address re-written to appear to come from the container host's IP, or the docker0 bridge IP (172.17.0.1/16)

Re:AT&T updates firmware to block access to 1.1.1.1 by fyfy18 on Wednesday May 02, 2018 @10:14PM (#16982863)
On a similar note, Docker for Mac assigns (or used to?) the IP address 192.168.99.100 to the VM that runs Docker. One day I was working in a coffee shop and got really confused as to why I couldn’t connect to my application, even though the server was running. Then I realised the coffee shop WiFi was using 192.168.99.0/24 for client IPs.
Re:AT&T updates firmware to block access to 1.1.1.1 by kbaker on Wednesday May 02, 2018 @10:17PM (#16982873)
IPv6 Unique Local Addressing is made for this scenario, with a low chance of collisions. fd: + 40 random bits, becomes your new /48.

https://tools.ietf.org/html/rfc4193

Re:AT&T updates firmware to block access to 1.1.1.1 by dcow on Thursday May 03, 2018 @02:20AM (#16983749)
I can't wait till the world comes around to the true advantages of IPv6. It's not just about adding more global addresses...nodes participate in multiple first class networks now (one of those networks is often the global internet). I'd be much more comfortable with smart devices in my home if they're on a universal local network with a public internet federation service for things like software updates. IPv6 makes this possible.
Re:AT&T updates firmware to block access to 1.1.1.1 by harshreality on Wednesday May 02, 2018 @09:33PM (#16982666)
In a cluster-in-a-box scenario, you could modify the OS's network scripts to have the cluster-specific private interface start after the general LAN interface is up. Check both 10/8 and 172.16/12 to see if they're used by the public interface, and use whichever one isn't for the cluster network.
Re:AT&T updates firmware to block access to 1.1.1.1 by derekp7 on Wednesday May 02, 2018 @11:06PM (#16983067)
That only works if the host is on the conflicting network. But if the conflict is a couple hops away, Docker won't detect it.
Re:AT&T updates firmware to block access to 1.1.1.1 by Symbiote on Thursday May 03, 2018 @02:04AM (#16983679)
The correct solution is to choose a small part of their allocated public range, and reserve it for this purpose.

This is also the correct solution for your cluster.

Re:AT&T updates firmware to block access to 1.1.1.1 by jfoutz on Wednesday May 02, 2018 @08:46PM (#16982428)
It’s weird at&t is in such poor technical shape that they can’t control a single ip address, and then just use that.

This was an organization that sustained five mines of uptime for decades.

Crazy to see a fallen (or broken up) titan struggle with basic stuff. I mean, basic compared to their heyday.

Re:AT&T updates firmware to block access to 1.1.1.1 by fourthark on Wednesday May 02, 2018 @09:23PM (#16982621)
If you look at the history, the current AT&T is actually Southern Bell. It got eaten by one of its children.
Re:AT&T updates firmware to block access to 1.1.1.1 by godzillabrennus on Thursday May 03, 2018 @03:04AM (#16983912)
You would be amazed at how antiquated telecom companies are. They port numbers manually in many scenarios.
Re:AT&T updates firmware to block access to 1.1.1.1 by gaadd33 on Wednesday May 02, 2018 @08:45PM (#16982422)
I like to use 33.0.0.0/8 for that stuff since I don't believe any of those IPs are available on the open internet.
Re:AT&T updates firmware to block access to 1.1.1.1 by Piskvorrr on Thursday May 03, 2018 @04:58AM (#16984383)
Which is the exact problem that we're seeing, here. "Oh, I know, I'll just use a segment allocated to somebody else; it's not like they use it!" Aaand...whoops, they do.
Re:AT&T updates firmware to block access to 1.1.1.1 by bowersbros on Wednesday May 02, 2018 @08:51PM (#16982451)
I can't see anything about the 33.0.0.0/8 range being reserved

https://en.wikipedia.org/wiki/Reserved_IP_addresses

Re:AT&T updates firmware to block access to 1.1.1.1 by sarah180 on Wednesday May 02, 2018 @09:03PM (#16982525)
33.0.0.0/8 belongs to the Department of Defense. https://whois.arin.net/rest/net/NET-33-0-0-0-1/pft
Re:AT&T updates firmware to block access to 1.1.1.1 by loeg on Wednesday May 02, 2018 @09:06PM (#16982546)
https://www.iana.org/assignments/ipv4-address-space/ipv4-add...

It's allocated to "DLA Systems Automation Center," a branch of the US military. The addresses are probably used on NIPRNet/SIPRNet, but not publically routed. (Much like 22.0.0.0/8.)

Re:AT&T updates firmware to block access to 1.1.1.1 by nasredin on Thursday May 03, 2018 @07:46AM (#16985049)
The OP better not have anything juicy on his network. The Russian and Chinese are gonna be on you like a wife in a Finnish wife-carrying competition.

Don't use Kaspersky!

Re:AT&T updates firmware to block access to 1.1.1.1 by anilakar on Thursday May 03, 2018 @01:35AM (#16983569)
My personal favorites are 44.128.0.0/16, the explicitly unallocated test network for amateur packet radio to internet gateways, and 100.64.0.0/10, the address range for bidirectional carrier grade NAT.
Re:AT&T updates firmware to block access to 1.1.1.1 by masklinn on Thursday May 03, 2018 @07:53AM (#16985094)
Until they are and then everything breaks, which is basically what happened for 1.1.1.1.
Re:AT&T updates firmware to block access to 1.1.1.1 by solarkraft on Wednesday May 02, 2018 @08:20PM (#16982311)
Of course they don't want to use their own address space or commit to anything.
Re:AT&T updates firmware to block access to 1.1.1.1 by termie on Wednesday May 02, 2018 @07:51PM (#16982171)
Curious to know if they block Google’s DNS servers as well. That 1.x space was a RIPE research segment, so it’s possible that some internal AT&T group was using it with the assumption it would not be publicly routable and got bit. I was enjoying the shorthand ping of 1.1 for my router at home until Cloudflare took it over. Needless to say, if that was the case for AT&T, their ‘fix’ is not at all acceptable.
Re:AT&T updates firmware to block access to 1.1.1.1 by outworlder on Wednesday May 02, 2018 @07:47PM (#16982147)
Because users were able to connect and after the firmware update they are not? And also because they didn't even let you change this setting to begin with.

There is not enough data to attribute this to malice yet, but it does not look good (see CloudFlare's tweet).

Re:AT&T updates firmware to block access to 1.1.1.1 by xienze on Wednesday May 02, 2018 @08:59PM (#16982498)
And they singled out this one instead of Google’s, which has been around since well before NN existed and is far more well-known, because...? I remember seeing talk about this on dslreports a couple weeks ago, IIRC it’s not a deliberate block, they were using this IP or a range internally.
Re:AT&T updates firmware to block access to 1.1.1.1 by mabbo on Wednesday May 02, 2018 @07:46PM (#16982139)
I think they'll block 8.8.8.8 if the anger for blocking 1.1.1.1 isn't too loud.

I think they're blocking 1.1.1.1 because customers are now using DNS that isn't them, which deprives them of valuable data on which domain names their customers go to, which they can sell to advertisers. Yes, there's other ways to get that information but the DNS server is an easy one.

Re:AT&T updates firmware to block access to 1.1.1.1 by tinalumfoil on Wednesday May 02, 2018 @08:03PM (#16982221)
> I think they'll block 8.8.8.8 if the anger for blocking 1.1.1.1 isn't too loud.

On what basis? Google started Google Public DNS in 2009 and, as far as I know, it was never intentionally blocked by any ISPs. The issue with 1.1.1.1 is a lot of hardware treats it as though it was reserved for private networks. For instance, I can't access 1.1.1.1 right now since I'm connected to a Cisco router. So this could very well be a technical issue.

But even if 1.1.1.1 is taking off more than 8.8.8.8 did, your assuming the DNS queries people are sending are secure anyway. I'll admit I'm not completely up-to-date on the whole "DNS over TLS" thing but I haven't noticed any support for it on my fully-updated Windows machine or Android phone. I'd love for someone to correct me, but I don't believe any major electronics ship with secure DNS by default. If people are sending DNS queries unencrypted the ISPs can just sniff them.

Re:AT&T updates firmware to block access to 1.1.1.1 by paulmd on Thursday May 03, 2018 @03:44AM (#16984098)
> On what basis? Google started Google Public DNS in 2009 and, as far as I know, it was never intentionally blocked by any ISPs.

Net Neutrality wasn't considered much of an issue back then, it was just taken for granted (and the administration at the time was attempting to enforce it as vigorously as possible).

Forcing independent internet technical infrastructure off the internet and through their own proprietary infrastructure would be the opening shot you would expect if they wanted to open that battle. After all, you gotta boil the frog slowly, and nobody but a tiny minority of technical users would really care about not being able to use third-party DNS servers.

Re:AT&T updates firmware to block access to 1.1.1.1 by RKearney on Wednesday May 02, 2018 @08:07PM (#16982238)
> I can't access 1.1.1.1 right now since I'm connected to a Cisco router.

I've never seen or heard of a Cisco router doing anything that would interfere with access to 1.1.1.1.

Their wireless LAN controllers on the other hand, use 1.1.1.1 as the default (but entirely configurable) Virtual IP to use as an anchor for the captive portal.

If you can't access 1.1.1.1 behind a Cisco router it's likely because someone set it up incorrectly.

Re:AT&T updates firmware to block access to 1.1.1.1 by lathiat on Wednesday May 02, 2018 @08:41PM (#16982406)
> I've never seen or heard of a Cisco router doing anything that would interfere with access to 1.1.1.1.

I have news for you...

"After very little research we quickly came across Cisco mis-using 1.1.1.1, a quick search for “cisco 1.1.1.1” brought up numerous articles where Cisco are squatting on 1.1.1.1 for their Wireless LAN Controllers (WLC). It’s unclear if Cisco officially regards 1.0.0.0/8 as bogon space, but there are lots of examples that can be found on their community websites giving example bogon lists that include the /8. It mostly seems to be used for captive portal when authenticating to the wireless access point, often found in hotels, cafés and other public WiFi hotspot locations."

from: https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-g...

Re:AT&T updates firmware to block access to 1.1.1.1 by RKearney on Wednesday May 02, 2018 @08:45PM (#16982421)
As I already mentioned, their wireless LAN controller uses it as a configurable default. The Cisco Wireless LAN controller is not a Cisco "router".
Re:AT&T updates firmware to block access to 1.1.1.1 by zaroth on Wednesday May 02, 2018 @08:17PM (#16982296)
> I've never seen or heard of a Cisco router doing anything that would interfere with access to 1.1.1.1.

Well, now you have.

> If you can't access 1.1.1.1 behind a Cisco router it's likely because someone set it up incorrectly.

That’s kinda the point.

Re:AT&T updates firmware to block access to 1.1.1.1 by RKearney on Wednesday May 02, 2018 @08:25PM (#16982340)
> Well, now you have.

Allow me to rephrase, I've never heard of a Cisco router doing that from a reliable source.

> That’s kinda the point.

Then it has nothing to do with Cisco and everything to do with the person who configured it.

Re:AT&T updates firmware to block access to 1.1.1.1 by kilburn on Thursday May 03, 2018 @05:04AM (#16984404)
> As far as I know, it was never intentionally blocked by any ISPs.

My Spanish ISP (Vodafone ES) doesn't block external DNS at the ISP level. However, the router they give you:

1) Blocks outgoing DNS requests from the internal network by default. This can be disabled.

2) Doesn't let you specify any other than Vodafone's DNS servers on the DHCP Server configuration. This cannot be changed.

I'll let you decide whether this is blocking or not...

Re:AT&T updates firmware to block access to 1.1.1.1 by briffle on Wednesday May 02, 2018 @07:57PM (#16982197)
I'm guessing they aren't blocking, but internally routing that ip that does not go where it should. Many cisco/Airspace wireless network gear would put the sign in network on 1.1.1.1