8.
How was the Internet Built? <ul><li>In the 60’s and 70’s there were many different networks, protocols and implementations. </li></ul><ul><li>Sharing of information among these dissimilar networks soon became a problem. </li></ul><ul><li>A common protocol needed to be developed. </li></ul>

9.
Historical Maps of ARPANET <ul><li>Paul Baran in the 1960s envisioned a communications network that would survive a major enemy attacked. The sketch shows three different network topologies described in his RAND Memorandum, &quot;On Distributed Communications: 1. Introduction to Distributed Communications Network&quot; (August 1964). The distributed network structured offered the best survivability. </li></ul>

10.
A rough sketch map of the possible topology of ARPANET by Larry Roberts Dr. Lawrence Roberts led the team that designed and developed ARPANET, the world's first major computer packet network. Dr. Roberts, as ARPA's chief scientist, began to architect ARPANET in 1967 influenced by the theoretical packet switching work by Leonard Kleinrock. This research network evolved into the modern Internet.

11.
DARPA <ul><li>The Defense Advanced Research Projects Agency funded the exploration of this common protocol. </li></ul><ul><li>The TCP/IP protocol suite evolved from the ARPANET protocol suite where the fundamental concept of layering was introduced. </li></ul>

12.
Backbone Protocol <ul><li>TCP/IP became the backbone protocol of multivendor networks such as ARPANET, NFSNET and other regional networks. </li></ul>

13.
TCP/IP’s Objective <ul><li>On the battlefield a communications network that sustains damage should be robust enough to automatically recover from any node or phone line failure </li></ul>

14.
A Suite is Born <ul><li>The protocol suite became popular when it was integrated into the University of California at Berkeley’s UNIX operating system. </li></ul>

15.
TCP/IP- Goodbye proprietary networks <ul><li>TCP/IP provides the ability to merge different physical networks using a common suite of functions and interoperability between equipment. </li></ul>

16.
TCP/IP Layer Model <ul><li>When networks first came into being, computer could typically communicate only with computers from the same manufacturer. In the late 1970s, the OSI (Open System Interconnection) model was created by the International Organization for Standardization to break this barrier. The OSI model was meant to help the vendors to create the standard network devices. The OSI model is the Primary architectural model for networks. It describes how data and network information are communicated from application on one computer, through the network media, to an application on another computer. The OSI reference model breaks this approach into Layers. </li></ul><ul><li>TCP/IP Layer Model </li></ul><ul><ul><li>7 layer OSI model </li></ul></ul><ul><ul><li>4 layer DOD model </li></ul></ul><ul><ul><li>Microsoft’s model </li></ul></ul>

17.
TCP/IP - The need for standards <ul><li>Gain an understanding of: </li></ul><ul><ul><li>the OSI and DOD Layer models </li></ul></ul><ul><ul><li>the 802.x standards </li></ul></ul><ul><li>Why standards play such an important role in the growth of the Internet </li></ul>

18.
RFC’s <ul><li>What are they? </li></ul><ul><li>The Requests for Comments (RFC) document series is a set of technical and organizational notes about the Internet (orginally the ARPANET), beginning in 1969. Memos in the RFC series discuss many aspects of computer networking, including protocols, procedures, programs, and concepts, as well as meeting notes, opinions, and sometimes humor </li></ul>

20.
Subject Goals <ul><li>Gain an understanding of how Linux fits into today’s networked world </li></ul><ul><li>Discuss the strengths and weaknesses of Linux </li></ul><ul><li>Learn when a Linux solution is right </li></ul><ul><li>Install and administer the latest in Linux applications for resource sharing </li></ul>

24.
You will learn the differences between: <ul><li>Mac address </li></ul><ul><li>IP address </li></ul><ul><li>Subnet masks </li></ul><ul><li>Private Addresses </li></ul><ul><li>Public Addresses </li></ul><ul><li>Unless you already know the difference in which case you will review it </li></ul>

27.
Configuring TCP/IP Networking <ul><li>Setting the Hostname </li></ul><ul><li>Assigning IP addresses statically </li></ul><ul><li>Automatically receiving an address (DHCP) </li></ul><ul><li>Subnet masks - what are they and what do they do? </li></ul><ul><li>Dividing networks using Subnets </li></ul>

28.
ARP and RARP <ul><li>The address resolution protocol </li></ul><ul><li>How does a machine communicate within the subnet? </li></ul><ul><li>When do we need to route using a Layer 3 Protocol? </li></ul>

29.
DNS <ul><li>Setting up name services (BINDx) </li></ul><ul><li>How does it resolve names to addresses and vice-versa </li></ul><ul><li>You will setup your machine with the name service running </li></ul>

30.
Setting up a DNS Nameserver <ul><li>When you need a nameserver </li></ul><ul><li>Why you may prefer to use your ISP’s DNS </li></ul><ul><li>Configuration files </li></ul><ul><ul><li>/etc/hosts </li></ul></ul><ul><ul><li>/etc/resolv.conf </li></ul></ul>

33.
Bridges, Routers and Switches <ul><li>Which device should be used to address a specific design goal? </li></ul><ul><li>What the differences are with each of these devices? </li></ul><ul><li>Why the layered model approach helps speed up the process required to bring products to market. </li></ul>

34.
Routing and Switching <ul><li>How does it differ? </li></ul><ul><li>What devices do we use to accomplish the task. </li></ul>

36.
Bridging Protocols <ul><li>Operates at Layer 2 of the OSI model </li></ul><ul><li>Smart bridges, allow some form of intelligence at Layer 3 </li></ul><ul><li>Spanning-Tree Protocol is a link management protocol that provides path redundancy while preventing undesirable loops in the network. </li></ul>

37.
Network monitoring and Discovery tools <ul><li>Ethereal - view the packets in real time </li></ul><ul><li>Nmap - port scanner </li></ul><ul><li>Npulse - front end for nmap </li></ul><ul><li>You will install and run these applications on your machines </li></ul>