Cohousing-L Mailing List: Re: Shared Internet Access

[Fred H Olson (fholson]

Signe e <ishtar_767 [at] yahoo.com>
is the author of the message below.
It was posted by Fred the Cohousing-L list manager <fholson [at] cohousing.org>
because the message included HTML ;      PLEASE do not post HTML, see
   http://csf.colorado.edu/cohousing/2001/msg01672.html
   http://www.harley.com/turn-off-html/
--------------------  FORWARDED MESSAGE FOLLOWS --------------------

Our cohousing group "Trillium Hollow" is wired for CAT 5 and we use a
Linux (Redhat 9) server for DHCP, Web hosting, and Email using a DSL
connection 640K down/256K up ( I may have these numbers backwards).  In
the past each of us paid $10 for a connection.

Since taking over the network, I've discovered if Email goes down, folks
become edgy, especially those relying on the server for business.  It is
my recommendation, if a member is relying on your server for business (ie
email), have them purchase their own Internet connection.  Typically the
person administering the server is a volunteer with limited time and is
not on call 24/7.

Second, are you going to host virtual domains on your server?  I've
decided to direct those requests to a professional organization.

Third, how many services can a single server accommodate without network
slow downs? Typically you would not want your web services and mail on the
same machine.

Fourth, what level of service will you provide the residents?  I've learn
to direct residents with computer problems to a professional.  I'm only
responsible for getting their machines on the network.

Fifth, how about security? Firewalls?  Believe me, folks will scan your
ports, I've seen the deny messages in our logs.  Our site has been hacked
in twice and I have since rebuilt the server with a stringent firewall.
Which ports will you allow open?  Will you allow someone to create a VPN
connection to their employer?

Next is the issue of backups.  Our site is only going to backup
configuration files and web code via a CD burn.  It is recommended to make
this clear to residents in the event a server crashes and they want their
email.

In terms of budget, you probably would want to charge enough per
connection to allow for a reserve amount for equipment (e.g. switches, PC
parts) failure or paying a consultant (~$125.00/hr) to troubleshoot
configuration issues.

To ensure a seamless operation, I would link your DSL connection to your
Cohousing business number.  One of our residents moved along with our DSL
connection.  We have since tied our DSL connection with Trillium Hollow
business line.

In my humble opinion, these suggestions will decrease significant
frustration and burnout for both the residents and the lonely volunteer
system administrator.

Just my .02 cents,
Signe



_______________________________________________
Cohousing-L mailing list
Cohousing-L [at] cohousing.org  Unsubscribe  and other info:
http://www.cohousing.org/cohousing-L