> addresses for ltsp workstations. I'm trying to avoid using the > mac-address for pointing out which workstations are ltsp-terminals. The > network has both the ltsp-workstations and workstations running Windows > and Mac OS. Because of the different options going into the dhcp-reply > depending on the client I'm trying to distinguish between them in the > dhcp-server. It's no problem detecting when Etherboot is requesting but > when the ltsp kernel send its request I don't know how I can detect > this. Is it possible to let dhcp-client in the kernel use a special > user-class option? Any ideas...
I will tell you how I solved a similar problem, but it isn't pretty. I had an over-eager NT server in the same subnet sticking its response to every DHCP. This problem exists even if I use MAC addresses in the Linux DHCP server. I found the "vendor encapsulated options (VCI?)" documentation, but I didn't find anything corresponding for dhclient. Therefore I told the DHCP server to use ports 1001 and 1002. Then for PCMCIA clients it is simply a matter of adding the -p option to the dhclient invocation in the linuxrc (the port numbers are reversed for the client). This much I did and it works. For the non-PCMCIA clients which download the kernel from the LSP server it is a matter of compiling the Etherboot images yourself instead of getting them from the web page. The file to change is etherboot.h. The lines are: #define BOOTP_SERVER 1001 #define BOOTP_CLIENT 1002 Since my non-PCMCIA clients haven't crashed yet, I haven't done this part. -bhaskar ------------------------------------------------------- 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
