Live data from Hacker News

Cloudflare's new DNS attracting 'gigabits per second' of rubbish

zdnet.com

151–160 of 206 posts

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#151
> "Some folk, without any material to justify it, started configuring 1.1.1.1. Now, I can start using your IP address, I suppose, but we're both going to have a problem," Huston told ZDNet, laughing.

Ha, I was using 1.1.1.0/24 as my local intranet as an expirement with dnsmasq a few years back. I got scolded for it, rightly so, but I figured as no-one was using 1.1.1.0/24 at the time it was OK.

I see I am not the only one who did so.

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#152

Earlier quoted context omitted.

Such are the joys of modern "customer support" -- human beings don't scale, because they need to sleep and can only talk to one other human at a time. So you hire the cheapest ones you can find, and instruct them to be minimally helpful. Even better, make them all "managers," so "can I please speak to your manager" will just take you to another minimum-wage employee. If you want actual customer support these days, yo…

A smarter, and perhaps even more profitable way to approach this problem is "OK, we want almost everything that happens to customers to be a self-serve situation" and then make your (fewer) call centre employees highly trained troubleshooters who can figure out why _this_ customer wasn't able to self-serve and get that sorted for them. The result is a better customer experience (usually everything just works, when yo…

Lots of people simply do not like self serve. I get that companies want to cut costs, which is why we got endless telephone menu trees, then support web sites with crappy search, then automated telephone agents, then chat bots, and on and on. And the public has devised all these various tactics to skip that crap. I just want to talk to a damned human being rather than spend 10x the time navigating your poorly thought out Customer Avoidance Systems! Sometimes I need a drone and sometimes I need an expert. I have yet to see an automated system that could successfully determine which tier support I needed.

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#153

Earlier quoted context omitted.

And people wonder why https everywhere is such a necessity now. It should not be necessary to treat your last mile ISP as a hostile entity , but sadly, it often is.

At my work, we treat our own internal network as a hostile entity. Defense in depth.

Same here. Devs can't even mount thumbdrives. Which is fine for us, we don't need them, but it prevents some funny business should one of our laptops get stolen.

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#154
post #16

> AT&T Gigapower using 1.1.1.1 on an internal interface on at least one model of router-gateway, the Pace 5268AC Yup. I can't use 1.1.1.1 because my AT&T router is responding to it.

FTA: 1.0.0.1 in addition to 1.1.1.1

Try that as an alternative.

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#155
post #149

Earlier quoted context omitted.

Which city?

Washington DC - my neighborhood has Comcast, RCN, and Verizon. Our neighbors report better service on all three — and when you go a couple blocks south where the FIOS rollout stopped, regression to normal sets in for Comcast. We also have municipal fiber but they’ve chosen not to make that available for residential service which is really disappointing but … politics.

So, channel bonded docsis3.0 and 3.1 on Comcast and rcn, and gpon fiber from Verizon? Or are the cable operators also doing singlemode to the house now?

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#156
post #87

Earlier quoted context omitted.

example.com (and other example.*) is reserved for documentation purposes, i.e. you can't buy it.

Just like 1.1.1.1 used to be null routed?

Not exactly; example.com and .org are reserved in RFC 2606[1]. 1.1.1.1 is not listed in the special use RFC[2], it's just an address previously unused by APNIC.

[1]: https://tools.ietf.org/html/rfc2606

[2]: https://tools.ietf.org/html/rfc5735

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#157
post #79

Earlier quoted context omitted.

That means they're intercepting requests to 8.8.8.8 (even if only before login), probably because of its popularity. It's a shame we still have to use these hacks to login; there's a solution for that in RFC7710 (which sends the captive portal information in DHCP), but who knows if and when it'll be adopted by most hotspots. https://tools.ietf.org/html/rfc7710

> That means they're intercepting requests to 8.8.8.8 No, it means their hotspot uses 1.1.1.1 as internal IP. I've seen this in a bunch of places.

Cisco gear is probably the biggest culprit in my experience.

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#159

Earlier quoted context omitted.

> Anyone who relies on SMS for any type of authentication should stop Err. That's pretty much every implementation of 2FA around the world. Why isn't this more well known ?

The beauty of it is cases like Google's. They have this bizarre 2FA security-theater Google Authenticator thing, but then nearly force everyone to have their phonenumber as a "backup device". Guess what the send you when you forget your 2FA or password? Yep, an SMS. So out the door goes the whole point of 2FA. Your three factors (account name / email address + password + Google Authenticator) have now been reduced to…

https://medium.com/message/everything-is-broken-81e5f33a24e1

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#160
post #119
post #4

I've seen some of the papers where people look at big chunks of unused address space and watch the probes etc. It is really quite amazing. Once I screwed myself royally by accidentally turning RIP on for the upstream side of my router (connected to the cable modem) and it advertised 192.168/16 which Comcast accepted and started routing random stuff from the local exchange to my router. It was pretty funny talking to…

Even for regular IPv4s you often get upwards of 20-40k SSH probes per day trying common passwords against root. IPv6 largely makes this go away since it's too big to brute force scan.

> Even for regular IPv4s you often get upwards of 20-40k SSH probes per day trying common passwords against root

So...anyone here ever set up a throwaway machine with root ssh enabled with one of those common passwords, so that some of those could get in, so you could see what they actually try to do once they are in?

If so, what did you see?

Post reply on HN