
2/147

Informationand

Communica

tionengineer

ing(ICE)

MUT

Class IV

ICMPv4, IPv6 ICMPv6

. (ICE)

MUTEmail:[email protected]

: F402: (02)9883655 220: 065343850


3/147

Informationand

Communica

tionengineering(ICE)

MUT

Introduction

ICMPv4

IPv6

ICMPv6


4/147

Informationand

Communica


MUT

Introduction

3 TCP/IP

IGMP = will talk in the class of multicasting

ICMPv4= This class

IPv4 = Last Class

ARP = Last Classes

IPv6 = This class

ICMPv6 = This class


5/147

Inf

ormationand

Communica


MUT

Introduction

ICMPv4

IPv6

ICMPv6


6/147

Inf

ormationand

Communicationengineering(ICE)

MUT

Upon completion you will be able to:Be familiar with the ICMP message format

Know the types of error reporting messages

Know the types of query messagesBe able to calculate the ICMP checksum

Know how to use the ping and traceroute commands

Understand the modules and interactions of an ICMP package

Objectives

Internet Control Message ProtocolInternet Control Message Protocolversion 4version 4


7/147

Inf

ormationand


MUT

Position of ICMP in the network


8/147

Inf

ormationand


MUT

ICMP encapsulation

ICMP is network layer protocol but i ts messages

are first encapsulated inside IP datagrams

Protocol Field in IP header =1


9/147

Inf

ormationand


MUT

ICMP messages are divided into errorICMP messages are divided into error--reporting messages and queryreporting messages and query

messages. The errormessages. The error--reporting messages report problems that a router orreporting messages report problems that a router ora host (destination) may encounter. The query messages get specia host (destination) may encounter. The query messages get specificfic

information from a router or another host.information from a router or another host.

TYPES OF MESSAGES


10/147

Inf

ormationand


MUT

ICMP messagesICMP messages


11/147

Inf

ormationand


MUT

An ICMP message has an 8An ICMP message has an 8--byte header and a variablebyte header and a variable--size data section.size data section.

Although the general format of the header is different for eachAlthough the general format of the header is different for eachmessagemessage

type, the first 4 bytes are common to all.type, the first 4 bytes are common to all.

MESSAGE FORMAT

Type : defined in the previous sl ide

Code: the reason for particular message types

Checksum: calculated over the entire message (header and data).calculated over the entire message (header and data).

Rest of the header: specific for each message types

DATA: Error message information for finding the error packetQuery messages extra information


12/147

Inf

ormationand


MUT

IP, as an unreliable protocol, is not concerned with error checkIP, as an unreliable protocol, is not concerned with error checking anding and

error control. ICMP was designed, in part, to compensate for thierror control. ICMP was designed, in part, to compensate for thissshortcoming. ICMP does not correct errors, it simply reports theshortcoming. ICMP does not correct errors, it simply reports them.m.

The topics discussed in this section include:The topics discussed in this section include:

Destination UnreachableDestination Unreachable

Source QuenchSource QuenchTime ExceededTime Exceeded

Parameter ProblemParameter Problem

RedirectionRedirection

ERROR REPORTING


13/147

Inf

ormationand


MUT

Error-reporting messages

ICMP always reports error messagesto the original source.


14/147

Inf

ormationand


MUT

The following are important points about ICMP

error messages:

No ICMP error message will be generated in response

to a datagram carrying an ICMP error message.

No ICMP error message will be generated for afragmented datagram that is not the first fragment.

No ICMP error message will be generated for a

datagram having a multicast address.

No ICMP error message will be generated for a

datagram having a special address such as 127.0.0.0 or

0.0.0.0.

Note:Note:


15/147

Informationand


MUT

Contents of data field for the error messages

8 bytes :

Received datagram IP header:

Sent datagram IP header :


16/147

Informationand


MUT

Destination-unreachable format


17/147

Informationand


MUT

Error code

0 : The network is unreachable

1 : The host is unreachable

2 : The protocol is unreachable 3 : The port is unreachable

4 : Fragmentation is required

5 : Source routing could not be accomplished

6 : The destination network is unknown

7 : The destination host is unknown

8 : The source is isolated

9 : Communication with the destination network is administratively prohibited

10 : Communication with the destination host is administratively prohibited

11 : The network is unreachable for the specified type of service

