mạng máy tính nâng cao nguyễn đức thái chương 4 network sinhvienzone com

Chapter 4: Network Layer RIP  OSPF  BGP  4.7 Broadcast and multicast routing SinhVienZone.Com... Network layer transport segment from sending to receiving host  network layer proto

Chapter 4

Network Layer

A note on the use of these ppt slides:

We’re making these slides freely available to all (faculty, students, readers)

They’re in PowerPoint form so you can add, modify, and delete slides

(including this one) and slide content to suit your needs They obviously

represent a lot of work on our part In return for use, we only ask the

following:

 If you use these slides (e.g., in a class) in substantially unaltered form,

that you mention their source (after all, we’d like people to use our book!)

 If you post any slides in substantially unaltered form on a www site, that

you note that they are adapted from (or perhaps identical to) our slides, and

note our copyright of this material.

Chapter 4: Network Layer

Chapter goals:

 understand principles behind network layer

services:

 network layer service models

 forwarding versus routing

 how a router works

 routing (path selection)

 dealing with scale

 advanced topics: IPv6, mobility

 instantiation, implementation in the InternetSinhVienZone.Com

Chapter 4: Network Layer

 RIP

 OSPF

 BGP

 4.7 Broadcast and multicast routing

SinhVienZone.Com

Network layer

 transport segment from

sending to receiving host

 network layer protocols

in every host, router

 router examines header

fields in all IP datagrams

passing through it

application transport

network

data link physical

application transport

network

data link physical

network

data link physical network

data link physical

network

data link physical

network

data link physical

network

data link physical

network

data link physical

network

data link physical

network

data link physical

network

data link physical

network

data link physical

network

data link physical

SinhVienZone.Com

Two Key Network-Layer Functions

 forwarding: process

of getting through single interchange

SinhVienZone.Com

2 3

3 2 2 1

Interplay between routing and forwarding

SinhVienZone.Com

Connection setup

 3rd important function in some network architectures:

 ATM, frame relay, X.25

 before datagrams flow, two end hosts and intervening routers establish virtual connection

 routers get involved

 network vs transport layer connection service:

 network: between two hosts (may also involve

intervening routers in case of VCs)

 transport:SinhVienZone.Combetween two processes

Network service model

Q: What service model for “channel” transporting

datagrams from sender to receiver?

Example services for

 guaranteed minimum bandwidth to flow

 restrictions on changes in inter-packet spacing

SinhVienZone.Com

Network layer service models:

VBR ABR UBR

Bandwidth none

constant rate

guaranteed rate

guaranteed minimum none

Loss no yes yes no no

Order no yes yes yes yes

Timing no

yes yes no no

Congestion feedback

no (inferred via loss) no

congestion no

congestion yes

no Guarantees ?

SinhVienZone.Com

Chapter 4: Network Layer

 RIP

 OSPF

 BGP

 4.7 Broadcast and multicast routing

SinhVienZone.Com

Network layer connection and

 no choice: network provides one or the other

 implementation: SinhVienZone.Comin network core

Virtual circuits

 call setup, teardown for each call before data can flow

 each packet carries VC identifier (not destination host

address)

 every router on source-dest path maintains “state” for

each passing connection

 link, router resources (bandwidth, buffers) may be

allocated to VC (dedicated resources = predictable service)

“source-to-dest path behaves much like telephone

circuit”

 performance-wise

 network actions along source-to-dest path

SinhVienZone.Com

VC implementation

a VC consists of:

1. path from source to destination

2. VC numbers, one number for each link along

path

3. entries in forwarding tables in routers along

path

(rather than dest address)

New VC number comes from forwarding table

SinhVienZone.Com

Forwarding table

1 2 3

VC number

interface number Incoming interface Incoming VC # Outgoing interface Outgoing VC #

1 12 3 22

2 63 1 18

3 7 2 17

1 97 3 87

… … … …

