[Bug 192413] libdhcp : IPv6 and IPv4 DHCP client and network configuration library API

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: libdhcp : IPv6 and IPv4 DHCP client and network configuration library API


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192413





------- Additional Comments From dcantrel at redhat.com  2006-05-24 17:04 EST -------
(In reply to comment #26)
> In reply to Comment #25 From David Cantrell (dcantrel at redhat.com) on 2006-05-24
> 16:18 EST:
> 
> libdhcp   DOES NOT REQUIRE ANY DHCP CLIENTS OR EXEC ANY DHCP CLIENT PROCESS .

It doesn't?  Perhaps I'm just drowning in a sea of code then.  At the top of
your README file, I see this:

LIBDHCP enables programs to invoke the ISC dhclient (IPv4 DHCP) and DHCPv6
client (IPv6 DHCP) libraries, libdhcp4client and libdhcp6client, within one
process, and to use the lease objects returned to configure network interface
parameters.

I read the two patches to the dhcp package before looking at libdhcp (because I
couldn't get libdhcp source before seeing the dhcp patches).  While I don't hack
on ISC dhcp, I do know that dhclient was it for a while.  There was no library.
 And looking at the code now, I see there's still no library.  So this is why I
assumed libdhcp4client and libdhcp6client just exec the appropriate client and
send info back to libdhcp.

Looking at /usr/include/dhcp4client/isc-dhcp/dhcp4client.h and then the one for
IPv6, I only see one function prototype and it looks like an entry point for
execing the client daemon to me.

If I am going to use this, I'd like the API explained better than what I see in
the README.  Is libnl required?  I don't like libnl or libnetlink because both
are pretty piss poor 80% solutions.

> Please read the README file shipped in the distribution.

I did.  Many times.  Please don't make long lines.
 
> libdhcp RUNS the DHCP client code in same process as the invoking program,
> from libraries linked into to the invoker.
> 
> That way, we do not have to develop and maintain DHCP and DHCPv6 client
> protocol implementations from scratch - we can re-use the same code
> used for the FC dhclient and dhcp6c programs, but run from within
> one process.

That makes sense to me and that's certainly the right way to go.  I'm just not
seeing that when I look at ALL of these packages and source files.  Too many
things with 'dhc' in the name.
 
> The DHCP and DHCPv6 protocols are separate protocols, with separate ports,
> message types and options.

Right.

> A drop-in replacement for pump is now being tested and will be
> submitted today.

Sounds good.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.