18 ms·
The DDoS that almost broke the Internet
- pragmatic 14y agoDid I miss something in your article (I skimmed), who are the gentlemen in the photo at the top?
- jgrahamc 14y agoI didn't write TFA, but it appears that that is an image of the group Massive Attack.
- solarflair 14y agoAfter seeing the headline and the photos, I kept expecting to read that it was some sort of composite "sketch" of suspects in the DDoS attack compiled from real photos. I am not familiar with what the members of Massive Attack look like and did not make that connection. Seems like poor photo usage.
- error54 14y agoThey were trying to be clever. "Largest DDoS attack"..."Massive Attack". But I love Massive Attack but yes, most people wouldn't recognize the muscians and assume that it was the suspects behind the attacks.
- m_for_monkey 14y agoI recognized them, nontheless, it would be nice to see the credits/licenses of the images.
- numbsafari 14y agoIt's a composite image of the members of Massive Attack.
- DangerousPie 14y agoSo, given that there is already a list of open resolvers and the problem is that they can be used to DDoS a server - why doesn't someone just make them attack each other? From what I have read one could easily forge packages appearing to come from DNS A and send it to DNS B-Z. Rinse, repeat and take down the servers one by one. Obviously this is probably illegal, but there would definitely be a beautiful irony to it. :)
- MostAwesomeDude 14y agoThese open resolvers are largely run by ISPs and resolve addresses for their customers. Taking them down would cripple the Internet access of their peers. They do not need to be taken down; they need to be reconfigured. An open DNS resolver is (arguably) misconfigured, not malicious.
- goldfeld 14y agoBy being made public they can be used maliciously by third parties. If such ISPs are slow to respond and reconfigure, they are a liability to the whole internet and the fault is theirs. A suggestion such as GPs, while probably illegal, sounds like an interesting way to hasten them a bit. Better to have their customers on their heels urging them to get a grip, than the whole internet in jeopardy.
- neumino 14y agoThanks for the post Clouflare. It's way more interesting to read from your perspective than from a random journalist.
- jre 14y agoAs a programmer with little knowledge of internet-scale networking, this was a very interesting read. Thanks !
- Ntrails 14y agoThanks for a really cool lesson about the nature of the internet :) I was, however, interested to see no mention whatsoever of cloudflare in other reports of this[1]. Is this something that bothers you? [1] e.g http://www.bbc.co.uk/news/technology-21954636 http://www.bbc.co.uk/news/technology-21954636
- eastdakota 14y agoNo. When we're doing our job right, no one should know that CloudFlare even exists.
- sakopov 14y agoThis was an immensely interesting read even though only high-level details were discussed. Always impressed with CloudFare architecture. Thanks for a great read!
- alanbyrne 14y agoThis is why I pay CloudFlare each month. They repeatedly publicly show that they know exactly what they're doing - and they do it without any sense of smugness.
- lucaspiller 14y agoI'm a bit confused about the 'open resolvers' bit. I searched for the static IP range assigned by my ISP, and a number of results came up: http://openresolverproject.org/search.cgi?mode=search4&search_for=109.224.131.0%2F24 http://openresolverproject.org/search.cgi?mode=search4&s... This range has a description of "Static IP Pool for xDSL End Users", so is it also home users who have open resolvers?
- bluedino 14y agoVery possible that the router provided by the ISP is mis-configured.
- nwh 14y agoYep, my ISP has three open resolvers in my assigned range, and another 6 in the alternate range. It it grounds to give them a slight prod?
- noselasd 14y agoYour ISP doesn't have 3 open resolvers. Your neighbors have. Your ISP could terminate the contract with those 3 customers, but they won't - they're customers. They could block inbound trafic on port 25 to those 3 customers (if they knew about it), but they have no incentive to. Or they could block all inbound traffic on port 25, which will likely break DNS for a lot of customers.
- baq 14y agoyou meant port 53, i presume?
- noselasd 14y agoups. ofcourse.
- nadinengland 14y agoI don't believe he/she did as for my ISP blocked port 80 and 443 making me resort to port 25 to send emails~
- apawloski 14y agoCloudflare always does an excellent job of optimizing their writeups for large, diverse audiences. The prose of this article reminds me of an equally accessible discussion of BGP from a few months ago [1]. [1] http://blog.cloudflare.com/why-google-went-offline-today-and-a-bit-about http://blog.cloudflare.com/why-google-went-offline-today-and...
- thatthatis 14y agoWhether intentional or not, this is some of the best PR marketing copy I've ever seen. Large, diverse audiences who are afraid of their blog/app/site getting DDOSed can understand enough to know that Cloudflare has a credible solution to that which they fear. I really can't figure out from their writing whether this is altruism accidentally leading to great PR or phenomenal PR leading to the appearance of altruism.
- hhw 14y agoI'd definitely say it's the latter. The non-PR version of the blog post is that they buy transit and peer at public exchanges out of many locations. Just like every other CDN. I cannot find a single action mentioned in the entire post of something that CloudFlare actually did to help mitigate the attack. Basically, it seems that the Internet network community at large scrambled to deal with the problems, and CloudFlare is taking credit for it.
- TranceMan 14y agoBasically, it seems that the Internet network community at large scrambled to deal with the problems, and CloudFlare is taking credit for it. This is true - if the Internet network community didn't identify this issue and see how they could mitigate it Cloudflare would have been toast. And now this blog post is number 1 on Hacker News...
- robryan 14y agoThey mitigated the attack against the site itself, forcing the attackers to move up the chain and try and target networks that connect to cloud flare. They also worked with these exchanges to mitigate the attack at that level. What more could they do?
- ChuckMcM 14y agoIn one of the earlier attacks I discovered I was running an open resolver on my home network. I fixed it, and now just get a bunch of 'recursive lookup denied' messages in my logs. But the key here is the source. And this from the article: "The attackers were able to generate more than 300Gbps of traffic likely with a network of their own that only had access 1/100th of that amount of traffic themselves." And this is key, so we could hunt them at their source if there was a way of deducing their launch points (it may be a botnet but it may also just be some random server farm) I've got log records of the form: Mar 27 09:19:21 www named[295]: denied recursion for query from [212.199.180.105].61604 for incap-dns-server.anycast-any2.incapsula.us IN Which suggests that 212.199.180.105 is somehow being used, and according my latest GeoIP database that is an IP address in Tel Aviv. $VAR1 = { 'longitude' => '34.7667', 'city' => 'Tel Aviv', 'latitude' => '32.0667', 'country_code' => 'IL', 'region' => '05', 'isp_org' => 'Golden Lines Cable' }; So can we create a service where the recurse requests send the IP trying to do the recursion to a service which then inverts the botnet/privatenet? Everytime this level of co-ordination is undertaken it potentially shines a bright light on the part of the Internet that is compromised/bad.
- peterwwillis 14y agoDNS requests are UDP, so you can just spoof the source address (actually that's what makes the attack work; you spoof the target as the source so replies 10x bigger than the query go to the target). Nobody can really know where they came from except at border routers of the source.
- pedrocr 14y agoDoes this mean that proper egress filtering would solve this? Because that seems like a more feasible solution. Having a bunch of large ISPs and datacenter operators block outgoing packets with sources outside their own IP ranges sounds much easier than having many more home users reconfigure their routers.
- peterwwillis 14y ago
- radio4fan 14y agoGreat post, and thanks for introducing me to the Open DNS Resolver Project. http://openresolverproject.org/ http://openresolverproject.org/
- kevinburke 14y agoWhat are the incentives for the maintainers of open DNS recursors? How can we alter their incentives so that they can no longer be used in DNS amplification attacks?
- sterlingross 14y agoThere isn't much incentive save for the fact that it is easier to configure. For some versions of DNS servers you need to consciously disable recursive lookups and then configure the list of servers that are accepted. If a DNS server doesn't perform lookups for any outside server it isnt very useful. If you think about a web host, with X number of servers that host websites, these are considered the Master DNS servers when the physical domains being hosted reside on those servers. The public listed DNS servers on your domain WHOIS records are actually the Secondary DNS servers, and these perform the DNS lookups when someone accesses the hosted website on your Master server. If the Secondary server accepts requests from anyone, even domains it isn't explicitly responsible for, then it is performing recursive lookups. A more secure configuration is for the Secondary servers to only accept lookups for its own Master servers.
- takeda64 14y agoThey set up a caching server for their organization so the DNS lookups are faster, but they forget to restrict the recursive queries only to their organization so anyone else can use them. That makes them work like Smurf ampliefiers (http://en.wikipedia.org/wiki/Smurf_attack http://en.wikipedia.org/wiki/Smurf_attack) in the past.
- bradleyland 14y agoThere are some benefits (incentives) to running your own DNS server with the ability to perform recursive queries, but best practices dictate that these servers should only accept queries from "trusted clients". So, it's not so much that there are incentives to run an open recursor as it is there are very few negative incentives to running an open DNS recursor. I keep highlighting the word "open", because the open state of a DNS server is often not an intentional decision. I'd speculate the most common reason for using DNS recursion is to allow a non-authoritative name server to return results for any query. This non-authoritative name server usually sits on a network that serves clients with low latency and high bandwidth, like a LAN. The network is typically private, but private is not always the same as secure/closed. Some benefits of running your own DNS are: * The ability to cache DNS lookup results (speed increase) * Placing the name server closer to clients (speed increase) * The ability to blacklist certain zones (security) And many more, most of which relate to control, speed, and security. The thing is, none of these advantages are related to running an "open" DNS with recursive queries enabled. I think the core problem is twofold: 1) Many amateur sysadmins don't recognize that running a name server with recursive queries enabled is a security issue. 2) Enabling recursion doesn't automatically require any configuration to secure the client-trust relationship. Unfortunately, I'm not really smart enough to propose any changes that would help the situation, but I think this represents a high-level overview of the most common problem scenario. EDIT: It's also worth noting that some DNS servers enable recursive queries by default. Anyone running their own DNS for their zone, but who don't have knowledge of the issues related to recursive DNS will likely be running an open DNS recursor as well. These are commonly servers at web hosts, which have much faster internet connections as well. So it's a matter of getting everyone on board for changing defaults.
- sikhnerd 14y agoI'm happy to see CloudFlare actually include some technical details in this post, though as always, I'd be happy to see more. It's always more interesting when we can follow along technically.
- omegant 14y agoSo, that´s why HN has been doing 503´s for the last week?, I am from Spain and it has been failing all the time.
- ceejayoz 14y agoHN isn't hosted on CloudFlare, and a slowdown wouldn't cause 503s like that. HN's likely just having server trouble.
- deleted 14y ago[deleted]
- calbear81 14y agoI wonder what the political implications of this type of "collateral damage" might be. Governments have recognized the need to defend against direct attacks on their networks and develop their own offensive attack capabilities from a national security perspective but I haven't seen the same level or response to these sorts of events. When the damage spills over to impacting services that tens of millions of people rely on and cause economic damage, should we treat this as the same as an attack on our critical infrastructure (electricity, water, etc.) like an act of terrorism? If that becomes the case, would it warrant the use of deadly force against the attackers?
- redblacktree 14y agoAll interesting questions, and now quite pressing ones.
- wglb 14y agoThis site http://www.internetpulse.net/ http://www.internetpulse.net/ is useful to check if you suspect a global slowdown.
- eah13 14y ago"..but first a bit about how the Internet works" My favorite part of a Cloudflare post.
- tptacek 14y agoWorth pointing out: I'm presuming that the 300gbps of reported traffic† was not generated by DNSSEC resolvers, because DNSSEC isn't that widely deployed. Which is bad, because DNSSEC dramatically increases the amplification effect you get from bouncing queries off open resolvers (the DNSSEC RRs are Big). Adam Langley notes on Twitter that Cloudflare reports 3k DNS responses, apparently containing the zone contents of RIPE.NET; I guess these were EDNS0 UDP AXFR requests? That's worse than DNSSEC. This has been one of Daniel Bernstein's big critiques of DNSSEC. It's not one of mine, but I'm still happy to see his argument validated. † (at a tier 1 Cloudflare doesn't have a business relationship with, which makes this kind of a "my cousin's best friend told me" number, but still)
- morsch 14y agoHow does this validate DJB's criticism? He's saying we shouldn't adopt DNSSEC because of traffic amplification. But we're already in an untenable situation with the amplification caused by bog standard DNS -- according to your quote, it's even worse than DNSSEC -- so we need to solve the problem anyway.
- tptacek 14y agoI am batting .000 on analysis for this situation and debated removing the comment and just replacing it with a link to DJB's talk. We don't have all the details but there's a notion that the attack already implicates DNSSEC because of RIPE's RRSIG records. I don't know, either way.
- morsch 14y agoOK. I was present at djb's CCC talk and also heard Dan Kaminsky's rebuttal, hence my interest. A link to DNSSEC would be interesting if not hing else.
- davidu 14y agoCorrect. DNSSEC just makes amplification worse. It's like: Do you want to be shot with 50 bullets or 100 bullets. DNSSEC is 100 bullets, regular DNS might be 50 bullets. Either way, you're going to die. I don't like DNSSEC, but amplification isn't my argument against it. The fact that it doesn't provide encryption, puts keys in the wrong hands, and is bizarrely complex for reasons that don't fit with the model of DNS is why I don't like DNSSEC.
- Bootvis 14y agoNews is that the dutch hoster CyberBunker[1] is responsible[2] for the attack. [1]: http://en.wikipedia.org/wiki/CyberBunker http://en.wikipedia.org/wiki/CyberBunker [2]: http://translate.google.com/translate?sl=nl&tl=en&js=n&prev=_t&hl=nl&ie=UTF-8&eotf=1&u=http%3A%2F%2Fwww.nu.nl%2Finternet%2F3382530%2Fstrafrechtelijk-onderzoek-aanvallen-nederlandse-cyberbunker.html&act=url http://translate.google.com/translate?sl=nl&tl=en&js...
- chiph 14y agoI'd still keep an open mind -- it could just as easily been someone seeing the opportunity to deflect blame away from themselves.
- speleding 14y agoWell, it's their own spokesman admitting it. Although they later rescinded it, probably after realising that there could very well be legal implications to it.
- summerdown2 14y agoI understand the issues with DNS reflection, but why are open resolvers the issue? Isn't the point of DNS to respond to requests with correct information? Surely if random people can't connect to DNS resolvers and get information, they can't surf the net either? Someone has to resolve DNS for people for the internet to function, don't they?
- yuliyp 14y agoDNS runs over UDP, which means the source of requests for information can be spoofed. Also, the amount of data of a response is significantly larger than the request, so you can use DNS resolvers to send significantly more data to a victim than you yourself need to generate by sending DNS queries with your victim as the source IP.
- summerdown2 14y agoYes, I understand the attack. My point is that somewhere, there have to be DNS servers that respond to public requests ... otherwise the internet will not work. Hence, some DNS servers have to be open. By saying it's openness that's the problem, we're blaming the victims, rather than the issue, which is that DNS is flawed. Simply moving to TCP would be better, surely?
- AdrenalinMd 14y agoUDP doesn't require a handshake hence is easy to spoof unlike TCP where a full-duplex connection must be established for a successful connection.
- summerdown2 14y agoYes, that's my point. If we move to TCP we fix the issue. At the moment I can't see how closing open servers is a real fix.
- pixl97 14y ago
- kronholm 14y agoFrom the article: "If the Internet felt a bit more sluggish for you over the last few days in Europe, this may be part of the reason why." Hm, as opposed to normal days, when our Internet is just normal sluggish. Not that fond of that phrasing. And I must be bored to even comment on that.
- voodoochilo 14y agoi can't see the attack. where is it? http://www.internettrafficreport.com http://www.internettrafficreport.com
- richardjordan 14y agoDoing a DDoS attack in the cause (however questionable the commitment to that cause is let's put it to one side for now) of Internet freedom is a ridiculous strategy. The more this sort of thing becomes inevitable the more TPTB will clamp down on such things and eventually we'll find ourselves on an Internet with far fewer freedoms and it'll all be far more locked down. Whether you like it or not society tends to react like high-school - when enough people abuse a privilege eventually that privilege gets taken away. You can argue that a free Internet is a right (as some do) but you won't win that argument in the public sphere if that right is used to stop everyone else from getting done what they want to do online.
- qu4z-2 14y agoI suspect the people DDoSing spamhaus aren't doing it for internet freedom.
- sigzero 14y agoIt wouldn't matter anyway. DDoS is not "freedom of speech".
- np422 14y agoOr perhaps they are? We really need places like cyberbunker to keep internet free and open. The day the the last piece of w4r3z, pr0n and other 1337 stuff is taken away from the internet the infrastructure would have to be in place to pretty much remove anything you want at will. I wonder what will be next thing to get removed after that? "First they came..."
- driverdan 14y agoCyberbunker hosts spammers. They're free to make that choice. Spamhaus runs an IP blacklist of known spammers and put Cyberbunker on that list. They're free to make that choice. Companies who don't like spammers subscribe to the blacklist and use it to block offenders. They are free to make that choice. I don't see where the internet is becoming less free and/or open.
- 14y ago
- ancarda 14y agoI feel like there's a shocking amount of laziness and incompetence rife in the industry. How else would so many open resolvers exist? It's like the thousands of nodes with default passwords that were used for the IPv4 census. How exactly do we combat this?
- andreasvc 14y agoI think ISPs should block things like mail servers and DNS servers on their clients by default, unless explicitly enabled and verified to be properly configured.
- kfcm 14y agoLaziness? Possibly. Incompetence? More likely. Incompetence due to having 45 #1 priorities and developing a deep understanding of secure configurations is a #3 priority? Most likely.
- dubcanada 14y agoI don't understand something... How is 300GBPS a lot? If we take London which has 8million and say roughly half of them are on the internet (4million). Wouldn't that mean that if everyone was using 78kbps we would reach 300 gbps(roughly)? I just don't understand how a tier1 or internet exchange router can only handle 100gbps. That seems extremely low to me considering I have like 1mbps for just my house?
- zjs 14y agoYour calculation is assuming that all of the traffic from those 4 million London-based users is travelling through LINX. While LINX is the IX for London, not all traffic originating from London would have to travel through it; Tier 2 and Tier 3 networks would route some portion of the traffic as well. This diagram from wikipedia shows some of the sorts of alternate routes that might be used: http://en.wikipedia.org/wiki/File:Internet_Connectivity_Distribution_%26_Core.svg http://en.wikipedia.org/wiki/File:Internet_Connectivity_Dist... As an aside: does anyone know of a good resource that gives an example of the rough percentage of traffic that would be handled in each of the various ways?
- nadinengland 14y agoI may have misunderstood this but I think this saying that a single IP (or endpoint) is receive this bandwidth. So there is this much going through the peer network AND regular internet use.
- lelandbatey 14y agoYou have 1mbps, but you very, very rarely actually use all of that. It doesn't actually really matter if everyone had 1Gbps internet connections, because most everyone is requesting data so infrequently that the points that must bear all the load can handle it. Pretty much, 100Gbps is about 100 thousand times your internet connection. So, a single 100Gbps line could handle 100 thousand people like you requesting a 1mb file at the EXACT same moment. Spread that out by even a few seconds and that router can handle way more people than that 100 thousand. This is a GROSS oversimplification, but the idea stands.
- mprovost 14y ago
- binary11 14y agoYes, my DNS server is listed on openresolvers.org. Here's why: I've a smallish home network, 5 machines, one of them running handful of VMs, some devices (printer, scanner). I wanted to have a local DNS server to name all these things, but mostly to learn about DNS and how to set up Bind. So i installed bind on a Debian machine, set up a local domain, promptly named .fia.intra. As an added benefit, I now had a local DNS caching server too, and since my machines use this as their primary DNS server, it needs to be recursive and not just respond to queries for my internal fia.intra. network. Now, all this is running on an internal 192.168.1.0 network, and bind is set up to only respond to queries from 192.168.1.0/24, and I'm behind an ADSL NAT gateway, so noone from outside should be able to query my internal DNS server. I ignorantly assumed that the ADSL modem wasn't completely broken and having a moronic way of operating. Now, I've not set a port forwarding rule in the modem that forwards port 53 to my internal DNS server, the only port forwarding rule I have is one for SSH. However, I have this setting on the ADSL modem: http://i.imgur.com/dlL9LKV.png http://i.imgur.com/dlL9LKV.png The ADSL modem as shipped from the ISP acts as DHCP server on the LAN side, as most modems would do, and by default the DHCP server hands out a DNS server that is my ISPs DNS server. I changed that to my internal DNS server, 192.168.1.20. In the image you will see the DHCP server isn't even enabled, I moved that to my same Debian machine and turned it off on the ADSL modem, but didn't erase the DNS settings. As it turns out, because of that setting the ADSL modem listens on port 53 on the WAN interface(which has a routable IP address), and forwards/reverse-NATs queries to my DNS server at 192.168.1.20. I'd never guessed it to do that. I did a "dig google.com @<my.public.ip>" from an EC2 instance I have, and indeed it responded nicely.. I've now changed the setting to read "Primary DNS Server= 0.0.0.0" and have verified I no longer respond to DNS queries from the WAN side. Stuff sucks.
- AdrenalinMd 14y agoHold on, isn't it the time to force DNS to be TCP only ?
- marshray 14y agoThat'd likely result in increased traffic and slowdowns even in normal cases.
- graylights 14y agoNo. Currently a significant amount of latency in opening a web page is the DNS resolution (for half a dozen domains). TCP adds a lot of overhead compared to UDP. But a case can be made that large requests should be TCP only.
- lucb1e 14y ago> TCP adds a lot of overhead compared to UDP. Not if you simply keep a TCP connection open and use SYN cookies on the servers. Many DNS servers already support TCP (though I'm pretty sure you need a new connection for every request).
- colbyolson 14y agoI thought this was an excellent writeup and I would like to learn more more. Are there any recommended books on learning about the Internet/DNS on a global scale?
- devdas 14y agohttp://www.amazon.com/Cisco-Essentials-Press-Networking-Technology/dp/1587050412 http://www.amazon.com/Cisco-Essentials-Press-Networking-Tech... (Networking) http://www.amazon.com/DNS-BIND-5th-Cricket-Liu/dp/0596100574 http://www.amazon.com/DNS-BIND-5th-Cricket-Liu/dp/0596100574 (DNS) There are always the standards texts, Computer Networks by Tannenbaum and Internetworking by Radia Perlman for the theory.
- vermontdevil 14y agoNo wonder I had difficulty accessing Google a few times during that time period.
- senthilnayagam 14y agoI don't think the attack has stopped, it will come back even bigger and would take down many networks. Hope that kind of pubic outcry and media visibility will get the networks and governments to take notice and fix the core Internet infrastructure of the known vulnerabilities
- senthilnayagam 14y agohttp://m.cnet.com/news/egypts-military-arrests-divers-cutting-undersea-internet-cables/57576689 http://m.cnet.com/news/egypts-military-arrests-divers-cuttin... now it feels like a conspiracy to takedown Internet
- davidschein 14y agoNot nearly almost: http://gizmodo.com/5992652/that-internet-war-apocalypse-is-a-lie http://gizmodo.com/5992652/that-internet-war-apocalypse-is-a...
- notatoad 14y agoI don't really know about these things, but I know enough to trust cloudflare over gawker.
- drchaos 14y agoI'm not a networking expert, but how would turning off recursive DNS queries mitigate this kind of attack? A nameserver must still answer queries for the domains it is authoritative for, so what prevents the bad guys from using only authoritative queries for their attack? Wouldn't it be much better to just add some rate limiting to every DNS (recursive or not)? On a side note, I think that especially in times where messing with DNS is used as a censorship tool by a lot of governments and regulators, there is some value in being able to ask someone else's DNS for any domain, but that's a different issue.
- uxp 14y agoI'm not a networking expert either, but I do believe the recursive nature turns this amplification DDoS to just a "normal" DDoS where the only target would be the nameservers of the target service. At the end of the day, if there wasn't a single nameserver that was turning around and asking 2, 10, or 100 other nameservers the same fraudulent question they didn't have the answer to, the only thing you could do with the same exact attack would be to take out someone's authoritative servers. No collateral damage by slowing down the internet connections of home users in California when the attack is being targeted at some server in Germany.
- drchaos 14y agoI don't think the nameserver (or the upstream NS) is the target of the attack, but the (spoofed) IP which appears to be sending the queries: * Attacker sends (small) query to a lot of resolvers, spoofing the source adress to be the IP of the target * Each NS replies with a (large) response, thus flooding the target with a lot of data As long as there is no rate limiting in the nameservers used for the attack, this would work regardless of whether the answer is authoritative or not.
- criley 14y agoGizmodo is calling out Cloudflare's claims that this affected anything more than Dutch networks: http://gizmodo.com/5992652 http://gizmodo.com/5992652 They point out, for example, that the IX's in question routinely see 2.0+Tbps peaks, so a 0.3Tbps attack would not be likely to shake a single IX, little like "the internet" itself. Interesting rebuttal, although certainly not comprehensive.
- macros 14y agoAkamai has more bandwidth at AMS-IX than this entire attack.
- TranceMan 14y agoIndeed they should, Cloudflare offers to protect you [and charge you for the privilege] from DDoS attacks like this. If they really know how the Internet works they shouldn't make claims like this.....
- guiambros 14y agoThat's called marketing. They are crafting the stories methodically (and successfully I'd say, given the number of times we all talk about CloudFlare on HN) to drive more exposure to their brand. It's too optimistic and hyperbolic sometimes, but no really different than any product announcement from Apple or Facebook. In all fairness to them, a positive side effect is that we're all discussing now how to solve the root cause of this decades-old - but still threatening - problem (open networks and dns attacks). I guess it will really take an apocalyptic event to convince millions of operators to configure better their own networks. This is not the first time CloudFlare uses hyperbolic headlines. Case in point: "Why Google Went Offline Today and a Bit about How the Internet Works" https://news.ycombinator.com/item?id=4747910 https://news.ycombinator.com/item?id=4747910
- ubercow13 14y agoHow is that at all hyperbolic?
- propercoil 14y agonic.fr is down so most .fr domains are down due to unresolved hostname.
- sabat 14y agoFact: all, or almost all, of these DoS attacks originate from Microsoft-based systems that have been compromised. Fact: Microsft has created and sold multiple operating systems that are vulnerable to simple attacks resulting in DoS drones. Fact: Microsoft's response in fixing vulnerabilities has frequently been lax. Fact: Microsoft has never been held accountable for any of the attacks that it directly contributes to. Why are governments and corporations not directly suing Microsoft back to the stoneage? Microsoft, and Microsoft alone, is responsible for shipping widely used operating systems that are highly susceptible to being owned and exploited by botnets. Why is it not being held accountable for its obvious negligence?
- deleted 14y ago[deleted]
- jwr 14y agoWhat I don't understand is why someone doesn't finally write a piece of malware that destroys botnets? These unmaintained machines cause the entire world so much grief. It doesn't have to be mean and destroy data, just incapacitate the machines and force the users to upgrade.
- brazzy 14y agoExisting botnet malware already protects itself against removal or interference from other malware and anti-virus software. And it usually has auto-update functionality. It would just be extended to defend against this new "anti-malware" as well. Besides, if this hypothetical "anti-malware" actually incapacitated machines, it would be highly illegal itself.
- k__ 14y ago"Tier 1 networks don't buy bandwidth from anyone, so the majority of the weight of the attack ended up being carried by them." "We're proud of how our network held up under such a massive attack." wat?!
- ateev23 14y agoMine was OK. In India
- munimkazia 14y agoUnfortunately, we in India are severely affected by the Mediterranean cable cut, which coincidentally also happened at roughly the same time
- nitins 14y agoThat Internet War Apocalypse Is a Lie! http://gizmodo.com/5992652/that-internet-war-apocalypse-is-a-lie http://gizmodo.com/5992652/that-internet-war-apocalypse-is-a...
- chisto 14y agoToday one guy in my local news (Monterrey, Mexico) talk about it, that "tech guy" said that netflix and other services were intermitent or fail to access, and also that this "war" were between cyberbunker and Spamhaus. I think this is not completly true, but he spoke if this kind of things would be the next kind of wars in the following years and recommendo to the people a good antivirus and a firewall. I really admire what cloudflare did, and help the not too tech guys to understand how this things works, if cloudflare were promoting himself with this posts well they need to eat and educate their children is normal their behavior.
- trumbitta2 14y agoAnd here's another interesting one from the past (7 / 13 root servers got shutdown or blocked): http://c.root-servers.org/october21.txt http://c.root-servers.org/october21.txt