<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> 50 each...you *could* do individual DHCP reservations for, say, 50 of the clients pointing to one LTSP server, and then have everyone else point to the other LTSP server. A little high-maintenance, but it certainly does work. Say your first LTSP server is 10.0.4.254 and your second one is 10.0.5.254. You want to direct a specific client (MAC address 11-22-33-44-55-66) to 10.0.5.254. host ws001 { hardware ethernet 11:22:33:44:55:66: option root-path "10.0.5.254:/opt/ltsp/i386"; next-server "10.0.5.254"; filename "/lts/boot/pxe/pxelinux.0"; Here's another option, the one I'd be looking at over the long haul. If your router and your switches all support 802.1Q VLAN trunking, then I'd pop each LTSP server in its own fully-routed IP subnet. For example, using Cisco gear, something like this: ------------------------------------------------------ interface FastEthernet0/1.101 description LTSP Server #1's subnet encapsulation dot1q 101 ip address 10.0.8.1 255.255.255.0 interface FastEthernet0/1.102 description LTSP Server #2's subnet encapsulation dot1q 102 ip address 10.0.9.1 255.255.255.0 ! This assumes that you propagate your routing table info via OSPF, like we do in my district router ospf 100 network 10.0.8.1 0.0.0.0 area 0 network 10.0.9.1 0.0.0.0 area 0 ------------------------------------------------------ Then, make VLAN's 101 and 102 in your switch, turn on your trunking, and pop whatever client ports you want for LTSP server #1 into VLAN 101, and the client ports for LTSP server #2 into VLAN 102. Your LTSP servers will, of course, need to be put into the new subnets and VLAN's as well. Note that everything's still fully routable internally throughout the school; you're not doing any NAT'ing here. --TP <div class="moz-signature">_______________________________ Do you GNU!? <a href="http://www.gnu.org/">Microsoft Free since 2003</a>--the ultimate antivirus protection! </div> Mel Wade wrote: <blockquote cite="mid43080f460709062238k55c286b5nbfadb1303fa56063@mail.gmail.com" type="cite"> <pre wrap="">1. About 50 each. 2. 10.0.4.0/22 - all clients 3. one-NIC setup On 9/6/07, "Terrell Prudé Jr." <a class="moz-txt-link-rfc2396E" href="mailto:microman@cmosnetworks.com"><microman@cmosnetworks.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> There are a couple of ways I can think of to do this: do it by subnet, or do it by individual DHCP reservation. The first method scales for many clients, but your network infrastructure really should support VLAN's. The second method is very specific, but I find maintenance to be a pain if you have to swap NIC's. A few more pieces of info would help: 1.) How many clients are we talking about directing to each LTSP server? 2.) What are the IP subnets being used on the LTSP client segment(s) of each LTSP server? 3.) Are you using a two-NIC (classical) or one-NIC LTSP setup? --TP Mel Wade wrote: I'm trying to use a third server as DHCP to direct specific clients to one of two other LTSP servers. On 9/6/07, "Terrell Prudé Jr." <a class="moz-txt-link-rfc2396E" href="mailto:microman@cmosnetworks.com"><microman@cmosnetworks.com></a> wrote: Remember that K12LTSP actually does use LTSP, and furthermore, Eric makes *minimal* changes...and I mean *minimal*. Really--it's nearly bone-stock from upstream LTSP. The file locations are, with the exception of /etc/dhcpd.conf, identical (IIRC, he renames it something like /etc/dhcpd-k12ltsp.conf or something like that). By contrast, Edubuntu tends to move the LTSP files into quite different locations (under /usr and such) than upstream LTSP uses. Drives me nuts whenever I want to run ltspadmin. Any time I use K12LTSP, I just use the LTSP docs, and I have yet to go wrong. Anything in particular you're looking to figure out? --TP _______________________________ Do you GNU!? Microsoft Free since 2003--the ultimate antivirus protection! Mel Wade wrote: Anyone know where I can find DHCP documentation specific to K12LSTP client booting? _______________________________________________ K12OSN mailing list <a class="moz-txt-link-abbreviated" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <a class="moz-txt-link-rfc2396E" href="http://www.k12os.org"><http://www.k12os.org></a> _______________________________________________ K12OSN mailing list <a class="moz-txt-link-abbreviated" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <a class="moz-txt-link-rfc2396E" href="http://www.k12os.org"><http://www.k12os.org></a> </pre> </blockquote> <pre wrap=""> </pre> </blockquote> </body> </html>