[ I Cc ltsp-discuss, but let's take this back to etherboot-users. ] > I posted this question on the etherboot mailing list but did not get any > response; I am hoping someone here will have some answer.
Sorry that you didn't get a quick answer, but people are busy and your subject line is misleading. Anyone looking at just the subject is justified in saying "Duh, of course". The DHCP options themselves defined by RFCs, not dhcp server versions, so etherboot supports *any* RFC compliant dhcp server implementation. The recent ISC dhcpd implementation is v3 and while it has improved option handling, this does not affect the options themselves. > Does the etherboot ROM image support DHCP V3 options? Namely I am > interested in passing what is called the "DHCP Class ID" where a client > passes a parameter that the DHCP V3 server recognizes and assign some > stuff based on it. We need it to use it with Win2k DHCP User class > options. A good question, if not the one your subject line described. :) First, you can differentiate Etherboot from other dhcp traffic using the *Vendor* Class ID, which encodes the string "Etherboot" and a version number in every request. Is there any reason you cannot use this? If the MS dhcp server likes to use *User* Class IDs then this is interesting and probably helpful to those in a MS environment. > I looked at the parameters that are stored in the image but I did not > see a thing other than the vendor class id which based on the docs is > the string "etherboot" Well, that pretty much answers your question - no. > Can I add parameters to etherboot image similar to the one above that > the client can pass? I started to look at this a few weeks ago. You'll have to hack the source code - and adding UCI has a complication in that it is NOT a single string (like the VCI). From RFC3004... This option MAY carry multiple User Classes. Servers may interpret the meanings of multiple class specifications in an implementation dependent or configuration dependent manner, and so the use of multiple classes by a DHCP client should be based on the specific server implementation and configuration which will be used to process that User class option. . . . DHCP clients implementing this option SHOULD allow users to enter one or more user class values. The multiple values are stored in DHCP's normal size/value list format, so to *send* the UCI, etherboot needs to be given the encoded options when it is built. [ Recieving them back is a bit more complex. ] ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
