Dear All: Interesting discussion! Thanks for the food for thought. My $0.02 worth is inserted below...
Yours Truly! Krishna On Thu, 7 Sep 2006, Cristi Mitrana wrote: > On 9/7/06, Fred Clewis <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi, I'm a LTSP and DHCP noob, and need to understand how I should work with >> a LTSP DHCP server in a large company with it's own DHCP servers. >> >> So when the LTSP workstation starts, it broadcasts for a DHCP server to >> meet it's needs. My questions below: >> >> 1. If I am in a large company intranet network situation and introduce an >> LTSP server into that network, how will my LTSP workstations (which may be >> in other parts of the country) find my LTSP DHCP server? > > They won't, because LTSP will not work over WAN. Actually, I think it can be made to work if you're truly committed. It is not likely to be worth the trouble, though - especially since there are so many other alternatives available. > >> 2. What is to keep other DHCP computers in the company not wanting to use >> LTSP from accidentally finding my LTSP DHCP server? I recommend having only one DHCP server active on the ONE subnet where you'll have true LTSP clients. Despite the fact that other setups can be made to work, it's just asking for trouble to have more than one going. What you need for running over subnet boundaries is something more like Thinstation - see http://www.thinstation.org/ for more (don't worry about their hardware being required - it's not.) > > Configure your dhcp LTSP server to not give out leases to unknown > clients and only add known LTSP clients to the DHCP server > configuration. This is a ISC Dhcpd issue and not really pertaining > LTSP. This won't be an issue at all if you run only one DHCP server per subnet. You'll still want to recognize individual MAC addresses and hand out a fixed IP address for that station in the majority of cases, with a config that matches the hardware at that station. > >> 3. How can you even experiment with LTSP without causing DHCP havoc and >> irritating your companies intranet police? Are you all on disconnected >> networks? Not disconnected! Truly connected, probably at high speed, too. It's just a matter of where you get the lease, etc.; it should be "local". > > Configure the LTSP dhcp server to listen to a different port and use > Etherboot images (floppy or cdrom) to boot your ltsp clients. The > Etherboot boot images can use a different bootp port number and will > only query your dhcp server. See www.rom-o-matic.net for information > on how to obtain such images. You can also have the "remote clients" use an image from a floppy or cdrom and skip DHCP altogether. Or simply do an X login over the Internet. One way I had success with was to use the options in a SUSE 10 (installed linux) login screen to connect to the LTSP server itself; the only flaw was in the case of an application that required a specific screen font that wasn't there (when there's a difference between the X fonts available - and expected - in the LTSP tree and what's on the machine that is logging in.) > > You can get away without a special dhcp server, you just need to hand > over to you LTSP booting clients the boot loader (pxelinux if using > pxe or the path to the tftp server if using Etherboot). You just need > to understand the basics of booting a LTSP client first. > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _____________________________________________________________________ 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
