forked from tomaszmrugalski/dibbler
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathRELNOTES
79 lines (70 loc) · 4.38 KB
/
RELNOTES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
Dibbler 1.0.2 Release Candidate 1 [2017-07-03]
------------------------------------------------
This is the first release candidate of the 1.0.2 release of the
Dibbler software. This update contains a number of fixes.
The Dibbler project started in 2003 an a double master thesis of
Marek Senderski and mine. We graduated, Marek left and I continued
the development for a while. First users appeared and the whole thing
took off as a real project. Dibbler was always my hobby project and
for most of the time it was a one man project. There were several
contributors who were interested in certain aspects and contributed
great deal of patches, but once the functionality was there, they
usually left after a while. Dibbler was the reason I was invited to
several conferences and DHCP inter-op events. One of the things that
appeared on the horizon was IETF. If you're not familiar with it,
this is the organization that defines RFC documents that govern how
Internet works. Somehow I got sucked into this world and soon
realized that if I do a good job with the code I can make one
implementation better, but if I write a better Internet standard, I
can make all of them better.
Things have changed significantly for me in 2011. Internet Systems
Consortium, a small non-profit company from Silicon Valley noticed my
work on Dibbler and DHCPv6 standardization and offered my a job.
DHCPv6 used to be my hobby and it became my full time job. This
turned my whole perspective upside down. The main goal of Dibbler
project was to stimulate IPv6 adoption. You may perhaps noticed that
Dibbler does everything in IPv6-only manner. Legacy technologies,
such as IPv4, are not and were never supported. This was nice, but
somewhat idealistic approach.
You may have noticed that dibbler's development slowed down to almost
nothing in the recent years. Sadly, after over 14 years of
development, I no longer have time to continue development of
Dibbler. This is the primary reason, but there are others. Dibbler
started as my master thesis and I was learning C++ back then. Some of
the design assumptions are ridiculous, the code is not that good
and updating it would require huge investement of time. And time is
a precious commodity these days. Also, over the years many use cases
faded into obscurity and new scenarios emerged. Handling some of them
properly would require a huge refactoring that I'm unwilling to
undertake.
After 1.0.2 is released, the server component will be deprecated. The
Kea software (http://kea.isc.org) provides a high quality open source
DHCPv6 server that is of superior quality, is much more modern and
has more features. Please migrate to Kea, if you are interested in
the server component.
If you're interested in the client component of Dibbler, the situation
is a bit more blurry. Kea does not yet feature a client. ISC may
implement a client if funding for it will appear. ISC DHCP, another
implementation, features a client, but it is often difficult to use and
definitely complex to extend. But given that Dibbler will no longer get
any serious development, it may be a viable alternative, if you want to
migrate away from dibbler client and Kea client is not yet available.
However, if you like how dibbler operates, this may be of interest to
you. Proposal for a new, modern DHCPv6 client will be announced in the
near future. The details are still sketchy at the moment, but it seems
it will be provide RESTful interface, will provide better handling of
dynamic changes - like being able to tell the client to request more
addresses, more prefixes, release now, do reconfiguration, perhaps tell
it that MAC address has changed and it must assume a new identity -
that's a big deal for privacy oriented solutions and more. News will
appear on dibbler-users and kea-dev mailing lists. Stay tuned.
If you find bugs, please report them on http://klub.com.pl/bugzilla/,
but given the above, they may not be addressed. Appropriate links are
on project website: http://klub.com.pl/dhcpv6/. If you need help or
want to share your thoughts, take a look at one of two mailing lists:
dibbler or dibbler-devel. Please do not contact author directly,
unless you want to report security issues or discuss confidential
matters.
Thank you for using Dibbler.
Tomek Mrugalski,
author