On Tue, May 21, 2002 at 05:05:51AM -0500, Brian Fahrlander wrote: > On Tue, 21 May 2002 10:31:42 +0200, "Hans Ekbrand" <[EMAIL PROTECTED]> wrote: > > > > I don't understand why this would be of benefit; having two seperate lines >might buy some bandwidth, but it must be a real pain in physically wiring the place. >Besides- I would thing the internet traffic (0>1M/sec, typical) would almost be >unnoticed on a 100-base-T network. Am I missing something? > > > > I think you are writing about different things. Richard Camp probably > > refers to a solution where only the server is connected to "the > > internet", while you seem to write about a setup where every terminal > > has two nics, one for internet traffic and one for LTSP. The OP was > > not clear about why he wanted a "gateway", perhaps he didn't know what > > he wanted. And the answers he recieved reflected that ambiguity. > > No, not the terminals- the server. Everyone's been pretty resolute about >putting the dual cards at the server...one to the terminal farm, the other to the >rest of the net. I just don't see why anyone would bother. What's the scoop?
I read your statement about "a real pain physically wiring the place" as to imply two nics on every terminal. And the OP wondered how the workstations would know which nic was for LTSP and which was for internet traffic. The gains of physically separating LTSP and internet traffic of course depend on a number of things: is the network connected with hubs or switches? what is the speed of the local network compared to the internet connection? Are there other machines not part of LTSP connected to the local network, and what load do these machine put on the network? What security risks does it imply to expose the terminals to internet traffic, and the LTSP traffic to the gateway your using fo r internet? I only see one con: if the terminals are dual boot LTSP / MS Windows, terminals booted to MS Windows cannot reach the internet if the LTSP server goes down. (And the need for a switch dedicated to the LTSP part of the LAN). -- Hans Ekbrand
msg05346/pgp00000.pgp
Description: PGP signature