Forwarding table in

northwest router:

Routers maintain connection state information!

SinhVienZone.Com

Virtual circuits: signaling protocols

 used to setup, maintain teardown VC

 used in ATM, frame-relay, X.25

 not used in today‟s Internet

1 Initiate call 2 incoming call3 Accept call

4 Call connected5 Data flow begins

6 Receive data

SinhVienZone.Com

Datagram networks

 no call setup at network layer

 routers: no state about end-to-end connections

 no network-level concept of “connection”

 packets forwarded using destination host address

 packets between same source-dest pair may take

1 Send dataSinhVienZone.Com2 Receive data

SinhVienZone.Com

Longest prefix matching

Prefix Match Link Interface

Datagram or VC network: why?

 can adapt, perform

control, error recovery

 simple inside network,

SinhVienZone.Com

Chapter 4: Network Layer

 RIP

 OSPF

 BGP

 4.7 Broadcast and multicast routing

SinhVienZone.Com

Router Architecture Overview

Two key router functions:

 run routing algorithms/protocol (RIP, OSPF, BGP)

 forwarding datagrams from incoming to outgoing link

SinhVienZone.Com

Input Port Functions

Three types of switching fabrics

SinhVienZone.Com

Switching Via Memory

First generation routers:

 traditional computers with switching under direct

control of CPU

packet copied to system‟s memory

 speed limited by memory bandwidth (2 bus

crossings per datagram)

Input Port

Output Port Memory

System Bus

SinhVienZone.Com

Switching Via a Bus

 datagram from input port memory

to output port memory via a shared

bus

 bus contention: switching speed

limited by bus bandwidth

 32 Gbps bus, Cisco 5600: sufficient

speed for access and enterprise

routers SinhVienZone.Com

Switching Via An Interconnection

Network

 overcome bus bandwidth limitations

 Banyan networks, other interconnection nets

initially developed to connect processors in

multiprocessor

 advanced design: fragmenting datagram into fixed

length cells, switch cells through the fabric

 Cisco 12000: switches 60 Gbps through the

interconnection networkSinhVienZone.Com

Output Ports

 Buffering required when datagrams arrive from

fabric faster than the transmission rate

 Scheduling discipline chooses among queued

datagrams for transmission

SinhVienZone.Com

Output port queueing

 buffering when arrival rate via switch exceeds

output line speed

 queueing (delay) and loss due to output port

buffer overflow!

SinhVienZone.Com

How much buffering?

equal to “typical” RTT (say 250 msec) times

link capacity C

 e.g., C = 10 Gps link: 2.5 Gbit buffer

 Recent recommendation: with N flows,

buffering equal to RTT C.

N

SinhVienZone.Com

Input Port Queuing

 Fabric slower than input ports combined -> queueing may occur at input queues

 Head-of-the-Line (HOL) blocking: queued datagram

at front of queue prevents others in queue from

moving forward

 queueing delay and loss due to input buffer overflow!

SinhVienZone.Com

Chapter 4: Network Layer

 RIP

 OSPF

 BGP

 4.7 Broadcast and multicast routing

SinhVienZone.Com

The Internet Network layer

forwarding table

Host, router network layer functions:

Network

layer

SinhVienZone.Com

Chapter 4: Network Layer

 RIP

 OSPF

 BGP

 4.7 Broadcast and multicast routing

SinhVienZone.Com

IP datagram format

32 bits

data (variable length, typically a TCP

or UDP segment)

16-bit identifier

header checksum

time to live

32 bit source IP address

IP protocol version

number header length

(bytes)

max number remaining hops (decremented at

each router)

for fragmentation/ reassembly

total datagram length (bytes)

upper layer protocol

to deliver payload to

head.

len

type of service

“type” of data flgs fragment

offset upper

layer

32 bit destination IP address

Options (if any) E.g timestamp,

record route taken, specify list of routers