12 : The host is unreachable for the specified type of service

13 : The host is unreachable because the administrator has put a filter on it

14 : The host is unreachable because the host precedence is violated

15 : The host is unreachable because the host precedence was cut off

Destination-unreachable

messages with codes 2 or 3 can

be created only by the

destination host.

Other destination-unreachable

messages can be created only by

routers.


18/147

Informationand

Communicationengineeri

ng(ICE)

MUT

Precedence

14 Host Precedence Violation. Sent by the first hop router to a host to indicate that a requested precedence is not

permitted for the particular combination of source/destination host or network, upper layer protocol, and

source/destination port;

15 Precedence cutoff in effect. The network operators have imposed a minimum level of precedence required for

operation, the datagram was sent with a precedence below this level;

The precedence subfield was designed, butnever used in version 4.


19/147

Informationand


ng(ICE)

MUT

A router cannot detect all problems

that prevent the delivery of a packet.

Note:Note:

There is no flow-control mechanism

in the IP protocol.


20/147

Informationand


ng(ICE)

MUT

Source-quench format

Cause of Congestion

A source-quench message informs the source that a datagram hasbeen discarded due to congestion in a router or the destination host.

The source must slow down the sending of datagrams until the

congestion is relieved.


21/147

Informationand

Communicat

ionengineeri

ng(ICE)

MUT

One source-quench message is sent

for each datagram that is discarded

due to congestion.

Note:Note:

Whenever a router decrements a datagram with a

time-to-live value to zero, it discards the datagram

and sends a time-exceeded message to the

original source.


22/147

Informationand

Communicat

ionengineeri

ng(ICE)

MUT

When the final destination does not

receive all of the fragments in a set

time, it discards the receivedfragments and sends a time-exceeded

message to the original source.

Note:Note:


23/147

Informationand

Communicat

ionengineering(ICE)

MUT

In a time-exceeded message,code 0 is

used only by routers to show that the

value of the time-to-live field is zero.Code 1 is used only by the destination

host to show that not all of the

fragments have arrived within a set

time.

Note:Note:


24/147

Informationand

Communicat

ionengineering(ICE)

MUT

Time-exceeded message format

- TTL

- Timeout


25/147

Informationand

Communicat

ionengineering(ICE)

MUT

Parameter-problem message format

0: Wrong header

1: Need options

A parameter-problem message can be created by a routeror the destination host.


26/147

Informationand

Communicat

ionengineering(ICE)

MUT

Redirection concept

A host usually starts with a smallrouting table that is gradually

augmented and updated. One of thetools to accomplish this is the

redirection message.


27/147

Informationand


MUT

Redirection message format

A redirection message is sent from a

router to a host on the same local

network.


28/147

Informationand


MUT

ICMP can also diagnose some network problems through the queryICMP can also diagnose some network problems through the query

messages, a group of four different pairs of messages. In this tmessages, a group of four different pairs of messages. In this type ofype of

ICMP message, a node sends a message that is answered in a speciICMP message, a node sends a message that is answered in a specificficformat by the destination node.format by the destination node.


Echo Request and ReplyEcho Request and Reply

Timestamp Request and ReplyTimestamp Request and Reply

AddressAddress--Mask Request and ReplyMask Request and ReplyRouter Solicitation and AdvertisementRouter Solicitation and Advertisement

QUERY


29/147

Informationand


MUT

Query messages

An echo-request message can be sent by a host or router. An echo-

reply message is sent by the host or router which receives an echo-

request message.

Echo-request and echo-reply messagescan test the reachability of a host. This

is usually done by invoking theping

command.


30/147

Info

rmationand


MUT

Echo-request and echo-reply messages


31/147

Info

rmationand


MUT

Echo-request and echo-reply messages


32/147

Info

rmationand


MUT

Timestamp-request and timestamp-reply messages can be

used to calculate the round-trip time between a source

and a destination machine even if their clocks are notsynchronized.

Note:Note:

The timestamp-request and timestamp-reply messages canbe used to synchronize two clocks in two machines if the

exact one-way time duration is known.


33/147

Info

rmationand


MUT

Mask-request and mask-reply message format


34/147

Info

rmationand


MUT

Router-solicitation message format


35/147

Info

rmationandCommunicationengineering(ICE)

