from the quill of "Mai Jianning" <[EMAIL PROTECTED]> on scroll
<001a01bf77cd$f5606700$01010108@tintin>
> Why dhcp-client is not used as default? Who decide which package to
> choose as DEFAULT?
There is a technical and I think policy problem with dhclient. First
the technical problem: currently, dhclient manages all interfaces with
one instance of the program, so integrating it into ifup/ifdown scripts
is impossible if you want to control more than one interface. Just this
weekend I finished and submitted code to the ISC to use the new OMAPI
interface in dhclient so that a utility can be used to tell it to add
and remove interfaces from it's control, on the fly. The client is
started with:
# dhclient -n
and then to have dhclient obtain an address on a given interface, say
eth0 you run:
# dhclient-if up eth0
To have dhclient release an address on an interface you would run:
# dhclient-if down eth0
Which will send a DHCPRELEASE and deconfigure the interface (the last
part is done by the shell script called from dhclient so customization
is easy).
The "dhclient-if" program (written but not formalized yet -- I am
waiting for direction on it's place within the package from Ted Lemon)
could be used in ifup and ifdown scripts.
The other current issue I believe is that dhcp-3.0 is still in beta. I
got the impression the last time I went down this road that Mandrake do
not include "beta" releases in their distribution. Silly, IMHO because
the ISC's "beta" is better than a lot of peoples "FCS".
b.
--
Brian J. Murrell InterLinx Support Services, Inc.
North Vancouver, B.C. 604 983 UNIX
Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD
