* Posts by Peter Stevens

3 publicly visible posts • joined 7 Dec 2007

This major internet routing blunder took A WEEK to fix. Why so long? It was IPv6 – and no one really noticed

Peter Stevens

It's not surprising it wasn't noticed. Routing follows the most specific route, so the cloudflare incident was obvious because Cloudflare annouced a /20 and somebody else announced a more specific /21. In this case it's the opposite, everything in 2400::/12 that's actually in use is already announced by a more specific route, somewhere around /29 to /48. The only affected addresses would be ones not in use.

Nobody noticed the unused addresses in a large IPv6 block going missing because they weren't in use so nobody was affected.

Hijacking huge chunks of the internet - a new How To

Peter Stevens

How do I tell.

So before the attack I'm routing my data over a potentially untrustworthy network. After the attack I'm routing my data over a different potentially untrustworthy network. Did I miss an announcement that the Internet was suddenly fundamentally trustworthy somewhere ?

The world's most fantastic, imaginary server start-up

Peter Stevens

The Mac Mini

We host lots of Mac Minis. 35-40W for a complete Core2Duo server, Gig Ethernet, small form factor so they stack quite well. We also do the AppleTV, at 16-20W it's half the performance/W of the Mac Mini, but as a dedicated server you're unlikely to get anything with a lower current draw.

http://www.mythic-beasts.com/resources/macmini/