Network Laboratory Project Proposal

Vision Thing

Our goal is to provide an SOS project that builds on last years Network Lab and will extend into the future. We will produce documentation to support next years iteration of this project, a simulated Wide Area Network, a Local Area Network, and a distributed network software system to be disclosed.

Due to our time limits, we will be doing a focused version of last years project. Our credit dispersal for project time is: Fall 2 credits, Winter 8 credits, Spring 8 credits.  

Assignments include:
1.	Read the first 3 chapters of the Chapters 1-3 of Computer Networks Third Edition - Andrew S. Tanenbaum - Prentice Hall PTR - ISBN 0-13-349945-6  and use the TCP/IP Illustrated Volume 1 - The Protocols - W. Richard Stevens - Addison Wesley 1994 - ISBN 0-201-63346-9 Stevens as a reference. 
2.	Do the Fall and Winter assignments and update them as is necessary to make a more general version. 
3.	Build a testbed flat (everything on the same subnet) network for learning about general TCP/IP networking. 
4.	At the end of winter quarter build a network that makes use of a Virtual Private Network protocol for authentication over the Internet. We already have a potential design that I can describe to you at a later date. This network would enable us to build a distributed network application, most likely an e-commerce system.
5.	Document what we feel is the necessary equipment to teach a small class in network infrastructure along with a detailed inventory of present equipment. Details will include Model, Manufacturer, serial number, resource/configuration settings. Due to the age of the equipment we presently have, there are some partly functional items. These will also be documented as to what exactly is broken.
At present our staffing is 4 people in the project and 2 associates. One associate is most likely going to be part of another project but would like to continue to work with us. The other associate is trying to develop a project for us to implement on top of our network. I hope that this meets with your desires for the project and we would enjoy all feed back. We also have a group mailing list that you may be interested in joining, please ask Erik Ordway for details if interested in joining it.

Proposed Final Projects to do in Spring.
Contained in every project will be the following – update last years documentation, build a network, document equipment, and document the project.
The Beer Run. 

HomeBrew e-commerce site decided on Sean Basham and Steve Paynter representing Home Brew database application. This will be an oracle database with a VPN connection to the warehouse in Kent. Pragmactive will provide a server machine for future collocation. The vendor (warehouse) has his entire inventory in his head. We may need to help the vendor develop an inventory system in parallel to the order entry web system. We'll need secure credit card authentication on the web. This vendor is currently dealing with microbreweries in the area, we will be opening a new market catering to casual users on the Internet. Sponsor is Eric Boyd of Pragmactive Custom Solutions Office (360) 456-4507 (800) 680-2923 Cell (360)239-6704 .

Component breakdown:
•	Write the data access application for database connectivity
•	Build a secure link between the database machine and the database application (running on a separate machine over VPN on TCP/IP).
•	Assist with configuring the database machine to be provided by Pragmactive.
•	Configuration of remote machine (warehouse) and its network connection.

Functional Requirements: Secure network link, application to access the database for the purpose of gathering new orders, ability to print orders, picking slips, and mailing labels.
Non-functional Requirements: must run over whatever hardware/software we have available, must be able to recover from power loss or connectivity outage.
User profiles
Warehouse worker: computer illiterate, very knowledgeable about beer supplies.
Pragmactive database administrator: moderately computer literate, knows next to nothing about beer supplies.
Secured Link How-To

Documentation on using IP-SEC to connect multiple Operating Systems in a secure fashion. Including step by step instructions for each OS connection.

Component breakdown:
•	IP-Sec documentation for each OS
•	Configuration and administration of UNIX and UNIX like machines.
•	Configuration and administration of Windows NT.
•	Document procedures for each secure link.
•	Write test and monitor applications.
Functional Requirements
Non-functional Requirements
User profiles
User A
User B

How to build a network lab.

Complete procedures detailing for an educational facility how to setup up a network laboratory like this one.

Component breakdown:
•	Interactive program flow
•	Graphics
•	Content
•	Document facilities requirements
•	Design a growth plan for five years
•	Document information about OS choices including pros and cons, and informational resources for each.
•	Document possible grant sources.

Functional Requirements
Non-functional Requirements
User profiles
User A
User B

DRAFT DATE: 10/29/99 TO: Torleiv Flatebo Ringer CC: Neal Nelson, Judy Cushing, David Meyers, current NSL members RE: 1999-2000 Networking Systems Laboratory Critical Needs The NSL (Network System Laboratory), a one year project of Student Originated Software (SOS) at Evergreen State College, is a continuation of the network lab previously built and operated by a group of 1998-1999 students utilizing a group contractBelow is a list of equipment we feel is required to produce a successful project. Note: the items on this list would supplement equipment already in the lab inventory. * 1. Three 486 workstations - these will function as firewall/routers on our simulated WAN. 2. Four ISA Ethernet Network Interface Cards - these are for the workstations enumerated above. 3. A PII or K6 workstation to function initially as an NT Backup Domain Controller and later to be a database server. * 4. NT 4.0 server software and 5 client licenses - this will be one of several network operating systems to be used. 5. Oracle Developers software and licenses - this will be our database engine. * 6. Dot matrix printer - customer site emulation and firewall logging. 7. Two - 4+ GB hard drives - these will be installed in the Primary Domain Controller and the database server. 8. $150 per quarter contingency budget for critical failure component replacements - if a hardware component fails during the year, we would like to be able to replace it rapidly. 9. One Internet Domain Name registration - estimated cost $35 for two years - this will give us a viable Internet domain for development of our final product. The domain name can be retained for future iterations of the Network Systems Laboratory. 10. Microsoft BackOffice Developers edition 120 day demo $29.95 * preliminary arrangements have been made to acquire this equipment from Evergreen State College through Torleiv. All documentation on the project is available on the Internet at http://grace.evergreen.edu/sos/project_home.html - click on the Network Group link on the aforementioned page. For questions about our current inventory, please refer to the relevant page on our website.