IP Fragmentation & Reassembly

 network links have MTU

(max.transfer size) - largest

possible link-level frame.

 different link types,

different MTUs

 large IP datagram divided

(“fragmented”) within net

 one datagram becomes

several datagrams

 “reassembled” only at final

destination

 IP header bits used to

identify, order related

IP Fragmentation and Reassembly

SinhVienZone.Com

Chapter 4: Network Layer

 RIP

 OSPF

 BGP

 4.7 Broadcast and multicast routing

SinhVienZone.Com

and physical link

 router‟s typically have

223.1.3.2 223.1.3.1

223.1.3.27

223.1.1.1 = 11011111 00000001 00000001 00000001

SinhVienZone.Com

 device interfaces with

same subnet part of IP

address

 can physically reach

each other without

223.1.3.2 223.1.3.1

223.1.3.27

network consisting of 3 subnets

subnet

SinhVienZone.Com

subnets, detach each

interface from its

223.1.3.2 223.1.3.1

223.1.3.27

223.1.1.2

223.1.7.0

223.1.7.1 223.1.8.0

223.1.8.1 223.1.9.1

223.1.9.2

SinhVienZone.Com

IP addressing: CIDR

CIDR: C lassless I nter D omain R outing

 subnet portion of address of arbitrary length

 address format: a.b.c.d/x, where x is # bits in

subnet portion of address

11001000 00010111 00010000 00000000

subnet part

host part

200.23.16.0/23

SinhVienZone.Com

IP addresses: how to get one?

 hard-coded by system admin in a file

 Windows:

control-panel->network->configuration->tcp/ip->properties

 UNIX: /etc/rc.config

 DHCP: Dynamic Host Configuration Protocol:

dynamically get address from as server

 “plug-and-play” SinhVienZone.Com

DHCP: Dynamic Host Configuration Protocol

Goal: allow host to dynamically obtain its IP address

from network server when it joins network

Can renew its lease on address in use

Allows reuse of addresses (only hold address while connected

an “on”) Support for mobile users who want to join network (more

shortly)

DHCP overview:

 host broadcasts “DHCP discover” msg

 DHCP server responds with “DHCP offer” msg

 host requests IP address: “DHCP request” msg

 DHCP server sends address: “DHCP ack” msg

SinhVienZone.Com

arriving DHCP client needs address in this network

SinhVienZone.Com

transaction ID: 654

DHCP offer

src: 223.1.2.5, 67 dest: 255.255.255.255, 68 yiaddrr: 223.1.2.4

transaction ID: 654 Lifetime: 3600 secs

DHCP request

src: 0.0.0.0, 68 dest:: 255.255.255.255, 67 yiaddrr: 223.1.2.4

transaction ID: 655 Lifetime: 3600 secs

DHCP ACK

src: 223.1.2.5, 67 dest: 255.255.255.255, 68 yiaddrr: 223.1.2.4

transaction ID: 655 Lifetime: 3600 secs

SinhVienZone.Com

IP addresses: how to get one?

Q: How does network get subnet part of IP

Organization 7 11001000 00010111 00011110 00000000 200.23.30.0/23SinhVienZone.Com

Hierarchical addressing: route aggregation

“Send me anything with addresses beginning

Organization 1

ISPs-R-Us “Send me anythingwith addresses

beginning 199.31.0.0/16”

Hierarchical addressing: more specific

routes

ISPs-R-Us has a more specific route to Organization 1

“Send me anything with addresses beginning

IP addressing: the last word

A: ICANN: Internet Corporation for Assigned

Names and Numbers

 allocates addresses

 manages DNS

 assigns domain names, resolves disputes

SinhVienZone.Com

NAT: Network Address Translation

10.0.0.1 10.0.0.2

10.0.0.3

10.0.0.4 138.76.29.7

local network (e.g., home network)

10.0.0/24

rest of Internet

