From: Justin Carlson <justincarlson@cmu.edu>
To: abdij.bhat@kshema.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Level DHCP Versus udhcp
Date: 15 Mar 2002 14:42:52 -0500 [thread overview]
Message-ID: <1016221377.7606.5.camel@gs256.sp.cs.cmu.edu> (raw)
In-Reply-To: <001c01c1cc56$b38a3ec0$8134aa88@cam.pace.co.uk>
In-Reply-To: <001c01c1cc56$b38a3ec0$8134aa88@cam.pace.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
On Fri, 2002-03-15 at 14:22, Abdij Bhat wrote:
> Hi,
> I am deploying a Linux Network Stack. I am supposed to use a stable, fully
> featured, RFC compliant, small memory foot-print DHCP client for an embedded
> system. We had converged on udhcp for the client. But I have found that
> there is a DCHP client implemented in the Linux Kernel ( Version 2.2.x or
> later ). This I believe can be configured by choosing the "Kernel level
> autoconfiguration".
> I have however practically no documentation on the Kernel DHCP Client. I do
> not know how buggy it is, is it a fully featured DHCP client or is it just a
> boot level DHCP client used for remote booting etc.
> Can some body help me with this. I believe it is used only for the remote
> booting, with the documentation currently available to me. How correct am I?
> Can I replace the udhcp client with this one? How much of a change will I
> need to do for the replacement?
It sounds like the kernel DHCP client is not what you want. It's really
intended for situations where you need to get dynamically assigned IP
information for a machine before you're far enough in the bootstrap to
do it in userland.
The most common situation for this that comes to mind is mounting your
root filesystem over NFS. At least, that's the only situation for which
I've needed it.
If, as you imply, you really need a full-featured DHCP client, you
should be using something in userland. The kernel-level one doesn't
(last I checked) handle DHCP details like temporarly IP address leases
and such; that's not the intention of having that option in the kernel.
-Justin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-03-15 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 19:22 Abdij Bhat
2002-03-15 19:42 ` Justin Carlson [this message]
2002-03-15 20:04 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1016221377.7606.5.camel@gs256.sp.cs.cmu.edu \
--to=justincarlson@cmu.edu \
--cc=abdij.bhat@kshema.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®