A short history of Dibbler
The design goals were simple: the new DHCP software should be easy to use, not be restricted by licensing, and help popularize IPv6. That’s how the Dibbler project came to be.
One of the core assumptions was to support IPv6 only. The reason was obvious — speed up the transition to IPv6, while making sure there were no strings attached. And it really worked! The software doesn’t have any ability to do anything with IPv4. It was a bit naive and idealistic, but it was a student project, so there was nobody to do a reality check for me….
Know more @ what is DHCP and how it works?
Somewhere around 2006, an email came that invited me to what became the first of a series of DHCPv6 ‘bake-off’ meetings. The idea was to bring in DHCPv6 developers from different companies to meet in one place, do interoperability tests, and discuss the issues discovered. I was flabbergasted and terrified at the same time.
Back then, I was a recent university graduate and some guy from the US invited me to fly to Amsterdam to test my software. The other engineers participating were coming from organizations such as Cisco, Microsoft, Sun, and ISC. Suddenly, the whole experiment became much more serious. I still remember the angst and doubts — how could an essentially overgrown student project possibly keep pace with giants like Cisco or Microsoft?
|Vote for this post
Bring it to the Main Page