1. Introduction & Lab I Lab Equipment & Organization Shlomo Hershkop Columbia University Fall 2006

2. Announcements  Introducing the TA Archana Rao maybe one more (depending on enrollment numbers)  Lab Setup  Online Poll please take the office hours poll so we can accommodate everyone’s preferences  Lab times we need to confirm all lab groups (3/4 members) might switch around some people for spreading out experience need to confirm specific lab times

3. Internet Lab Equipment  4 Cisco 2600 Routers  4 Linux PCs (Intel Celeron 400MHz, 256MB Ram, 40GB disk, cdrom, floppy)  4 Ethernet hubs 2x 5-port Hub 3Com OfficeConnect Dual Speed (10/100) 2x 8-port Hub NETGEAR DS108  Dual monitor, keyboard, mouse  1 KVM switch can accommodate two users at once  Cables pretty colors

4. Internet Lab Equipment

5. Linux PCs  PCs are labeled as: RackPC1, RackPC2, etc.  PCs run Linux (Redhat)  Each PC has: a floppy drive, a cdrom drive, 2 usb ports a serial port, 5x 10/100 Mbps Ethernet interface cards (NICs) named eth0 – eth4.

6. Linux PC

7. Cisco Routers  Routers are labeled: Router1, Router2, Router3, Router4.  Routers run Cisco IOS 12.0 or a later version  Each router has: a console port an auxiliary port two 10/100 Mbps Fast Ethernet interfaces

8. Ethernet Hubs  Each hub has 4 or more RJ-45 ports  Ports can operate at 10 Mbps or 100 Mbps

9. Lab Sequence

10. Core Labs  Lab 1 – Introduction to the Internet Lab Overview of the Internet Lab equipment; introduction to ethereal and tcpdump.  Lab 2 – Single Segment IP Networks Configuring a network interface for IP networking; address resolution with ARP; security problems of common Internet applications.

11. Core Labs (cont.)  Lab 3 – Static routing IP forwarding and routing between IP networks; setup a Linux PC and a Cisco router as an IP router; manual configuration of routing tables.  Lab 4 – Dynamic Routing Protocols Routing protocols RIP, OSPF and BGP.  Lab 5 – Transport Protocols: UDP and TCP Data transmissions with TCP and UDP; TCP connection management; TCP flow control; retransmissions in TCP; TCP congestion control.

12. Advanced Labs  Lab 6 - LAN switching LAN switching in Ethernet networks; forwarding of Ethernet frames between LAN switches/bridges; spanning tree protocol for loop free routing between interconnected LANs.  Lab 7 - NAT and DHCP Setup of a private network; dynamic assignment of IP addresses with DHCP.  Lab 8 – Domain Name System Domain name resolution with DNS; name server hierarchy; setup of a DNS root server.  Lab Extra Credit Maybe something to do with wireless

13. Structure of the Labs  Each lab has three phases: Pre-laboratory Assignment (Prelab) Lab Session Lab Reports

14. Structure of the Labs (cont.)  Pre-laboratory Assignment (Pre-lab) Exercises to be completed in advance of the associated lab session. The pre-labs ask you to acquire background knowledge that is needed during the lab exercises. Each pre-lab has a question sheet that must be completed before the corresponding lab session. The answers to the prelab questions are graded.

15. Structure of the Labs (cont.)  Lab Session. Lab exercises that are performed on the equipment of the Internet lab. All lab exercises can be completed without supervision. The time to complete a lab session should be three hours on the average, but may vary. Complete the laboratory activities to the extent that you can. The activities during the lab session are not graded, however, data collected during the lab session are needed to complete a lab report.  Floppy disk symbol in the lab manual indicates when you have to collect data. Floppy disk symbol

16. Structure of the Labs (cont.)  Lab Reports. After each lab session, you prepare a lab report that summarizes and analyzes the findings from the lab session. A notepad symbol indicates an assignment for the lab report. The lab reports should be submitted as a typewritten document.  The lab report is generally due 1 week after the lab session. The lab report is graded.  Note: Lab reports should not include irrelevant data Notepad symbol

