The Little Network That Could: Which IPv6 Address?

An IPv6 addressing detour My next post about The Little Network That Could (TLNTC) was going to be about IPv6 addressing plans - and this post is definitely about IPv6 addressing - but before we can lay out a plan, there's something more...

Pain points: MLD snooping on Linux bridges

It seems that MLD snooping on Linux bridges has broken various parts of IPv6 connectivity over the past 10 years or so. Initial reports of bugs were from 2013, when having MLD snooping enabled on the bridge broke neighbour discovery (breaking...

Pain points. Or, IPv6-only: the ugly bits

Alongside my tech nibbles posts, I'm going to add another type of short post which chronicles the difficulties I've encountered in trying to achieve my IPv6-only end state. These posts may contain somewhat spicy opinions 🌶️ or ranting 🤬. Mostly I...

The Little Network That Could

(Credit: Flickr) Gather 'round, folks - Grandpa has a story to tell. (OK, I'm not a grandpa and I don't expect to be one any time soon, but as I've journeyed back in my memory to write this post, I sure feel old...) For as long as it has been...

NAT is evil, but not bad

2011-09-20: Edited to add section about IPv6 options; minor cleanup; references added. This is kind of a follow-on from my post about the subnet addressing design differences between IPv4 and IPv6. Recently, Tom Hollingsworth started a little...

Pondering subnet allocations

Edit, 2011-05-03: To all those poor souls who have been directed here by Google in their search for best practices on IPv4 and/or IPv6 subnet allocations (or worse, the HP A5500's NAT capabilities), please accept my sincere apologies.  This page...