LinuxSA Mailing list archives
Index:
[thread]
[date]
[subject]
[author]
From: Glen Turner <glen.turner@adelaide.edu.au>
To : linuxsa@linuxsa.org.au
Date: Fri, 25 Jun 1999 05:14:22 +0000
Re: Linux server in a small business LAN (was: Request for ...)
John wrote:
> (Also, it doesn't really matter whether you crash the
> remote machine or not: if the link IS saturated (by pinging
> a multicast network, for example), then it doesn't
> matter whether the machine dies or not. People can't get
> _their_ traffic through to your machine, so the end result is
> the same: Denial of a server's Service.)
Normally I would agree. In this case, the network configuration
I was suggesting looks like this:
+-----------+
ISDN | | ethernet --PC
Internet ---------------| Server |-------------SWITCH--PC
| | --PC
+-----------+
So the ISDN link flooding deosn't matter to people working from
their PC using Word, etc. But killing the server from the
Internet does matter.
I am more than aware that more secure configurations than the
above one exist. But my contention was that the above is
adequate for a small business with limited means. Probably
the largest improvement to security would be to have two servers,
one for file/print for internal users and one dealing with Internet
access and service issues.
I don't think you've said anything I'd disagree with in other
problem domains (such as in a larger company using Win NT servers).
Regards,
glen
--
Glen Turner Network Specialist
Tel: (08) 8303 3936 Information Technology Services
Fax: (08) 8303 4400 The University of Adelaide 5005
Email: glen.turner@adelaide.edu.au South Australia
--
Check out the LinuxSA web pages at http://www.linuxsa.org.au/
To unsubscribe from the LinuxSA list:
mail linuxsa-request@linuxsa.org.au with "unsubscribe" as the subject
Index:
[thread]
[date]
[subject]
[author]
Return to the LinuxSA Mailing List Information Page