lab 3

repost of lab 3

lab 2

repost

Lab 9

test

Industry Panel Lab

It was very interesting listening to how much communication skills matter in a tech related profession. Its not all about what you can do in front of a computer screen but also what you can do face to face. The panel also eased my thoughts about what to major in. I have realized just because you have a certain major, it doesn't plug u in to one profession. It gives you options.

Lab 8

test post

Make up Lab

Objective: use wireshark and other web programs to capture and reveal packets of information from various websites and sources.

In the make up lab we used various tools such as wireshark and superscan to observe what was contained within packets sent to use via youtube. We learned about how these packets connected with the various layers of networking.

http://en.wikipedia.org/wiki/Transport_Layer_Security

Before this lab I was unaware of what TLS meant as far as a type of packet and it looks to encrypt information to add security to the 4th layer of the network. We also used whois.net to look at who actually owns certain domains and it also gave us statistics on when the domain was registered.

We also looked into T1 lines via t1shopper.com and it was interesting to see how much T1 costs and what advantages it offers over a traditional DSL connection.

Lab 7 Subnetting

Objective: Create a network with proper subnetting

The network was physically built fairly easily but configuring it took about an hour. We kept running into issues configuring out IP and router incorrectly. I feel like I have a new understanding of the process needed to be done to subnet a network properly.

Lab 6 Packet Sniffing with Ethereal

Objective: lab 6 was all about using software called Ethereal to view packets that were being transmitted during various network activities.

A sample packet

Type: DNS
Length: 60
Source IP: 10.10.2.204
Destination IP: 129.130.176.1

During the lab I discovered the lack of security when talking about file transfer protocol servers. It is very easy using a free program on the internet to see the FTP password. This just reinforces the idea that one should only use FTP when transmitting files they wouldn't mind anyone seeing. It is too easy to hop on and view anything on an FTP without permission.

The lab also involved ICMP, or Internet Control Message Protocol. It is typically not used to send and receive data between end systems, but rather to send error messages. Within approximately 100 frames you could see 5 different protocols working together; DNS, TCP, NBNS, ARP, and HTTP.

ARP is used to acquire a MAC address from an IP address

Networking 1 Lab 5

Lab 5 involved downloading and using a free ftp web server known as Apache. Our testing home page had the text 'It works!' on it.

httpd.conf was the main configuration file for the Apache server. There were other configuration files as well used for different languages, manuals, and user directories. Apache supports 27 different languages.

The path to our document root directory was C:/Program Files/Apache/Apache2.2/

We changed our browser to Portuguese [pt]

Apache also works on Unix systems. I wouldn't recommend Apache for commercial applications because you could get more security and features from a non-freeware web server.

127.0.0.1 is the default address because it is the home address. An external connection can be made by using the IP of 10.10.2.2

IP address ports identify the service provided. For example port 80 identifies a web server where 14147 would identify a FTP server.

http://10.10.2.2/aboutme.html
This link would take you to the about me page on our web server.




Ethan Weis
Networking 1
Lab 5 FTP Server