MUT

Router-advertisement message format


36/147

Info


MUT

In ICMP the checksum is calculated over the entire message (heaIn ICMP the checksum is calculated over the entire message (headerder

and data).and data).


Checksum CalculationChecksum Calculation

Checksum TestingChecksum Testing

CHECKSUM


37/147

Info


MUT

The following Figure shows an example of checksum

calculation for a simple echo-request message. We randomlychose the identifier to be 1 and the sequence number to be 9.

The message is divided into 16-bit (2-byte) words. The words

are added together and the sum is complemented. Now the

sender can put this value in the checksum field.

See Next Slide

Example 1


38/147

Info

rmationandCommunicationengineerin

g(ICE)

MUT

Example of checksum calculation


39/147

Info


g(ICE)

MUT

Two tools that use ICMP for debugging:Two tools that use ICMP for debugging:pingpingandandtraceroutetraceroute..


PingPing

TracerouteTraceroute

DEBUGGING TOOLS


40/147

Info


g(ICE)

MUT

We use the ping program to test the server fhda.edu. The resu

is shown below:

See Next Slide

$ ping fhda.edu

PING fhda.edu (153.18.8.1) 56 (84) bytes of data.

64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=0 ttl=62 time=1.91 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=1 ttl=62 time=2.04 ms

64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=2 ttl=62 time=1.90 ms



Example 2


41/147

Info


g(ICE)

MUT



64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=7 ttl=62 time=1.94 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=8 ttl=62 time=1.97 ms



--- fhda.edu ping statistics ---11 packets transmitted, 11 received, 0% packet loss, time 10103ms

rtt min/avg/max = 1.899/1.955/2.041 ms

Example 2 (Continued)


42/147

Info

rmationandCommunicati

onengineerin

g(ICE)

MUT

For the this example, we want to know if the adelphia.net mail server is alive and running. The

result is shown below:

$ ping mail.adelphia.net

PING mail.adelphia.net (68.168.78.100) 56(84) bytes of data.

64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=0 ttl=48 time=85.4 ms

64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=1 ttl=48 time=84.6 ms64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=2 ttl=48 time=84.9 ms



See Next Slide

Example 3


43/147

Info


onengineerin

g(ICE)

MUT









--- mail.adelphia.net ping statistics ---

14 packets transmitted, 13 received, 7% packet loss, time 13129ms

rtt min/avg/max/mdev = 84.207/84.694/85.469

Example 3


44/147

Info


onengineerin

g(ICE)

MUT

We use the traceroute program to find the route from the

computer voyager.deanza.edu to the server fhda.edu. The

following shows the result:

See Next Slide

$ traceroute fhda.edutraceroute to fhda.edu (153.18.8.1), 30 hops max, 38 byte packets

1 Dcore.fhda.edu (153.18.31.254) 0.995 ms 0.899 ms 0.878 ms2 Dbackup.fhda.edu (153.18.251.4) 1.039 ms 1.064 ms 1.083 ms

3 tiptoe.fhda.edu (153.18.8.1) 1.797 ms 1.642 ms 1.757 ms

Example 4


45/147

Info


onengineerin

g(ICE)

MUT

The un-numbered line after the command shows that the destination is 153.18.8.1. The TTL value is 30 hops.

The packet contains 38 bytes: 20 bytes of IP header, 8 bytes of UDP header, and 10 bytes of application data. The

application data is used by traceroute to keep track of the packets.

The first line shows the first router visited. The router is named Dcore.fhda.edu with IP address

153.18.31.254. The first round trip time was 0.995 milliseconds, the second was 0.899 milliseconds, and the third

was 0.878 milliseconds.

The second line shows the second router visited. The router is named Dbackup.fhda.edu with IP address

153.18.251.4. The three round trip times are also shown.

The third line shows the destination host. We know that this is the destination host because there are no more

lines. The destination host is the server fhda.edu, but it is named tiptoe. fhda.edu with the IP address 153.18.8.1.

The three round trip times are also shown.

Example 4 (Continued)


46/147

Info


onengineerin

g(ICE)

MUT

In this example, we trace a longer route, the route to xerox.com

$ traceroute xerox.comtraceroute to xerox.com (13.1.64.93), 30 hops max, 38 byte packets1 Dcore.fhda.edu (153.18.31.254) 0.622 ms 0.891 ms 0.875 ms

