Banned!
The other day I clicked on a link to Slashdot, and got a nice page with the title “BANNED!”:
Either your network or ip address has been banned from Slashdot
…due to script flooding that originated from your network or ip address — or this IP might have been used to post comments designed to break web browser rendering. Or you crawled us with a rude robot, especially one that doesn’t understand RFCs very well.
If you feel that this is unwarranted, feel free to include your IP address (203.147.0.42) in the subject of an email, and we will examine why there is a ban. If you fail to include the IP address (again, in the subject!), then your message will be deleted and ignored. I mean come on, we’re good, we’re not psychic.
[snipped a further dozen paragraphs of blah blah]
It didn’t really bother me, since I don’t care much for Slashdot anyway. Accusing me of being rude and claiming to be good themselves in one breath is the sort of thing I could expect from them.
But this morning, an attempt to search for something on Google got me a 403 Forbidden error:
We’re sorry…
… but we can’t process your request right now. A computer virus or spyware application is sending us automated requests, and it appears that your computer or network has been infected.
We’ll restore your access as quickly as possible, so try again soon. In the meantime, you might want to run a virus checker or spyware remover to make sure that your computer is free of viruses and other spurious software.
We apologize for the inconvenience, and hope we’ll see you again on Google.
Fortunately, there’s plenty of other search engines.
But it does point out how vulnerable the Internet in its present incarnation is. I know for a fact that my network hasn’t been hitting anybody’s server. My ADSL router has a built-in NAT, which allows me to see each and every active connection. But even if I wasn’t that smart, the idle state of the LED on the router that indicates traffic speaks volumes.
The router’s IP address is assigned by my ISP through DHCP. In English, that means that I get a new address every time I turn the thing on, as does everybody else using that ISP. It also means that the IP address I have today was used by somebody else yesterday.
And there lies the problem. The previous user of the IP was probably used by somebody who doesn’t care much for computer hygiene, and has ended up with a zombie computer. To protect themselves, Google blocked the IP. Since Slashdot has told me I’ve been banned on several occasions, they probably blocked the whole subnet. Because IP addresses are shared, careless behavior by some spoils the party for everybody.
The solution is of course to use static IP addresses, which can be easily blocked without collateral damage. But that won’t happen until IPv6 is rolled out on a major scale, since there simply aren’t enough IP addresses to go around for everybody (and their phone, and their iPod, and their wristwatch).