network protocols

12
Network Protocols ISO OSI 7-layer model TCP/IP suite TCP/UDP IP Ethernet/Token Ring ICMP

Upload: mara-peters

Post on 13-Mar-2016

31 views

Category:

Documents


3 download

DESCRIPTION

Network Protocols. ISO OSI 7-layer model TCP/IP suite TCP/UDP IP Ethernet/Token Ring ICMP. Protocol Layers. Network communication is divided up into seven layers Each layer deals with one particular aspect of the communication - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Network Protocols

Network Protocols

ISO OSI 7-layer model TCP/IP suite

TCP/UDP IP Ethernet/Token Ring ICMP

Page 2: Network Protocols

Protocol Layers Network communication is divided up into seven layers

Each layer deals with one particular aspect of the communication

Each layer uses a set of routines provided by the layer below it

Each layer ignores lower-level (and higher-level) details and problems

Each layer takes a message passed down to it by a higher layer, adds some header information, and passes the message on to a lower layer

Each layer has the illusion of peer-to-peer communication

Eventually the message reaches the bottom layer, and get physically sent across the network

Page 3: Network Protocols

ISO OSI 7-layer protocol scheme

Page 4: Network Protocols

ISO OSI protocol summary Application layer — provides network access to application

programs

Examples: telnet, ftp, email (SMTP)

Presentation layer — provides freedom from machine-dependent representations - maintains structured information - arrays, records, etc: translates between machine presentations if necessary, encryption/decryption, compression/decompression

Session layer — provides communication/synchronization between processes, Not required in connectionless communication

Example: Remote Procedure Call (RPC)

Transport layer — accepts messages of arbitrary length between hosts, error control for out-of-sequence and missing packets

Examples: TCP (connection-oriented), UDP (connectionless)

Page 5: Network Protocols

ISO OSI protocol summary (cont.) Network layer — provides switching and routing needed to (1)

establish, maintain, and terminate switched connections, and (2) transfer data (packets) between end systems

Examples: IP (connectionless), X.25 (connection-oriented)

Data link layer — reliably transfers packets (broken up into frames) over a communication link, error correction within frame/ flow control

Examples: Ethernet

Physical layer —converts 1s and 0s into electrical or optical signals, and transmits frames of bits across a wire / cable

Examples: RS-232-C (serial communication lines), X.21

Page 6: Network Protocols

TCP/IP Protocol suite Upper layers

ftp — file transfer protocol Sends files from one system to another under user

command Handles both text and binary files Supports userids and passwords

telnet — remote terminal protocol Lets a user at one terminal log onto a remote host

smtp — simple mail transfer protocol Transfers mail messages between hosts Handles mailing lists, forwarding, etc. Does not specify how mail messages are created

dns — domain name service Maps names into IP addresses A domain may be split into subdomains Name severs are usually replicated to improve reliability

Page 7: Network Protocols

TCP

TCP — Transmission Control Protocol Connection-oriented (3-way handshake) On transmit side, breaks message into packets, assigns sequence

numbers, and and sends each packet in turn Sends to a particular IP address and port Flow control — doesn’t send more packets than receiver is

prepared to receive On receive side, receives packets, reassembles them into messages

Computes a checksum for each packet and compares it to checksum sent, discards packet if checksums don’t agree

Reorders out-of-order packets Reliable

Packets must be acknowledged If sender doesn’t receive an acknowledgment after a short period,

it retransmits that packet Congestion control — don’t overwhelm the network

Page 8: Network Protocols

IP IP — Internet Protocol

Connectionless

Unreliable Packets may be lost, duplicated, or delivered out of order

Forward packet from sender through some number of gateways (routers) until it reaches the final destination

A gateway accepts a packet from one network and forwards it to a host or gateway on another network

Destination has specific Internet address, which is composed of two parts: network part — network the host is on address part — specific host on network

Routing is dynamic — each gateway chooses the next gateway to send the packet to

Gateways send each other information about network congestion and gateways which are down

Page 9: Network Protocols

Ethernet Network is a bus – broadcast to anyone who cares to listen Every Ethernet device (everywhere in the world!) has a unique address

The Institute of Electrical and Electronics Engineers (IEEE) allocates addresses to manufacturers, who build a unique address into each Ethernet device

Transmission – Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Carrier sense: listen before broadcasting, defer until channel is

clear, then broadcast Collision detection: listen while broadcasting

If two hosts transmit at same time —collision — the data gets garbled

Each jams network (short jammed signal is issued), then waits a random (but increasing) amount of time, and tries again

Page 10: Network Protocols

Token Ring

Devices are joined in a ring Transmission

unique message (token) is circulated in the ring Token is free when no device is transmitting To transmit, a host waits for a free token, attaches its message to

it, sent the token status to busy, and sends it on Destination removes the message, sets the token status to free,

and sends it on Advantage: not sensitive to load Disadvantage: complexity – token maintenance is complex

Page 11: Network Protocols

ICMP A part of IP that is less widely known is the Internet Control Message

Protocol (ICMP)

Allows gateways and hosts to exchange bootstrapping information, report errors, and test the liveliness of the network

Some useful programs using ICMP:

traceroute /usr/contrib/bin/traceroute Displays route taken to reach destination, time for each hop Sends multiple (?) 20-byte packets

ping /usr/sbin/ping Tests that destination is up and reachable Sends ICMP echo request to destination Destination sends ICMP echo reply Sends 64-byte packets repeatedly

Page 12: Network Protocols

Example routing - taceroute

mymachine:~% traceroute www.cis.ksu.edutraceroute to polaris.cis.ksu.edu (129.130.10.93), 30 hops max, 40 byte packets 1 wraith.facnet.mcs.kent.edu (131.123.46.1) 0.878 ms 0.620 ms 0.553 ms 2 ghost.uis-mcs.mcs.kent.edu (131.123.40.1) 6.000 ms 3.366 ms 2.632 ms 3 lib2-255x248-e37-lib.gate.kent.edu (131.123.255.254) 7.170 ms 3.552 ms 4.477 ms 4 twcneo-cw.neo.rr.com (204.210.223.3) 9.515 ms 15.167 ms 18.687 ms 5 bordercore4-hssi1-0.NorthRoyalton.cw.net (166.48.233.253) 17.864 ms 10.971 ms

14.652 ms 6 core4.WillowSprings.cw.net (204.70.4.73) 23.438 ms 22.099 ms 17.397 ms 7 wsp-sprint2-nap.WillowSprings.cw.net (206.157.77.94) 18.367 ms 22.854 ms 20.267 ms 8 sl-bb11-chi-2-1.sprintlink.net (144.232.10.157) 23.518 ms 24.528 ms 18.757 ms 9 sl-bb12-chi-5-1.sprintlink.net (144.232.10.6) 21.197 ms 31.452 ms 15.050 ms10 sl-bb10-kc-7-1.sprintlink.net (144.232.9.117) 46.752 ms * 40.125 ms11 sl-gw5-kc-0-0-0.sprintlink.net (144.232.2.62) 38.360 ms 48.002 ms 44.795 ms12 sl-uok-1-0-0.sprintlink.net (144.232.132.14) 93.256 ms 67.070 ms 61.727 ms13 ks-1-ks-ksu.r.greatplains.net (164.113.232.193) 77.743 ms 64.566 ms 67.117 ms14 164.113.212.250 (164.113.212.250) 59.988 ms 46.188 ms 55.616 ms15 129.130.252.9 (129.130.252.9) 68.211 ms 67.881 ms 75.441 ms16 polaris.cis.ksu.edu (129.130.10.93) 76.462 ms 54.838 ms *