2 Ddmz.fhda.edu (153.18.251.40) 2.132 ms 2.266 ms 2.094 ms

...

18 alpha.Xerox.COM (13.1.64.93) 11.172 ms 11.048 ms 10.922 ms

Here there are 17 hops between source and destination. Note that some round trip times look unusual. It could be

that a router is too busy to process the packet immediately.

Example 5


47/147

Info


g(ICE)

MUT

An interesting point is that a host can send a traceroute packet to itself. This can be done by

specifying the host as the destination. The packet goes to the loopback address as we expect.

$ traceroute voyager.deanza.edutraceroute to voyager.deanza.edu (127.0.0.1), 30 hops max, 38 byte packets

1 voyager (127.0.0.1) 0.178 ms 0.086 ms 0.055 ms

Example 6


48/147

Info


g(ICE)

MUT

Finally, we use the traceroute program to find the route

between fhda.edu and mhhe.com (McGraw-Hill server). We

notice that we cannot find the whole route. When traceroutedoes not receive a response within 5 seconds, it prints an

asterisk to signify a problem, and then tries the next hop..

$ traceroute mhhe.comtraceroute to mhhe.com (198.45.24.104), 30 hops max, 38 byte packets1 Dcore.fhda.edu (153.18.31.254) 1.025 ms 0.892 ms 0.880 ms

2 Ddmz.fhda.edu (153.18.251.40) 2.141 ms 2.159 ms 2.103 ms

3 Cinic.fhda.edu (153.18.253.126) 2.159 ms 2.050 ms 1.992 ms

...

16 * * *

17 * * *

...............

Example 7

I


49/147

Info


g(ICE)

MUT

To give an idea of how ICMP can handle the sending and receivingTo give an idea of how ICMP can handle the sending and receiving ofof

ICMP messages, we present our version of an ICMP package made ofICMP messages, we present our version of an ICMP package made of

two modules: an input module and an output module.two modules: an input module and an output module.


Input ModuleInput Module

Output ModuleOutput Module

ICMP PACKAGE

I


50/147

Info

rmationandC

ommunicationengineerin

g(ICE)

MUT

ICMP package

I


51/147

Info

rmationandC


g(ICE)

MUT

?

I


52/147

Info

rmationandC


g(ICE)

MUT

1 2 3

A

IPA=1

D

C

IPA=8

L5

L4

L3

L2

L1 L1

L3

L2

L1

L2

L1

L3

L2

L1

L2

L1

L3

L2

L1

L2

L1

L5

L4

L3

L2

L1L1

1010101011.. 101011.. 101011.. 101010.. 1010101010001011..

B

IPA1=2, IPA2=3 IPA1=4, IPA2=5 IPA1=6, IPA2=7

SA=Source IP Address

DA=Destination IP Address

IPA=IP Address

IPA1=X,IPA2=Z IPA1=W,IPA2=Y

H 1 8 DATA

H SA DA DATA

A

B

C

D E

F

G

ICMP

A, B, C, D, E, F,G

In


53/147

nformationandC


g(ICE)

MUT

A =

B = C = error

D =

E =

F =

G = error

In


54/147

nformationandC


g(ICE)

MUT

Exercise 13: How can we determine if an IP packet is carrying an

ICMP packet?

In


55/147

nformationandC


g(ICE)

MUT

Protocol field in IP header = 1

In


56/147

nformationandC


g(ICE)

MUT

Exercise 17: An ICMP message has arrived with the header (in

hexadecimal): 03 03 10 20 00 00 00 00 00 What is the type of the message?

What is the code ?

What is purpose of the message ?

In


57/147

nformationandC


g(ICE)

MUT

What is the type of the message?

Type = 03 = destination is unreachable

What is the code ? Code = 03 = the port is not available

What is purpose of the message ?

Informs the sender that the port is not available

In


58/147

nformationandC


g(ICE)

MUT

IPv4

IPv4

In

( i )


59/147

nformationandC


g(ICE)

MUT

(port scanning)

UDP

ICMP packets ICMP

Code = 3

Inf


60/147

formationandC


g(ICE)

MUT

Introduction

ICMPv4

IPv6

ICMPv6

Inf

N G i IP 6 d ICMP 6N t G ti IP 6 d ICMP 6


