Option 252 don't work
Niall.oReilly at ucd.ie
Tue Feb 12 10:09:01 UTC 2008
On 11 Feb 2008, at 18:45, Phibee Network Operation Center wrote:
> Where i ca find this probleme ?
On 11 Feb 2008, at 20:46, David W. Hankins wrote:
> It may be the client digests option 252 but they do not put it on
> the Parameter Request List ("PRL"). You can work around this by
> over-riding the PRL in the server and tacking 252 on the end;
> option dhcp-parameter-request-list =
> concat(option dhcp-parameter-request-list, fc);
This may do the trick, but it depends on how your client
application behaves. From what I've seen in our logs, the
browser isn't involved in the network-parameter-acquisition
transaction (DISCOVER/OFFER/REQUEST/ACK), but needs a
subsequent application-parameter-acquisition one (INFORM/ACK).
I didn't see any DHCPINFORM request in the log fragments from
Phibee NOC. Are there any? If not, then I would expect that
the client application (browser, or whatever) simply isn't
sending the request to the DHCP server.
I hope this helps.
University College Dublin IT Services
PGP key ID: AE995ED9 (see www.pgp.net)
Fingerprint: 23DC C6DE 8874 2432 2BE0 3905 7987 E48D AE99 5ED9
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
More information about the dhcp-users