toliphant

Just another WordPress.com site

Lab 09

Objectives

The objective of this lab was to understand how to create a simple client/server and how to create an interactive client/server.

Equipment

Computer with python installed

Notes and Oberservations

For this assignment, we had a couple pre coded client server python programs.  After examining the code I understood how they would talk back and forth with one another.  I inserted the IP address of my neighbors computer and he did the same with mine so that we could talk back and forth.  First we start the server program.  You have to talk to the server because that is where the information comes from.  The you start the client program, this program is what talks back and forth. From here, you can type messages back and forth.  This is an example of a simple client/server.

Next, we added a while loop with preset responses to interact with the person who is sending something to our address.  For example, if he were to say “Hi”, it the server would say “Hi” back to him.

The last project that we did was we created a web client.  By using this we were able to see the code for a website and also see the writing it to a file.

Conclusion

 

Advertisements

Lab 08

Objectives:

The objectives of this lab was to configure a Static Route Network, configure a RIP, and troubleshooting a RIP.

Equipment List:

2 Routers
2 Switches
2 Computers
Cat5 cable

Notes and Observations:

For the first project we had to configure a Static Route Network.  First, we got the necessary  supplies and hooked up the computers, the routers, and also the switches.  After we achieved this, got on the computers and started to configure the network.  We configured the interfaces for the e0/0 and s1/0 with IP addresses.  We then configured the computers so that they know how to talk back and forth across the switches and routers.  Next we tried to ping the computers to see if they would talk but at first they would not because in a static route there is no change and we have to show which route the computer will take.  After configuring the route from one network to the other we pinged the computers and were able to talk back and forth.

The second project we configured a routing protocol in our network unlike the first project.  We started out the same way but configured IP addresses to each device but instead of configuring a direct route we creating a routing protocol.

For the third project, we debugged our second project with the routing protocol.

Diagrams, Flowcharts, and Figures:

This is the network that we used.
[pc1] <–> [hub] <–> e0 [router1] f0 <- crossover -> f0 [router2] e0 <–> [hub] <–> [pc2]

Conclusion

After we finished up with this project I was still a little unclear about the static network.  In a way a felt like a knew about it a little but I had a lot of trouble getting it all set up correctly.  Our computers were not talking at first and we followed the instructions the best we could.

Lab 07

Objectives:

The objective of this lab was to create our own network to better understand subnetting.

Equipment List:

Computer
Switches
Routers

Notes and Observations:

We first designed out network up on the whiteboard.  We figured out how many networks we were going to need and then assigned IP addresses.  We had to configure the routers to read from one router to another.  At the very end of the lab, we were able to ping from one side of the network to the other side of the network. going through all the switches and the routers.

Conclusion:

In conclusion, I don’t think I will ever become a professional at networking but I feel that it is useful to know some of this information.

References

References for Alexander Graham Bell and how he was important to networking.

YouTube Videos  – short clips

Public Domain Images

F Potter. “Reluctant genius: Alexander Graham Bell and the passion for invention.”
Choice 1 Aug, 2007: Research Library, ProQuest. Web. 30 Apr. 2012.

Bellis, Mary. “The History of the Telephone – Alexander Graham Bell.” About.com Inventors. About.com.
Web. 30 Apr. 2012. <http://inventors.about.com/od/bstartinventors/a/telephone.htm&gt;.

“Alexander Graham Bell.” 2012. Biography.com 30 Apr 2012, 04:28
<http://biography.com/people/alexander-graham-bell-9205497&gt;.

“A Brief History of Telegrams.” 2012 30 Apr. 2012.
<http://www.retro-gram.com/telegramhistory.html&gt;.

Blog 10

This blog for me will cover the past couple of weeks.  Over the two past weeks we went into discussion about Subnets.  These addresses help to create a network and also how to assign IP addresses and network addresses to everything in the network.  For the lab, we created our own network but hooking up some routers and computers and using subnet masks to create all the networks.  It was really interesting and fun to learn.  I have never really questioned what is a subnet mask and what is it used for.  But to my amazement they play a very important role into setting up your own network and also gave me a better understanding of how IP addresses are assigned.

Binary and Hexidecimal

This week we hit on the idea of binary and hexidecimal.  These machine languages are instructions that make computers work correctly.  Binary consists of 1’s and 0’s.  The arrangement of these makes bits and bytes.  There are 8 bits in 1 byte.  Hexidecimal consistes of a a few more numbers and also includes letters.  0-9, and A-F.  These hexidecimal numbers can be converted into decimal, octal and binary.  MAC addresses are written in hexidecimal and also, computers read colors by hexidecimal.  I have taken Intro to Computer Technology which covered a lot of the information that we covered in class but took it a step further by doing adding and subtracting and also two compliment.  This information we covered was a review but definitely nice to have a refresher of some of the basic ideas of binary and hexidecimal.

Lab 6

Objectives:

The objective of this lab was to understand how information is sent by packet sniffing.

Equipment List:

Computer connected to a network
Wireshark
Pencil and paper

Notes and Observations:

To me this projects was like sending out a letter and seeing where all it went then waiting for the replay back from the recipient when they received it.  It was interesting to see how the internet is all linked together and how it asks for IP addresses and MAC addresses to get where it needs to go.  But when looking around on the internet, the tool used to get this information can be used in a wrong way such as getting passwords and other information that is sent across the internet.

Diagrams, Flowcharts, and Figures:

References:

http://www.wireshark.org

Questions:

Conclusion:

In conclusion, information from point a to point b moves ridiculously fast and to see all the places it goes before it gets to the end is mind boggling.

Blog 7

This week was part a continuation of last week but we also juggled a little bit with WireShark.  Again, we set up a class network giving each person a part of a network.  We then passed pieces of data back and forth using the layers that we were in.  Certain layers can only read certain pieces of data to pass it from one network node to another.

WireShark is a pretty cool program when used correctly.  Reading on the internet, people can get into a lot of trouble when using this program in the wrong way.  It was very interesting to see what all happens when sending a request for a webpage and then receiving the request back from the destination.  You can see the MAC addresses and also the IP addresses that it has to go through to get from point A to point B.

I posted a link about the possible future of the internet, a shared web.

Blog 6: Contributions

As described in the previous blog title, Blog 6: Summary, I explained the class experiment to show how networks worked, sending information and how the data is handed from one layer to the next.  I played the part of the switch.  My job was to take the incoming data and get it sent out to try to find the address of the receiving network device.

Blog 6: Summary

Over the past week, we covered encapsulating the data.  Encapsulation is the idea of breaking down one data type into a lower layer data type so that it can be shared over networks.  To better understand this concept, we separated the class into two “networks”.  Each network had a switch, router, and server.  To complete the network, the other students played the parts of printers, cell phones, computers, and game consoles.  Each part of the “network” had MAC addresses and also IP addresses which allow us to talk to one another in the second and third layers of the OSI Model. Our overall goal was to send information from one network to another by passing packets and datagrams and frames from one person to the other until it got to the destination.  As more information is passed on, a table is formed which stores all of the MAC addresses of the original senders of the information.

 

Post Navigation