61/147

formationandC

ommunicationengineering(ICE)

MUT

Upon completion you will be able to:

Understand the shortcomings of IPv4

Know the IPv6 address format, address types, and abbreviations

Be familiar with the IPv6 header format

Know the extension header typesKnow the differences between ICMPv4 and ICMPv6

Know the strategies for transitioning from IPv4 to IPv6

Objectives

Next Generation: IPv6 and ICMPv6Next Generation: IPv6 and ICMPv6

Inf

IP 6


62/147

formationandC

ommunicatio

nengineering(ICE)

MUT

IPv6 has these advantages over IPv4:IPv6 has these advantages over IPv4:

1.1. larger address spacelarger address space 128 bits 32 bits128 bits 32 bits2.2. better header formatbetter header format keep header overhead to a minimumkeep header overhead to a minimum3.3. new optionsnew options additional functionalitiesadditional functionalities4.4. allowance for extensionallowance for extension for new technologies or applicationsfor new technologies or applications5.5. support for resource allocationsupport for resource allocation using flow label forusing flow label for QoSQoS6.6.support for more securitysupport for more security confidentially and integrity of the packetsconfidentially and integrity of the packets


IPv6 AddressesIPv6 Addresses

Address Space AssignmentAddress Space Assignment

Packet FormatPacket Format

Comparison between IPv4 and IPv6Comparison between IPv4 and IPv6

IPv6

Inf

IPv6 address


63/147

formationandC

ommunicatio

nengineering(ICE)

MUT

IPv6 address

Info Abbreviated address


64/147

formationandC

ommunicatio

nengineering(ICE)

MUT

Abbreviated address

Info Abbreviated address with consecutive zeros


65/147

ormationandC

ommunicatio

nengineering(ICE)

MUT

Abbreviated address with consecutive zeros

1 IP

Info CIDR address


66/147

ormationandC

ommunicatio

nengineering(ICE)

MUT

CIDR address

Info Address structure


67/147

ormationandC

ommunicatio

nengineering(ICE)

MUT

Address structure

See next slide for types of prefix

Info

Type prefixes for IPv6 addressesType prefixes for IPv6 addresses


68/147

or

mationandC

ommunicatio

nengineering(ICE)

MUT

Type prefixes for IPv6 addressesType prefixes for IPv6 addresses

Info Provider-based address


69/147

or

mationandC

ommunicatio

nengineering(ICE)

MUT

Provider based address

Type identifier010:a provider-based addressRegistry11000:North America

01000:European

10100:Asian and Pacific countries

Info Address hierarchy


70/147

r

mationandC

ommunicatio

nengineering(ICE)

MUT

Address hierarchy

Provider prefixan ISP, variable-lengthSubscriber prefixan organization subscriber, 24 bitsSubnet prefixa network under a territory of the subscriber, 32 bitsNode Identifierthe identity of node connected to the subnet 48 bits

Infor Unspecified address


71/147

r

mationandC

ommunicatio

nengineering(ICE)

MUT

Unspecified address

For:

- a host does no know its own address

- A host sends an inquiry to find its address

Infor Loopback Address


72/147

r

mationandC

ommunicatio

nengineering(ICE)

MUT

p

For:

-used by a host to test itself without going on the networks

Infor Compatible address


73/147

r

mationandC

ommunicatio

nengineering(ICE)

MUT

p

-Used when a computer using IPv6 wants to send a packet to another computer using

IPv6

- the packet passes through IPv4 networks

IPv6 IPv4 IPv60x0220x0D130x11170x0E14

Infor Mapped address


74/147

r

mationandC

ommunicatio

nengineering(ICE)

MUT

pp

For:

-Used when a computer that has migrated

to IPv6 want to sent a packet to a computer

stil l using IPv4

Infor Link local address


75/147

mationandC

ommunicatio

nengineering(ICE)

MUT

For:

- Used in an isolated network

- Does not have a global effect

Infor Site local address


76/147

mationandC

ommunicatio

nengineering

(ICE)

MUT

For:

-Used for a site with several networks- Used in isolated networks

- Does not have a global effect

Infor Multicast address


77/147

mationandC

ommunicatio

nengineering

(ICE)

MUT

For:

- For a group of hosts

Inform IPv6 datagram


78/147