Datagrams with source or destination in this network have 10.0.0/24 address for source, destination (as usual)

All datagrams leaving local

network have same single source

NAT IP address: 138.76.29.7,

different source port numbersSinhVienZone.Com

NAT: Network Address Translation

 Motivation: local network uses just one IP address as

far as outside world is concerned:

 range of addresses not needed from ISP: just one IP address for all devices

 can change addresses of devices in local network

without notifying outside world

 can change ISP without changing addresses of

devices in local network

 devices inside local net not explicitly addressable,

visible by outside world (a security plus).SinhVienZone.Com

NAT: Network Address Translation

Implementation: NAT router must:

#) of every outgoing datagram to (NAT IP address, new port #)

remote clients/servers will respond using (NAT

IP address, new port #) as destination addr

IP address, port #) to (NAT IP address, new port #) translation pair

port #) in dest fields of every incoming datagram

with corresponding (source IP address, port #)

SinhVienZone.Com

NAT: Network Address Translation

10.0.0.1 10.0.0.2

10.0.0.3

S: 10.0.0.1, 3345 D: 128.119.40.186, 80

1

10.0.0.4 138.76.29.7

1: host 10.0.0.1 sends datagram to 128.119.40.186, 80

NAT translation table WAN side addr LAN side addr

138.76.29.7, 5001

4: NAT router changes datagram dest addr from 138.76.29.7, 5001 to 10.0.0.1, 3345

SinhVienZone.Com

NAT: Network Address Translation

 16-bit port-number field:

 60,000 simultaneous connections with a single

LAN-side address!

 NAT is controversial:

 routers should only process up to layer 3

 violates end-to-end argument

• NAT possibility must be taken into account by app designers, eg, P2P applications

 address shortage should instead be solved by

IPv6 SinhVienZone.Com

NAT traversal problem

 client wants to connect to

server with address 10.0.0.1

 server address 10.0.0.1 local

to LAN (client can‟t use it as

138.76.29.7

Client

?

SinhVienZone.Com

NAT traversal problem

 solution 2: Universal Plug and

Play (UPnP) Internet Gateway

Device (IGD) Protocol Allows

NATted host to:

 learn public IP address

(138.76.29.7)

 add/remove port mappings

(with lease times)

i.e., automate static NAT port

map configuration

10.0.0.1

10.0.0.4

NAT router

138.76.29.7

IGD

SinhVienZone.Com

NAT traversal problem

 solution 3: relaying (used in Skype)

 NATed client establishes connection to relay

 External client connects to relay

 relay bridges packets between to connections

138.76.29.7

Client

10.0.0.1

NAT router

1 connection to relay initiated

SinhVienZone.Com

Chapter 4: Network Layer

 RIP

 OSPF

 BGP

 4.7 Broadcast and multicast routing

SinhVienZone.Com

ICMP: Internet Control Message Protocol

 used by hosts & routers to

 ICMP message: type, code plus

first 8 bytes of IP datagram

causing error

Type Code description

0 0 echo reply (ping)

3 0 dest network unreachable

3 1 dest host unreachable

3 2 dest protocol unreachable

3 3 dest port unreachable

3 6 dest network unknown

3 7 dest host unknown

4 0 source quench (congestion

control - not used)

8 0 echo request (ping)

Traceroute and ICMP

 Source sends series of

UDP segments to dest

 First has TTL =1

 Second has TTL=2, etc.

 Unlikely port number

 When nth datagram arrives

to nth router:

 Router discards datagram

 And sends to source an

ICMP message (type 11,

 Traceroute does this 3 times

Stopping criterion

 UDP segment eventually arrives at destination host

 Destination returns ICMP

“host unreachable” packet (type 3, code 3)

 When source gets this ICMP, stops.

SinhVienZone.Com

Chapter 4: Network Layer

 RIP

 OSPF

 BGP

 4.7 Broadcast and multicast routing

SinhVienZone.Com