*** From dhcp-server -- To unsubscribe, see the end of this message. ***
If you are a vendor - that is, you are supplying a DHCP client that
will configure your device, then you should send a vendor identifier
option containing information about the device. You should define a
set of vendor-specific options, and request the vendor-specific
information option in your parameter request list.
You can then define an option space for your device in the dhcp
server, define options for that device, and arrange for the
information to be sent to the device. RFC2132 explains how the
vendor-specific options work. The dhcpd.conf man page explains how to
configure the server to do this - search for VENDOR ENCAPSULATED
OPTIONS. This is only supported in the 3.0 release of the ISC DHCP
server.
You should not allocate a code directly out of the regular DHCP option
space - if you do, chances are that it'll get stomped later on,
because we're very short on option codes. If you want to create a
standard option or two for IP telephony, you are welcome to submit a
standard to the working group and try to get option codes assigned to
you, but if these option codes are specific to your product, you're
much better off just using the vendor-specific information option.
_MelloN_
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