mationandC

ommunicatio

nengineering

(ICE)

MUT

Inform Format of an IPv6 datagram


79/147

mationandC

ommunicatio

nengineering

(ICE)

MUT

Flow label: a particular flow of data

Payload length: length of IP datagram excluding the base

header(40 bytes)

Next Header: Header following the base header

Hop l imit: TTL

Source Address: the original source IP address

Destination Address: the final destination IP address

Version: version 6

Priority: packet priorities

Inform Next header codesNext header codes


80/147

mationandC

ommunicatio

nengineering

(ICE)

MUT

Inform

Priorities for congestionPriorities for congestion--controlledcontrolled


81/147

mationandC

ommunicatio

nengineering

(ICE)

MUT

traffictraffic

Inform

Priorities forPriorities fornoncongestionnoncongestion--controlledcontrolled


82/147

mationandC

ommunicatio

nengineering

(ICE)

MUT

traffictraffic

Inform Comparison between IPv4 and IPv6 packet headerComparison between IPv4 and IPv6 packet header


83/147

mationandC

ommunicatio

nengineering

(ICE)

MUT

Inform Extension header format


84/147

mationandC

ommunicatio

nengineering

(ICE)

MUT

Inform Extension header types


85/147

ationandCommunicationengineering

(ICE)

MUT

Inform Hop-by-hop option header format


86/147


(ICE)

MUT

Used when the source needs to pass information to allrouter visited by the datagram

Informa

The format of options in a hop-by-hop option header


87/147


(ICE)

MUT

Informa

Pad1


88/147


(ICE)

MUT

Informa

PadN


89/147


(ICE)

MUT

Informa

Jumbo payload


90/147


(ICE)

MUT

For:

- normally the IP datagram can be a maximum of 65535 bytes

- Jumbo payload =2^32-1 (4,294,967,295 bytes)

Informat

Source routing


91/147


(ICE)

MUT

Informat

Source routing example


92/147


(ICE)

MUT

Inform

at

Fragmentation


93/147


(ICE)

MUT

- Only the source could do

- PATH MTU Discovery technique

-If no path MTU discovery, a size of 576 bytes of smaller

Inform

at

Authentication


94/147

tionandCommunicationengineering

(ICE)

MUT

Inform

ati

Calculation of authentication data


95/147

ionandCommunicationengineering

(ICE)

MUT

The authentication header validates the message sender

and ensures the integrity of data

Inform

ati

Encrypted security payload


96/147


(ICE)

MUT

Providing confidentiality () and guards against eavesdropping()

Inform

ati

Transport mode encryption


97/147


(ICE)

MUT

Inform

ati

Tunnel-mode encryption


98/147

onandCommunicationengineering

(ICE)

MUT

Inform

atio

Comparison between IPv4 options and IPv6Comparison between IPv4 options and IPv6

extensionextension headersheaders


99/147

onandCommunicationengineering

(ICE)

MUT

extensionextension headersheaders

Inform

atio


100/147

onandCo

mmunication

engineering

(ICE)

MUT

?

Inform

atio


101/147

onandCo

mmunication

engineering

(ICE)

MUT

Exercise 2: Show the original (unabbreviated) form of the following

address:

a. 0::0

b. 0:AA::0

c. 0:1234::3

d. 123::1:2

Inform

atio


102/147

onandCo

mmunication

engineering

(ICE)

MUT

a. 0::0

a. 0000:0000:0000:0000:0000:0000:0000:0000:0000

b. 0:AA::0

a. 0000:00AA:0000:0000:0000:0000:0000:0000:0000

c. 0:1234::3

a. 0000:1234:0000:0000:0000:0000:0000:0000:0003

d. 123::1:2

a. 0123:0000:0000:0000:0000:0000:0000:0001:0002

Inform

atio


103/147

onandCo

mmunication

engineering

(ICE)

MUT

Exercise 3: What is the type of the following addresses:

a. FE80::12

b. FEC0::24A2

c. FE02::0

d. 0::01

Inform

atio


104/147

nandCo

mmunication

engineering

(ICE)

MUT

a. FE80::12 11111110:1000000:12

a. Link local address

b. FEC0::24A211111110:1010000:24A2

a. Link local address

c. FF02::0 11111110:0000

a. Multicast

d. 0::01

