Networking Lab 7b

Lab Name: Subnetting
Name: Leo Burke
Date: 10-21-07

Objective
In the lab, our assignment was to take the computers create a network by manually subnetting each computer and switch to create a working network. In the process we decided on what network class to use, what default subnet was, as well as the network's topology. During the construction of our network, we had to configure each switch independently with hyper terminal, as well as each router. All of our IP addresses were calculated by hand with the help of a network topology diagram.

Equipment list
4 Lab Computers
2 Routers
2 Cisco Switches
Hyperterminal
Cat 5 Cable of varied length
Network Topology diagram

Notes and observations.
This Lab was very complicated and confusing at times. The hardest was not figuring out what IP addresses to use and how to assign subnets and masks (althought that was one of the difficult portions of the lab). Rather, the difficult part was getting hyperterminal to 'see' the router we had hooked up so we could configure it. After that, the most complicated part of subnetting a network is figuring out the IPs themselves, which was difficult to do until someone in class told me how to properly subnet the network. I also learned a few tips in the lab and what to look for when subnetting a network.

Diagrams Flowcharts and Figures
(Network Diagram)

















(Network Practice Lab worksheet)















References
Lab Handout, Hyperterminal command list, Whiteboard Diagram

Questions
no questions were included in the lab

Conclusions
this lab, while a little more complicated and not as straightforward as others, proved to be full of useful information and practical knowledge. I had set up a network in a previous lab, but I had not done any of the subnetting or mask setup that took place in this lab. I finally learned how subnetting works and how to set up a functional network using subnetting.

Networking Lab 6

Lab Name: Packet Sniffing with Ethereal
Name: Leo Burke
Date: 10-14-07

Objective
Using tools found on the web, we are to find out exactly what happens to packets and information that flows in and out of our computer. We downloaded a "packet sniffer" which records and describes the packets that are being sent and received by our computer, then we were to create situations where certain packets would show up and we would describe them.

Equipment list
Computer lab
Ethereal packet sniffer

Notes and observations
Compared to other labs, this one was very easy and only required us to download one program and run it. The ease of which to record and capture packet transfer data surprised everyone. The sheer amount of packets being sent also caught everyone off guard. Going through and simulating different network traffic types was interesting and easy.

Diagrams Flowcharts and figures.
ethereal in action:















References
Lab Handout

Questions
1. What is the purpose of sequence numbers? To find which order the packets are sent and received
2. What is the purpose of source and destination addresses? Find where packets come from and go to.
3. What is theh purpose of DNS? Turn web addresses into Ip Addresses
4.What is DHCP? Domain Host Configuration protocol, issues ip addresses automatically.
5. What are the implications of having a tool like Eathereal freely available? Anyone can inspect the network traffic.

Conclusions
This was an eye opening lab to the nuts and bolts of packet traffic. When the sheer volume of information that comes in and out of one's computer has an address, source and other information ready to view, then things seem a bit unreal. The ease of which to find tools to mo niter internet traffic is unheard of, and the wealth of information that it can produce is staggering. I now know how to monitor the packets coming in and out of my computer, and what kind of packets are being sent and received when I do various online tasks. Overall, it was a very informative and fun lab.

Networking Lab 5

Lab Name: Setting Up a web server
Date: 9-30-07
Name: Leo Burke


Objectives

In this lab, our objective was to create our own web server using the Apache Client, as well as using other free methods in order to set up a server. We also used a free FTP client to set up a simple FTP server on our server, as well as host a simple website locally.

Equipment List
Computer lab
Apache server client
Internet Explorer
Filezilla FTP client

Notes and Observations
Setting up the Apache server was usually simple, but not after downloading the wrong file package and attempting to figure out why it would not work. Finding the right registries to change in order to change settings was also a difficult trial and error problem. Getting the FTP client up and running, however, was another challenge unto itself. It was a multistep process that required a lot of searching in order to work our way through, but it paid off and we eventually got our little FTP server working

Diagrams, Flowcharts, and Figures
All of our work was done on one computer with no need for visual aids.

References.
lab handout
Apache server help page

Questions.
I regret to admit the handout containing the questions has been misplaced.

Conclusions
This was a lab where we did some very hands on networking. Setting up an FTP server and Apache web server is the nuts and bolts of website administration. The only problems we had with the lab were setting up the FTP server. I assumed that setting up a website would be a difficult but straight through process, I was pleasantly surprised to find it easier than I expected. The one thing I wish I could do over was set up the FTP server, since it took way longer than it should have, and I know I could get it to work the first time, rather than try several times before getting it to work. Overall, it was an interesting lab.