Re: [Etherboot-developers] Dropping DHCP messgaes
Brought to you by:
marty_connor,
stefanhajnoczi
|
From: Peter L. <P.L...@sy...> - 2001-11-04 16:19:29
|
> Ok, in first32.c of mknbi, I modify it so that is also extract the =
> nisdomain (rfc1533 tag 40) from the bootp messages. But when using dhc=
p =
> I find the nisdomain tag is missing or empty string. What is the =
> problem? It seems the messages are sent by the dhcp server but the =
> client cannot receive it? Is there a bug in the current ISC dhcpd that =
> use non-standard vendor tag number for nisdomain or it is dropped by =
> etherboot? I just want to make sure what's happening.... Thanks.
Are you using "option dhcp-parameter-request-list" in dhcpd.conf? If so
is the nisdomain code included?
Are you sending nisdomain in a parameter request list from Etherboot?
RFC2132 says...
9.8. Parameter Request List
This option is used by a DHCP client to request values for specified
configuration parameters. The list of requested parameters is
specified as n octets, where each octet is a valid DHCP option code
as defined in this document.
The client MAY list the options in order of preference. The DHCP
server is not required to return the options in the requested order,
but MUST try to insert the requested options in the order requested
by the client.
The code for this option is 55. Its minimum length is 1.
Code Len Option Codes
+-----+-----+-----+-----+---
| 55 | n | c1 | c2 | ...
+-----+-----+-----+-----+---
|