a. Loopback Address

First 10 bits = 1111111010Link local addressFirst 10 bits = 1111111011Site local addressFirst byte = 11111111Multicast address

Inform

ation


105/147

nandCo

mmunication

engineering

(ICE)

MUT

Exercise 14: A host has the address 581E:1456:2314:ABCD::1211.

If the node identification is 48 bits and the subnet identification is 32

bits, find the provider prefix?

Inform

ation


106/147

nandCo

mmunication

engineering

(ICE)

MUT

581E:1456:2314:ABCD:0000:0000:0000:1211010110000011110:1456:2314:ABCD::1211

Node identifier = 48 bits

Subnet identifier = 32 bits

The prefix provider =581E:14

The provider prefix is the type identifierplus registry identifier plus provideridentifier (3 + 5 + 16 = 24 bits).

Inform

ation


107/147

nandCo

mmunication

engineering

(ICE)

MUT

Exercise 28: what is the ip-compatible address for 119.254.254.254?

Inform

ation


108/147

nandCo

mmunication

engineering

(ICE)

MUT

119.254.254.254->77.FE.FE.FE

IP-compatible = 0::77FE:FEFE

Inform

ation


109/147

nandCo

mmunication

engineering

(ICE)

MUT

Exercise 29: what is the ip-mapped address for 119.254.254.254?

Inform

ation


110/147

nandCo

mmunication

engineering

(ICE)

MUT

119.254.254.254->77.FE.FE.FE

IP-mapped address = 0::FFFF:77FE:FEFE

Inform

ation


111/147

andCo

mmunication

engineering

(ICE)

MUT

Introduction

ICMPv4

IPv6

ICMPv6

Inform

ation

ICMPv6


112/147

andCo

mmunication

engineering

(ICE)

MUT

ICMPv6, while similar in strategy to ICMPv4, has changes that maICMPv6, while similar in strategy to ICMPv4, has changes that makes itkes it

more suitable for IPv6. ICMPv6 has absorbed some protocols thatmore suitable for IPv6. ICMPv6 has absorbed some protocols that werewere

independent in version 4.independent in version 4.


Error ReportingError Reporting

QueryQuery

Inform

ation

Comparison of network layers in

version 4 and version 6


113/147

andCo

mmunication

engineering

(ICE)

MUT

Inform

ation

Categories of ICMPv6 messages


114/147

andCo

mmunication

engineering

(ICE)

MUT

Inform

ationa

General format of ICMP messages


115/147

andCo

mmunication

engineering

(ICE)

MUT

Inform

ationa

Error-reporting messages


116/147

andCo

mmunication

engineering

(ICE)

MUT

Destination Unreachable: The same concept as in ICMPv4Packet too big: a router receives a packet that is larger than MTU

Time exceed: Have not arrived within the time limit

Parameter problems: Error in header fields, an unrecognized

extension header, an unrecognized option

Redirection: the same concept as in ICMPv4

Inform

ationa

Comparison of errorComparison of error--reporting messages inreporting messages in

ICMPv4 and ICMPv6ICMPv4 and ICMPv6


117/147

andCo

mmunication

engineering(ICE)

MUT

Inform

ationa

Destination-unreachable message format


118/147

andCo

mmunication

engineering(ICE)

MUT

0: No path to destination

1: Communication is prohibited

2: Strict source routing is impossible.

3: Destination address is unreachable.

4: Port is not available.

Inform

ationa

Packet-too-big message format


119/147

andCo

mmunication

engineering(ICE)

MUT

Inform

ationan

Time-exceeded message format


120/147

ndCo

mmunication

engineering(ICE)

MUT

0: a hop limit field =0

1: not arrived within the time limit for fragments of datagram

Inform

ationan

Parameter-problem message format


121/147

ndCo

mmunication

engineering(ICE)

MUT

0: Error in header fields

1:an unrecognized extension header

2: an unrecognized option

Inform

ationan

Redirection message format


122/147

ndCo

mmunication

engineering(ICE)

MUT

Inform

ationan

Query messages


123/147

ndCommunication

engineering(ICE)

MUT

Inform

ationan

Echo request and reply messages


124/147

ndCommunication

engineering(ICE)

MUT

Inform

ationan

Router-solicitation and advertisement message formats


125/147

ndCommunication

engineering(ICE)

