>> option option-128 e4:45:74:68:00:00; >> option option-129 "NIC=ne IO=0x300"; > >Ken, if you are reading - How does this work again? I tried to explain >it to some one the other day but became confused. I believe that option >128 is a Hex representation that Etherboot understands to mean that >there are some options that it should pass to the kernel. Option 129 >are those options.
That's exactly it. This is already explained in the LTSP docs. option-128 is not a MAC address, it only looks like one. It's a constant signature that tells Etherboot that option-129 is not an accident but holds user specified options. The colon syntax is how arbitrary binary data is specified to ISC DHCPD. >> option-129 looks like it would be something like "NIC=tlan ..." >> What words are reserved for setting the duplex ... DUPLEX=full? >> Can I set duplex from within the dhcpd.conf file? > >Yes, NIC=tlan ... should work. ;-) I have no idea what should come >after it though. NIC= is interpreted by LTSP. It's only needed if the autodetect of LTSP fails. The other options may be interpreted by the kernel and modules. Unknown options will be unclaimed and do nothing. BTW, IO= is not needed for PCI NICs in general. The IO will be assigned by the BIOS and may differ from machine to machine, so you don't want to hardwire it. Fortunately most PCI NIC drivers ignore the address anyway. But back to your question, I doubt if duplex is your problem, unless your switch is incapable of correct autonegotiation. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _____________________________________________________________________ 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.freenode.net
