Download
1 / 17
170 likes | 296 Vues
CSCI 4550/8556 Computer Networks. Comer, Chapter 2: Motivation and Tools. Introduction. Motivation Service Tools for exploration. Historic Motivation. Early computers were expensive. They were very large (compared to today’s machines). They were centralized and not easily moved.
E N D
CSCI 4550/8556Computer Networks Comer, Chapter 2: Motivation and Tools
Introduction • Motivation • Service • Tools for exploration
Historic Motivation • Early computers were expensive. • They were very large (compared to today’s machines). • They were centralized and not easily moved. • Programs took a relatively long time to run. • It was not economically feasible to put computers in a large number of locations
ARPA • The Advanced Research Project Agency initiated a project to connect researchers with the centralized computer systems. • In doing so, they adopted new technologies: • Packet switching • Internetworking • The result was a network that allowed remote access by users to the expensive resources.
Packet Switching • In packet switching, data is transmitted in small, independent pieces. • The source divides outgoing messages into packets. • The destination reassembles the received packets into the original message. • Each packet travels independently from the source to the destination. • Each packet includes enough information for delivery. • The packets may take different paths to the destination. • Each packet can be retransmitted if necessary.
Internetworking • There are many mutually incompatible network technologies in use today. • No one technology is appropriate for every situation. • Internetworking glues together networks of dissimilar technologies with routers. • The result is a virtual network whose details are practically invisible to the individual computers connected to it.
History and Growth • The ARPAnet began in late 1960s (not using TCP/IP). • TCP/IP developed in late 1970s. • ARPAnet switched to TCP/IP in early 1980s. • Start of Internet • Few hundred computers • Few tens of networks
Probing the Internet • Two common tools can be used to examine the Internet: • ping - sends a message that is echoed by a remote computer back to the sending computer • traceroute – attempts to identify and report the path taken by a packet as it travels to a remote computer
Ping • Sends a packet to a remote computer system. • The remote computer replies with an echo packet. • The local computer reports receipt of the echo. • Some systems (e.g. Windows) limit number of packets. • Others (e.g. UNIX) may send until interrupted or until specified number of packets are sent. • Report usually includes indication of how long the round trip required, and if any packets were lost.
Ping – Example 1 apollo> /usr/sbin/ping stanw.unomaha.edu PING stanw.ist.unomaha.edu (137.48.134.226): 56 data bytes 64 bytes from 137.48.134.226: icmp_seq=0 ttl=126 time=2 ms 64 bytes from 137.48.134.226: icmp_seq=1 ttl=126 time=0 ms 64 bytes from 137.48.134.226: icmp_seq=2 ttl=126 time=0 ms 64 bytes from 137.48.134.226: icmp_seq=3 ttl=126 time=0 ms 64 bytes from 137.48.134.226: icmp_seq=4 ttl=126 time=0 ms ----stanw.ist.unomaha.edu PING Statistics---- 5 packets transmitted, 5 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/2 ms apollo>
Ping – Example 2 [stanw@pki0029 stanw]$ ping -c 5 cs002pc.unomaha.edu PING cs002pc.ist.unomaha.edu (137.48.134.214) from 137.48.252.29 : 56(84) bytes of data. 64 bytes from cs002pc.ist.unomaha.edu (137.48.134.214): icmp_seq=0 ttl=248 time=940 usec 64 bytes from cs002pc.ist.unomaha.edu (137.48.134.214): icmp_seq=1 ttl=248 time=6.797 msec 64 bytes from cs002pc.ist.unomaha.edu (137.48.134.214): icmp_seq=2 ttl=248 time=6.393 msec 64 bytes from cs002pc.ist.unomaha.edu (137.48.134.214): icmp_seq=3 ttl=248 time=6.382 msec 64 bytes from cs002pc.ist.unomaha.edu (137.48.134.214): icmp_seq=4 ttl=248 time=6.605 msec --- cs002pc.ist.unomaha.edu ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/mdev = 0.940/5.423/6.797/2.247 ms [stanw@pki0029 stanw]$
Traceroute • Sends a series of packets along a path to the destination. • Each successive packet identifies the next router along the path. • Traceroute uses an expanding ring search. • Each packet is usually sent three times. • The list of packets received is reported at the local computer.
Traceroute – Example 1 [root@cs002pc stanw]# /usr/sbin/traceroute apollo.unomaha.edu traceroute to apollo.unomaha.edu (137.48.1.12), 30 hops max, 38 byte packets 1 137.48.134.253 (137.48.134.253) 1.242 ms 0.883 ms 0.914 ms 2 west-dist-rtr-back (137.48.239.34) 5.903 ms 2.275 ms 1.044 ms 3 apollo (137.48.1.12) 0.840 ms 0.738 ms 0.707 ms [root@cs002pc stanw]#
Traceroute – Example 2 [stanw@pki0029 stanw]$ /usr/sbin/traceroute apollo.unomaha.edu traceroute to apollo.unomaha.edu (137.48.1.12), 30 hops max, 38 byte packets 1 unebpki.uneb.edu (199.240.194.68) 0.506 ms 0.525 ms 0.550 ms 2 199.240.194.254 (199.240.194.254) 2.274 ms 2.270 ms 2.987 ms 3 199.240.198.246 (199.240.198.246) 3.019 ms 2.328 ms 2.685 ms 4 199.240.199.252 (199.240.199.252) 6.158 ms 7.467 ms 5.799 ms 5 uncsn-uno (137.48.200.254) 5.902 ms 7.351 ms 6.091 ms 6 west-dist-rtr-main (137.48.239.2) 7.921 ms 6.867 ms 21.806 ms 7 apollo (137.48.1.12) 6.458 ms 6.129 ms 6.160 ms [stanw@pki0029 stanw]$
Web Access to Tools • Ping and Traceroute are available on the web (provided by Carnegie-Mellon University). • To avoid some security problems, the University of Nebraska networks are configured to disallow ping and traceroute packets from “crossing the border” between the university networks and the rest of the Internet.
