Skip to main content

DOS, Backscatter, ATT and 4chan

If I’ve got the story straight, it goes something like this:

  1. 4chan.org is subject to a DDOS attack.
  2. 4chan attempts to block the DOS, and in the process, unintentionally DOS’s one or more of ATT customers.
  3. ATT ‘blocks’ 4chan.
  4. The world comes to and end.

Forget network neutrality, evil empires, Haliburton, black helicopters and aliens from area 51. Let’s try for a simple explanation, assuming that nobody is evil and everyone is incompetent. It’s speculative, but has the advantage of holding to Occams Razor far better than the other speculative explanations floating around.

  1. 4chan gets DDOS’d, presumably from spoofed IP addresses. For high profile sites, that’s a normal thing. For low profile sites with large address spaces (us), that’s a normal thing. The sun rises in the east, someone on the Internet gets DDOS’d from spoofed addresses. It’s been that way for a decade or so. Life goes on. Get used to it. If you think you can run a high profile site and not get DOS’d, they perhaps you need to rethink your career. Try accounting. Accountants rarely get DOS’d from spoofed addresses.
  2. 4chan responds by filtering packets. Unfortunately they appear to have filtered in a manner that sent ICMP destination unreachable or perhaps TCP RST or ACK packets back at the spoofed IP addresses. It’s called backscatter.
  3. One of the spoofed addresses is an ATT customer. From ATT’s point of view they see a DOS sourced from 4chan. They don’t know or care if it’s real or backscatter. ATT puts up with the DOS for awhile, weeks perhaps, and finally says screw it – null route the dumb SOB’s.
  4. The Internet panics, providing amusing news for what otherwise would have been a slow news weekend.

Let’s pretend you are an ATT operator or engineer.

If ATT’s ops had decided to follow up with the owner of the IP address, there is no reason the think they’d have got very far. Presumably someone like ATT is subjected to DDOS’s more or less continuously, so to expect them to follow up on every one is pretty unreasonable.

As of today, the IP address for the 4chan web server’s Whois points to a generic hosting provider with no rwhois. A PTR lookup ends in ‘Server Failed’. Even if they had followed up and tracked it back to 4chan, the whois for 4chan.org points at a generic Network Solutions phone number with no other useful information. Surfing to the IP would have worked, but the only contact info on the web site is a few e-mail addresses, and surfing to an unknown web site to see who owns it is pretty unsafe now days. There is no reason for them to think that 4chan is anything other than a mickey mouse, incompetently run BBS that’s badly hacked and originating a DOS against them. It’s not like they haven’t seen that a hundred times before. Back in the day when I though it would matter, I followed up on a thousand-odd hacked web servers that port scanned, DOS’d or tried to hack me. Twenty or so per day for a couple or more years. Trust me, it’s a bloody pain.

ATT’s network ops see a DOS from an IP address aimed at one of their  customers. They null route it. It goes away. They move on to the next crisis.

That’s what I’d do, and that’s what I’ve done a hundred times over the last decade.

The 4chan crowd think they are famous, and in their own minds they no doubt are, but I’ll bet that the vast majority of network engineers don’t know or care who 4chan is or what it does. They didn’t have a clue who 4chan is until Monday am., when they saw themselves in the news.

Comments

  1. And once again, it NEVER fails with the incessant lying, as lying is a way of life for these hacker creeps. I salute AT&T for blocking viruses, trojans and nasty spider scripts, as that is what the REAL truth is as to WHY AT&T has flashed the middle finger [blocked] to 4 Chan. Why should AT&T waste time and energy in dealing with viruses, trojans and uncontrollable script programs emanating from the 4 Chan site?

    I don't condone censorship and I certainly don't condone lies "in the name of lulz". The only thing 4 Chan has proven again and again, is that they are infantile and violent. A bunch of two year olds who go on tirades. And just like an out of control two year old, they need some REAL hard slaps from the school of hard knocks.

    Any consequences or denial of internet access to AT&T customers due to NAZI actions emanating from 4 Chan [or any other hacker creeps for that matter], I pray that they are caught, rounded up, prosecuted beyond the extent of the law, thrown in a windowless cell and locked up forever until the day they die.

    I commend AT&T for taking the step forward and I sincerely hope that other ISP'S follow suit ASAP. ENOUGH IS ENOUGH. Hackers cause destruction, chaos, waste everyones time and energy. Normal people on the net are SICK AND TIRED of these two year old tantrum antics that 4 Chan displays on a daily basis. These hacker creeps really and truly need to GROW THE F*** UP.

    ReplyDelete

Post a Comment

Popular posts from this blog

Cargo Cult System Administration

“imitate the superficial exterior of a process or system without having any understanding of the underlying substance” --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:Failing to understand the difference between necessary and sufficient. A daily backup is necessary, b…

Ad-Hoc Verses Structured System Management

Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to …

The Cloud – Provider Failure Modes

In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:
In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. The…