MUT

Inform

ationan

Neighbor-solicitation and advertisement message formats


126/147

ndCommunication

engineering(ICE)

MUT

Inform

ationand

Group-membership messages


127/147

dCommunication

engineering(ICE)

MUT

Inform

ationand

Group-membership message formats


128/147

dCommunication

engineering(ICE)

MUT

Inform

ationand

Four situations of group-membership operation


129/147

dCommunication

engineering(ICE)

MUT

Inform

ationand Three strategies have been devised by the IETF to provide for aThree strategies have been devised by the IETF to provide for a smoothsmooth

TRANSITION FROM IPv4

TO IPv6


130/147

dCommunication

engineering(ICE)

MUT

Three strategies have been devised by the IETF to provide for aThree strategies have been devised by the IETF to provide for a smoothsmooth

transition from IPv4 to IPv6.transition from IPv4 to IPv6.


Dual StackDual Stack

TunnelingTunneling

Header TranslationHeader Translation

Inform

ationand

Three transition strategies


131/147

dCommunication

engineering(ICE)

MUT

Inform

ationand

Dual stack


132/147

dCommunication

engineering(

ICE)

MUT

Inform

ationand

Automatic tunneling

Dual Stack


133/147

dCommunication

engineering(

ICE)

MUT

Receiving host uses a compatible IPv6 address

Inform

ationand

Configured tunneling


134/147

Communication

engineering(

ICE)

MUT

Receiving host does not support a compatibi le IPv6 address

Inform

ationand

Header translation


135/147

Communication

engineering(

ICE)

MUT

Informationand

Summary

ICMPv4


136/147

Communication

engineering(

ICE)

MUT

IPv6

ICMP6

Next Class RIPv1 RIPv2

InformationandC


137/147

Communication

engineering(

ICE)

MUT

?

InformationandC

Exercise 18: what type of ICMP messages contain of the IP datagram?


138/147

Com

munication

engineering(

ICE)

MUT

Why is this included?

InformationandC

destination unreachable: type 1


139/147

Com

munication

engineering(

ICE)

MUT

packet too big: type 2

time exceeded: type 3

parameter problem: type 4

Redirection: type 137

The IP header and first 8 bytes of data are included because this data

contains all of the information needed for the source of the datagram to

identify the packet in question, including the destination address andthe source and destination port addresses.

InformationandC

Packet Analysis: ICMPv6


140/147

Com

munication

engineering(

ICE)

MUT Ref: Radcom RC-100 WL

InformationandC

TCP over ipv6


141/147

Com

municationengineering(

ICE)

MUT

InformationandC

UDP over IPv6


142/147

Com

municationengineering(ICE)

MUT

InformationandC

Check Sum Calculation (Ex1)

14

0 05 0 28 (4+1)100__ ________

(4+0)100

(4+0)100___ ________(0+1)0____ ________

(0+1)0_____ ________ (0+1)0______ ________

(0+0)0_______ ________


143/147

Com


MUT

12.6.7.910.12.4.5

41

00 0

17

12.6

10.12

1

0

284 5 0

0 04 17

4.5

7.9

01000101 0000000000000000 0001110000000000 0000000100000000 0000000000000100 0001000100000000 00000000

00001010 0000110000001110 0000010100001100 0000011000000111 00001001

(4+0)100_ ________(2+0)10 ________

(0+0) 0_______(0+1)00______

(4+0)100____(2+1)010___

(4+1)100__(0+1)000_(4+0)100

01110100 01001110 Sum

Checksum10001011 10110001

InformationandC

Check Sum Calculation(Ex2)


144/147

Com


MUT

InformationandC

21/10/2007, Intro

28/10/2007 Addressing


145/147

om


MUT

28/10/2007, Addressing

4/11/2007, Router Architecture

11/11/2007, IPv4

18/11/2007, ICMPv4 IPv6 ICMPv6 25/11/2007, RIP

2/12/2007, OSPF

9/12/2007, First seminar

InformationandCo

Presentation

Routed Protocol 25 2550


146/147

om


MUT

25 2550

Microsoft word file ( 2 2550)

power points 3 2550

IEEE, ACM, Elsevier, Wiley, www.google.com and others

4-12

InformationandCo


147/147

om


MUT

nete0514 network switching and routing

Documents