I have a few token Linux clients that are getting their IPs from a Windows
2000 DHCP. Unfortunately, the Linux clients are sending out repeat DHCP
Inform packets, which by inspection in a sniffer are requesting these
parameters:

1 = Subnet Mask
3 = Router
6 = Domain Name Server
12 = Host Name
15 = Domain Name
17 = Root Path
23 = Default IP Time-to-Live
28 = Broadcast Address
29 = Perform Mask Discovery
31 = Perform Router Discover
33 = Static Route
40 = Network Information Service Domain
41 = Network Information Service Servers
42 = Network Time Protocol Servers

Which of these parameters are so essential that the client will just not
give up until it gets them?

How should I provision any of these on the DHCP server in order to have the
Linux client see them as in the correct class for its consumption?

--
Will