Date: Tue, 29 Jul 2003 22:18:05 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: mb@imp.ch Cc: current@freebsd.org Subject: Re: STEP 2, fixing dhclient behaviour with multiple interfaces Message-ID: <20030729.221805.113566203.imp@bsdimp.com> In-Reply-To: <20030730013027.D25188@cvs.imp.ch> References: <Pine.NEB.3.96L.1030729173653.78063D-100000@fledge.watson.org> <20030730013027.D25188@cvs.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20030730013027.D25188@cvs.imp.ch>
Martin Blapp <mb@imp.ch> writes:
:
: Hi Folks,
:
: I had a closer loom at the OMAPI stuff in dhclient.
:
: Just to say, I'm very disappointed. The only objects that exist are:
: "control" and "interface". The later is not inplemented at all.
: It pretends to work, but if you look at the source there are
: stubs only :P.
:
: "control" does only release leases and exit (state 2), I never managed to make
: dhclient sleep (state 3) and wake up (state 2).
:
: It seems that the whole implementation is only a proof of concept
: and not very functional at all, at least for the client side, dhcpd
: may be different.
:
: I'll think about how we can solve this differently. This
: really sucks !
That's why I start/kill dhclient from pccard_ether.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030729.221805.113566203.imp>