problem with dhcp setup
Ted Lemon
Ted.Lemon at nominum.com
Tue Jun 19 19:05:10 UTC 2007
On Jun 19, 2007, at 10:53 AM, John Jason Brzozowski wrote:
> A client MAY include an Option Request option in a Solicit, Request,
> Renew, Rebind, Confirm or Information-request message to inform the
> server about options the client wants the server to send to the
> client. A server MAY include an Option Request option in a
> Reconfigure option to indicate which options the client should
> request from the server.
>
> It is only a MAY, if we really wanted to force this shouldn't it
> have been a
> MUST?
Oh, that's right. Sorry, it's been a long time since I looked at
that part of the spec. So if you send an ORO, then the server can't
send you anything you didn't ask for in the ORO. If you don't send
an ORO, it can send you whatever it wants. But if you send an ORO
and don't request the right stuff, then what I said stands - you
really don't want the server to volunteer options in that case.
Personally I think a client that doesn't send an ORO is going to be
an interop nightmare, though. Clients should really explicitly
request the options they want.
More information about the dhcp-users
mailing list