Craig Ringer wrote:
On Thu, 2004-08-19 at 22:48, Rick Reynolds wrote:
I am researching LTSP as part of preparation for a Linux desktop pilot project for one of the directorates here at Census. Currently, all client computers get ip addvlanresses from ISC DHCP 3.0 servers run by an organization other than the susbject directorate. I want to set up all the dhcp functions (PXE, client identification) on the LTSP server so that the LTSP managers can handle it all, but I can't find this described anywhere.
You can make the main DHCP server refuse to hand out leases for select MAC addresses, and set up a secondary one that ONLY hands out leases for those MAC addreses. The secondary server can be configured differently, sent out different parameters, etc. It's quite a bit of admin work to maintain the MAC listings in two places, though.
If you only want to redirect tftp, the next-server directive may be useful.
Alternately, you could always VLAN off your LTSP users and run a separate DHCPd that's private to that VLAN. Of course, for this you'll need switching gear capable of understanding VLANs, plus either VLAN support in Linux or a second NIC in the server that can be on the LTSP VLAN.
I could easily be misunderstanding what you want or just wrong, but hopefully this will point out some possible avenues of investigation.
-- Craig Ringer IT Manager POST Newspapers Western Australia
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _____________________________________________________________________ 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
Craig,
What I want to do is seperate the two functions the way all of the pxe management stuff is removed from the dhcp service in Active Directory and posited in the RIS server. The RIS server must be registered in AD as a dhcp server, but this seems to me to be more of a security thing (binl can't start unless AD thinks it's authorized) than a dhcp thing. Like any rogue dhcp server, RIS still needs to be specified as a relay agent to get outside its local subnet. Records, however, are kept in the directory, including the records of how the RIS server responds. Haven't had to think about this before, but it's possible that the process I'm trying to avoid (mkaing a request to the DHCP manager to update setup parameters like bootfiles and workstation MAC addresses) may actually be in part refereed by the directory. The directory knows who's allowed and who's not and may be making that determination at the bootfile level for dhcp. So maybe the first suggestion is the one to pursue, since it would allow me to run dhcp on the ltsp server and provide only the addresses for the boxes I want there to begin with, and maintain all the other stuff locally at the server. So the only external request left to make would be to exclude the MAC address, and maybe adjust the dhcp ranges used in each server from time to time. They might let me do that. Thanks. Maybe it's been in front of me all along
Don't remember if this kind of thing might work for the guy withn the Win2K dhcp. It might, at that.
Rick Reynolds
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _____________________________________________________________________ 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