17. In the Lab: 1. I am trying to get USB keys, in the meantime, either have one of the group members dig one up (no questions asked, or use provided floppies (please don’t offload them on ebay) 2. Reboot Linux PCs 3. Complete exercises as described in the lab manual 4. Take measurements as instructed 5. Save data to floppy disk

18. Additional notes  The equipment of the Internet Lab is not connected to the Internet. you can bring in a laptop (best) and connect wired or wirelessly  Each lab has an anonymous feedback sheet. The feedback is used to improve the setup and organization of the labs.  Since you have administrative (root) privileges on the Internet Lab equipment, exercise caution when modifying the configuration of the Internet Lab equipment.

19. Introductory material. This module illustrates the interactions of the protocols of the TCP/IP protocol suite with the help of an example. The example intents to motivate the study of the TCP/IP protocols. TCP/IP Networking An Example

20.  A user on host argon.netlab.edu (“Argon”) makes web access to URL http://neon.netlab.edu/index.html.  What actually happens in the network? A simple TCP/IP Example

21. HTTP Request and HTTP response  Web server runs an HTTP server program  HTTP client Web browser runs an HTTP client program  sends an HTTP request to HTTP server  HTTP server responds with HTTP response

22. HTTP Request GET /example.html HTTP/1.1 Accept: image/gif, */* Accept-Language: en-us Accept-Encoding: gzip, deflate User-Agent: Mozilla/4.0 Host: 192.168.123.144 Connection: Keep-Alive

23. HTTP Response HTTP/1.1 200 OK Date: Sat, 25 May 2002 21:10:32 GMT Server: Apache/1.3.19 (Unix) Last-Modified: Sat, 25 May 2002 20:51:33 GMT ETag: "56497-51-3ceff955" Accept-Ranges: bytes Content-Length: 81 Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Content-Type: text/html Internet Lab Click here for the Internet Lab webpage. How does the HTTP request get from Argon to Neon ?

24. From HTTP to TCP  To send request, HTTP client program establishes an TCP connection to the HTTP server Neon.  The HTTP server at Neon has a TCP server running

25. Resolving hostnames and port numbers  Since TCP does not work with hostnames and also would not know how to find the HTTP server program at Neon, two things must happen: 1. The name “neon.netlab.edu” must be translated into a 32-bit IP address. 2. The HTTP server at Neon must be identified by a 16-bit port number.

26. Translating a hostname into an IP address  The translation of the hostname neon.netlab.edu into an IP address is done via a database lookup  The distributed database used is called the Domain Name System (DNS)  All machines on the Internet have an IP address: argon.netlab.edu 128.143.137.144 neon.netlab.edu 128.143.71.21

27. Finding the port number  Note: Most services on the Internet are reachable via well-known ports. E.g. HTTP servers on the Internet can be reached at port number “80”.  So: Argon simply knows the port number of the HTTP server at a remote machine.  On most Unix systems, the well-known ports are listed in a file with name /etc/services. The well-known port numbers of some of the most popular services are: ftp21finger79 telnet23http80 smtp 25nntp 119

28. Requesting a TCP Connection  The HTTP client at argon.netlab.edu requests the TCP client to establish a connection to port 80 of the machine with address 128.141.71.21

29. Invoking the IP Protocol  The TCP client at Argon sends a request to establish a connection to port 80 at Neon  This is done by asking its local IP module to send an IP datagram to 128.143.71.21  (The data portion of the IP datagram contains the request to open a connection)

30. Sending the IP datagram to an IP router  Argon (128.143.137.144) can deliver the IP datagram directly to Neon (128.143.71.21), only if it is on the same local network (“subnet”)  But Argon and Neon are not on the same local network (Q: How does Argon know this?)  So, Argon sends the IP datagram to its default gateway  The default gateway is an IP router  The default gateway for Argon is Router137.netlab.edu (128.143.137.1).

31. The route from Argon to Neon  Note that the gateway has a different name for each of its interfaces.

32. Finding the MAC address of the gateway  To send an IP datagram to Router137, Argon puts the IP datagram in an Ethernet frame, and transmits the frame.  However, Ethernet uses different addresses, so-called Media Access Control (MAC) addresses (also called: physical address, hardware address).  Therefore, Argon must first translate the IP address 128.143.137.1 into a MAC address.  The translation of addressed is performed via the Address Resolution Protocol (ARP)

33. Address resolution with ARP

34. Invoking the device driver  The IP module at Argon, tells its Ethernet device driver to send an Ethernet frame to address 00:e0:f9:23:a8:20

35. Sending an Ethernet frame  The Ethernet device driver of Argon sends the Ethernet frame to the Ethernet network interface card (NIC)  The NIC sends the frame onto the wire

36. Forwarding the IP datagram  The IP router receives the Ethernet frame at interface 128.143.137.1, recovers the IP datagram and determines that the IP datagram should be forwarded to the interface with name 128.143.71.1  The IP router determines that it can deliver the IP datagram directly

37. Another lookup of a MAC address  The router needs to find the MAC address of Neon.  Again, ARP is invoked, to translate the IP address of Neon ( 128.143.71.21) into the MAC address of neon (00:20:af:03:98:28).

38.  The IP protocol at Router71, tells its Ethernet device driver to send an Ethernet frame to address 00:20:af:03:98:28 Invoking the Device Driver at the Router

39. Sending another Ethernet frame  The Ethernet device driver of Router71 sends the Ethernet frame to the Ethernet NIC, which transmits the frame onto the wire.

40. Data has arrived at Neon  Neon receives the Ethernet frame  The payload of the Ethernet frame is an IP datagram which is passed to the IP protocol.  The payload of the IP datagram is a TCP segment, which is passed to the TCP server

41. Wrapping up the example  Data traverses a sequence of layers  Each layer has protocols to handle the packets  Next Lecture (Lab 2) Layered architecture of the Internet Protocols at each layer

42. Review of Important Networking Concepts Introductory material using Prof. Liebeherr on-line notes Review of important networking concepts: protocol architecture, protocol layers, encapsulation, demultiplexing, network abstractions.

43. Networking Concepts  Layered Architecture to reduce complexity Encapsulation Abstractions

44. Sending a packet from Argon to Neon

45. DNS: The IP address of “neon.netlab.edu ” is 128.143.71.21 ARP: What is the MAC address of 128.143.137.1? Sending a packet from Argon to Neon DNS: What is the IP address of “neon.netlab.edu ” ? ARP: The MAC address of 128.143.137.1 is 00:e0:f9:23:a8:20 128.143.71.21 is not on my local network. Therefore, I need to send the packet to my default gateway with address 128.143.137.1 frame 128.143.71.21 is on my local network. Therefore, I can send the packet directly. ARP: The MAC address of 128.143.137.1 is 00:20:af:03:98:28 ARP: What is the MAC address of 128.143.71.21? frame

46. What’s a protocol? human protocols:  “what’s the time?”  “I have a question”  introductions … specific msgs sent … specific actions taken when msgs received, or other events network protocols:  machines rather than humans  all communication activity in Internet governed by protocols protocols define format, order of msgs sent and received among network entities, and actions taken on msg transmission, receipt

47. What’s a protocol? a human protocol and a computer network protocol: Q: Other human protocols? Hi Got the time? 2:00 TCP connection req TCP connection response Get http://www.awl.com/kurose-ross time

48. Communications Architecture  The complexity of the communication task is reduced by using multiple protocol layers:  Each protocol is implemented independently  Each protocol is responsible for a specific subtask  Protocols are grouped in a hierarchy  A structured set of protocols is called a communications architecture or protocol suite

49. TCP/IP Protocol Suite  The TCP/IP protocol suite is the protocol architecture of the Internet  The TCP/IP suite has four layers: Application, Transport, Network, and Data Link Layer  End systems (hosts) implement all four layers. Gateways (Routers) only have the bottom two layers.

50. Functions of the Layers  Data Link Layer: Service: Reliable transfer of frames over a link Media Access Control on a LAN Functions: Framing, media access control, error checking  Network Layer: Service: Move packets from source host to destination host Functions: Routing, addressing  Transport Layer: Service: Delivery of data between hosts Functions: Connection establishment/termination, error control, flow control  Application Layer: Service: Application specific (delivery of email, retrieval of HTML documents, reliable transfer of file) Functions: Application specific

51. TCP/IP Suite and OSI Reference Model The TCP/IP protocol stack does not define the lower layers of a complete protocol stack

52. Assignment of Protocols to Layers

53. Layered Communications  An entity of a particular layer can only communicate with: 1. a peer layer entity using a common protocol (Peer Protocol) 2. adjacent layers to provide services and to receive services

54. Service Primitives N+1 Layer Entity N Layer Entity N+1 Layer Peer Protocol Request Delivery Indicate Delivery Communication services are invoked via function calls. The functions are called service primitives

55. Service Primitives Recall: A layer N+1 entity sees the lower layers only as a service provider Service Provider N+1 Layer Entity N+1 Layer Peer Protocol Request Delivery Indicate Delivery

56. Layers in the Example

57. Send HTTP Request to neon Establish a connection to 128.143.71.21 at port 80 Open TCP connection to 128.143.71.21 port 80 Send a datagram (which contains a connection request) to 128.143.71.21 Send IP datagram to 128.143.71.21 Send the datagram to 128.143.137.1 Send Ethernet frame to 00:e0:f9:23:a8:20 Send Ethernet frame to 00:20:af:03:98:28 Send IP data-gram to 128.143.71.21 Send the datagram to 128.143.7.21 Frame is an IP datagram IP datagram is a TCP segment for port 80

58. Layers and Services  Service provided by TCP to HTTP: reliable transmission of byte streams over a logical connection  Service provided by IP to TCP: unreliable transmission of IP datagrams across an IP network  Service provided by Ethernet to IP: transmission of a frame across an Ethernet segment  Other services: DNS: translation between domain names and IP addresses ARP: Translation between IP addresses and MAC addresses

59. Encapsulation & Demultiplexing  As data is moving down the protocol stack, each protocol is adding layer-specific control information

60. Encapsulation & Demultiplexing in our Example  Let us look in detail at the Ethernet frame between Argon and the Router, which contains the TCP connection request to Neon.  This is the frame in hexadecimal notation. 00e0 f923 a820 00a0 2471 e444 0800 4500 002c 9d08 4000 8006 8bff 808f 8990 808f 4715 065b 0050 0009 465b 0000 0000 6002 2000 598e 0000 0204 05b4

61. Encapsulation & Demultiplexing

62. Encapsulation & Demultiplexing: Ethernet Header

63. Encapsulation & Demultiplexing: IP Header

65. Encapsulation & Demultiplexing: TCP Header Option: maximum segment size

66. Encapsulation & Demultiplexing: TCP Header

67. Encapsulation & Demultiplexing: Application data

68. Different Views of Networking  Different Layers of the protocol stack have a different view of the network. This is HTTP’s and TCP’s view of the network.

69. Network View of IP Protocol

70. Network View of Ethernet  Ethernet’s view of the network