[K12OSN] LTSP server with 3 NICs?
"Terrell Prudé Jr."
microman at cmosnetworks.com
Fri Dec 19 18:45:57 UTC 2008
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).
Do you GNU <http://www.gnu.org>?
Microsoft Free since 2003 <http://www.cmosnetworks.com>--the ultimate
R. Scott Belford wrote:
> 2008/12/19 "Terrell Prudé Jr." <microman at cmosnetworks.com>:
>> 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.
> 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.
>> 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.
> 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.
> K12OSN mailing list
> K12OSN at redhat.com
> For more info see <http://www.k12os.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the K12OSN