<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> I actually didn't have to touch /etc/hosts.allow, just /etc/hosts. Reason is that there aren't any network services (e. g. SSH, httpd) to which the clients connect. They're thin clients. That might be different with LTSP 5, though, since it encrypts everything in SSH tunnels. I just haven't tried it yet (no time). --TP <div class="moz-signature">_______________________________ Do you <a href="http://www.gnu.org">GNU</a>? <a href="http://www.cmosnetworks.com">Microsoft Free since 2003</a>--the ultimate antivirus protection! </div> R. Scott Belford wrote: <blockquote cite="mid:cf32ed920812191039v3a492dan7f57db735c75cd42@mail.gmail.com" type="cite"> <pre wrap="">2008/12/19 "Terrell Prudé Jr." <a class="moz-txt-link-rfc2396E" href="mailto:microman@cmosnetworks.com"><microman@cmosnetworks.com></a>: </pre> <blockquote type="cite"> <pre wrap="">This is exactly how I did the PPC/x86/SPARC K12LTSP server a while back, and yes, it would work wonderfully for your situation. Basically, you'd need to do this: 1.) Set up your third NIC for another client subnet (e. g. 192.168.4.0/24), and hook 'er up to that switch. 2.) Modify /etc/hosts to include host entries for the 192.168.4.0 range, just like the ones for 192.168.0.0 are today. </pre> </blockquote> <pre wrap=""> Right on, Terrell. This is how I have done it for labs and for the PTC email garden. I am thinking that /etc/hosts.allow needs to be modified, and I think I had to assign somewhat different hostnames for the 192.168.4.0 range in /etc/hosts. </pre> <blockquote type="cite"> <pre wrap="">Note that this is not channel-bonding. This is just good ol' fashioned separate interfaces on separate broadcast domains. There doesn't seem to be any need to channel-bond here. </pre> </blockquote> <pre wrap=""> This is a key point for many. Often times the congestion on your server is not at your dual or core or octa CPU or in your RAM or in your disk I/O. It is at your single NIC, even if it's a giganic, trying to serve all that data. I rarely do an install with only one NIC for the LAN. </pre> <blockquote type="cite"> <pre wrap="">--TP </pre> </blockquote> <pre wrap=""> --scott _______________________________________________ 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> </body> </html>