Presentation is loading. Please wait.

Presentation is loading. Please wait.

Information and Communication engineering (ICE) MUT ITEC4610 Network Switching and Routing ดร. ประวิทย์ ชุมชู หัวหน้าสาขาวิชาวิศวกรรมสารสนเทศและการสื่อสาร.

Similar presentations


Presentation on theme: "Information and Communication engineering (ICE) MUT ITEC4610 Network Switching and Routing ดร. ประวิทย์ ชุมชู หัวหน้าสาขาวิชาวิศวกรรมสารสนเทศและการสื่อสาร."— Presentation transcript:

1 Information and Communication engineering (ICE) MUT ITEC4610 Network Switching and Routing ดร. ประวิทย์ ชุมชู หัวหน้าสาขาวิชาวิศวกรรมสารสนเทศและการสื่อสาร (ICE) MUT Email: prawit@mut.ac.thprawit@mut.ac.th ห้องทำงาน : F402 เบอร์โทรศัพท์ที่ทำงาน : (02)9883655 ต่อ 220 เบอร์โทรศัพท์เคลื่อนที่ : 065343850

2 Information and Communication engineering (ICE) MUT Class IV ICMPv4, IPv6 และ ICMPv6 ดร. ประวิทย์ ชุมชู หัวหน้าสาขาวิชาวิศวกรรมสารสนเทศและการสื่อสาร (ICE) MUT Email: prawit@mut.ac.thprawit@mut.ac.th ห้องทำงาน : F402 เบอร์โทรศัพท์ที่ทำงาน : (02)9883655 ต่อ 220 เบอร์โทรศัพท์เคลื่อนที่ : 065343850

3 Information and Communication engineering (ICE) MUT หัวข้อที่บรรยาย  Introduction ICMPv4 IPv6 ICMPv6

4 Information and Communication engineering (ICE) 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 Information and Communication engineering (ICE) MUT หัวข้อที่บรรยาย Introduction  ICMPv4 IPv6 ICMPv6

6 Information and Communication engineering (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 messages Be 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 Protocol version 4

7 Information and Communication engineering (ICE) MUT Position of ICMP in the network

8 Information and Communication engineering (ICE) MUT ICMP encapsulation ICMP is network layer protocol but its messages are first encapsulated inside IP datagrams Protocol Field in IP header =1

9 Information and Communication engineering (ICE) MUT ICMP messages are divided into error-reporting messages and query messages. The error-reporting messages report problems that a router or a host (destination) may encounter. The query messages get specific information from a router or another host. TYPES OF MESSAGES

10 Information and Communication engineering (ICE) MUT ICMP messages

11 Information and Communication engineering (ICE) MUT An ICMP message has an 8-byte header and a variable-size data section. Although the general format of the header is different for each message type, the first 4 bytes are common to all. MESSAGE FORMAT Type : defined in the previous slide Code: the reason for particular message types calculated over the entire message (header and data). Checksum: 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 packet Query messages  extra information

12 Information and Communication engineering (ICE) MUT IP, as an unreliable protocol, is not concerned with error checking and error control. ICMP was designed, in part, to compensate for this shortcoming. ICMP does not correct errors, it simply reports them. The topics discussed in this section include: Destination Unreachable Source Quench Time Exceeded Parameter Problem Redirection ERROR REPORTING

13 Information and Communication engineering (ICE) MUT ICMP always reports error messages to the original source. Note:

14 Information and Communication engineering (ICE) MUT Error-reporting messages

15 Information and Communication engineering (ICE) 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 a fragmented 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:

16 Information and Communication engineering (ICE) MUT Contents of data field for the error messages 8 bytes : Received datagram IP header: Sent datagram IP header :

17 Information and Communication engineering (ICE) MUT Destination-unreachable format

18 Information and Communication engineering (ICE) 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

19 Information and Communication engineering (ICE) MUT 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. Note:

20 Information and Communication engineering (ICE) MUT A router cannot detect all problems that prevent the delivery of a packet. Note:

21 Information and Communication engineering (ICE) MUT There is no flow-control mechanism in the IP protocol. Note:

22 Information and Communication engineering (ICE) MUT Source-quench format Cause of Congestion

23 Information and Communication engineering (ICE) MUT A source-quench message informs the source that a datagram has been 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. Note:

24 Information and Communication engineering (ICE) MUT One source-quench message is sent for each datagram that is discarded due to congestion. Note:

25 Information and Communication engineering (ICE) MUT 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. Note:

26 Information and Communication engineering (ICE) MUT When the final destination does not receive all of the fragments in a set time, it discards the received fragments and sends a time-exceeded message to the original source. Note:

27 Information and Communication engineering (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:

28 Information and Communication engineering (ICE) MUT Time-exceeded message format - TTL - Timeout

29 Information and Communication engineering (ICE) MUT A parameter-problem message can be created by a router or the destination host. Note:

30 Information and Communication engineering (ICE) MUT Parameter-problem message format 0: Wrong header 1: Need options

31 Information and Communication engineering (ICE) MUT Redirection concept

32 Information and Communication engineering (ICE) MUT A host usually starts with a small routing table that is gradually augmented and updated. One of the tools to accomplish this is the redirection message. Note:

33 Information and Communication engineering (ICE) MUT Redirection message format

34 Information and Communication engineering (ICE) MUT A redirection message is sent from a router to a host on the same local network. Note:

35 Information and Communication engineering (ICE) MUT ICMP can also diagnose some network problems through the query messages, a group of four different pairs of messages. In this type of ICMP message, a node sends a message that is answered in a specific format by the destination node. The topics discussed in this section include: Echo Request and Reply Timestamp Request and Reply Address-Mask Request and Reply Router Solicitation and Advertisement QUERY

36 Information and Communication engineering (ICE) MUT Query messages

37 Information and Communication engineering (ICE) MUT 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. Note:

38 Information and Communication engineering (ICE) MUT Echo-request and echo-reply messages can be used by network managers to check the operation of the IP protocol. Note:

39 Information and Communication engineering (ICE) MUT Echo-request and echo-reply messages can test the reachability of a host. This is usually done by invoking the ping command. Note:

40 Information and Communication engineering (ICE) MUT Echo-request and echo- reply messages

41 Information and Communication engineering (ICE) MUT Echo-request and echo- reply messages

42 Information and Communication engineering (ICE) 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 not synchronized. Note:

43 Information and Communication engineering (ICE) MUT The timestamp-request and timestamp- reply messages can be used to synchronize two clocks in two machines if the exact one-way time duration is known. Note:

44 Information and Communication engineering (ICE) MUT Mask-request and mask- reply message format

45 Information and Communication engineering (ICE) MUT Router-solicitation message format

46 Information and Communication engineering (ICE) MUT Router-advertisement message format

47 Information and Communication engineering (ICE) MUT In ICMP the checksum is calculated over the entire message (header and data). In ICMP the checksum is calculated over the entire message (header and data). The topics discussed in this section include: Checksum Calculation Checksum Testing CHECKSUM

48 Information and Communication engineering (ICE) MUT The following Figure shows an example of checksum calculation for a simple echo-request message. We randomly chose 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

49 Information and Communication engineering (ICE) MUT Example of checksum calculation

50 Information and Communication engineering (ICE) MUT We introduce two tools that use ICMP for debugging: ping and traceroute. The topics discussed in this section include: PingTraceroute DEBUGGING TOOLS

51 Information and Communication engineering (ICE) MUT We use the ping program to test the server fhda.edu. The result 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 ms 64 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 64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=3 ttl=62 time=1.97 ms 64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=4 ttl=62 time=1.93 ms Example 2

52 Information and Communication engineering (ICE) MUT 64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=5 ttl=62 time=2.00 ms 64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=6 ttl=62 time=1.94 ms 64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=7 ttl=62 time=1.94 ms 64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=8 ttl=62 time=1.97 ms 64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=9 ttl=62 time=1.89 ms 64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=10 ttl=62 time=1.98 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)

53 Information and Communication engineering (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 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=2 ttl=48 time=84.9 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=3 ttl=48 time=84.3 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=4 ttl=48 time=84.5 ms See Next Slide Example 3

54 Information and Communication engineering (ICE) MUT 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=5 ttl=48 time=84.7 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=6 ttl=48 time=84.6 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=7 ttl=48 time=84.7 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=8 ttl=48 time=84.4 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=9 ttl=48 time=84.2 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=10 ttl=48 time=84.9 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=11 ttl=48 time=84.6 ms 64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=12 ttl=48 time=84.5 ms --- 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

55 Information and Communication engineering (ICE) MUT Example 3

56 Information and Communication engineering (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.edu traceroute 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 ms 2 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

57 Information and Communication engineering (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)

58 Information and Communication engineering (ICE) MUT In this example, we trace a longer route, the route to xerox.com $ traceroute xerox.com traceroute to xerox.com (13.1.64.93), 30 hops max, 38 byte packets 1 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

59 Information and Communication engineering (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.edu traceroute 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

60 Information and Communication engineering (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 traceroute does not receive a response within 5 seconds, it prints an asterisk to signify a problem, and then tries the next hop.. $ traceroute mhhe.com traceroute to mhhe.com (198.45.24.104), 30 hops max, 38 byte packets 1 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

61 Information and Communication engineering (ICE) MUT To give an idea of how ICMP can handle the sending and receiving of ICMP messages, we present our version of an ICMP package made of two modules: an input module and an output module. The topics discussed in this section include: Input Module Output Module ICMP PACKAGE

62 Information and Communication engineering (ICE) MUT ICMP package

63 Information and Communication engineering (ICE) MUT คำถาม ?

64 Information and Communication engineering (ICE) MUT แบบฝึกหัดท้ายบทลองทำดู ถ้าแพ็คเก็ตหายที่จุดต่าง ๆ ดังรูป ICMP ตอบสนองอย่างไรบ้าง A, B, C, D, E, F,G

65 Information and Communication engineering (ICE) MUT แบบฝึกหัดท้ายบทลองทำดู Exercise 13: How can we determine if an IP packet is carrying an ICMP packet?

66 Information and Communication engineering (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 ?

67 Information and Communication engineering (ICE) MUT แบบฝึกหัดท้ายบทลองทำดู ถ้าคุณต้องการทราบว่าคอมพิวเตอร์ IPv4 เครื่องหนึ่งมีการเปิดให้บริการโปรแกรมประยุกต์ อะไรบ้างนักศึกษาสามารถทำได้อย่าง ถ้า นักศึกษามีคอมพิวเตอร์ที่มีการเชื่อมต่อ เครือข่าย IPv4 กับคอมพิวเตอร์เครื่องนั้น

68 Information and Communication engineering (ICE) MUT หัวข้อที่บรรยาย Introduction ICMPv4  IPv6 ICMPv6

69 Information and Communication engineering (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 types Know the differences between ICMPv4 and ICMPv6 Know the strategies for transitioning from IPv4 to IPv6 Objectives Next Generation: IPv6 and ICMPv6

70 Information and Communication engineering (ICE) MUT IPv6 has these advantages over IPv4: 1. larger address space  128 bits 32 bits 2. better header format  keep header overhead to a minimum 3. new options  additional functionalities 4. allowance for extension  for new technologies or applications 5. support for resource allocation  using flow label for QoS 6. support for more security  confidentially and integrity of the packets The topics discussed in this section include: IPv6 Addresses Address Space Assignment Packet Format Comparison between IPv4 and IPv6 IPv6

71 Information and Communication engineering (ICE) MUT IPv6 address

72 Information and Communication engineering (ICE) MUT Abbreviated address

73 Information and Communication engineering (ICE) MUT Abbreviated address with consecutive zeros ย่อได้ครั้งเดียวเท่านั้นต่อ 1 หมายเลข IP

74 Information and Communication engineering (ICE) MUT CIDR address

75 Information and Communication engineering (ICE) MUT Address structure See next slide for types of prefix

76 Information and Communication engineering (ICE) MUT Type prefixes for IPv6 addresses

77 Information and Communication engineering (ICE) MUT Provider-based address Type identifier  010:a provider-based address Registry  11000:North America 01000:European 10100:Asian and Pacific countries

78 Information and Communication engineering (ICE) MUT Address hierarchy Provider prefix  an ISP, variable-length Subscriber prefix  an organization subscriber, 24 bits Subnet prefix  a network under a territory of the subscriber, 32 bits Node Identifier  the identity of node connected to the subnet 48 bits

79 Information and Communication engineering (ICE) MUT Unspecified address For: - a host does no know its own address - A host sends an inquiry to find its address

80 Information and Communication engineering (ICE) MUT Loopback Address For: -used by a host to test itself without going on the networks

81 Information and Communication engineering (ICE) MUT Compatible address -Used when a computer using IPv6 wants to send a packet to another computer using IPv6 - the packet passes through IPv4 networks IPv6  IPv4  IPv6 0x02  2 0x0D  13 0x11  17 0x0E  14

82 Information and Communication engineering (ICE) MUT Mapped address For: -Used when a computer that has migrated to IPv6 want to sent a packet to a computer still using IPv4

83 Information and Communication engineering (ICE) MUT Link local address For: - Used in an isolated network - Does not have a global effect

84 Information and Communication engineering (ICE) MUT Site local address For: -Used for a site with several networks - Used in isolated networks - Does not have a global effect

85 Information and Communication engineering (ICE) MUT Multicast address For: - For a group of hosts

86 Information and Communication engineering (ICE) MUT IPv6 datagram

87 Information and Communication engineering (ICE) MUT Format of an IPv6 datagram 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 limit: TTL Source Address: the original source IP address Destination Address: the final destination IP address Version: version 6 Priority: packet priorities

88 Information and Communication engineering (ICE) MUT Next header codes

89 Information and Communication engineering (ICE) MUT Priorities for congestion- controlled traffic

90 Information and Communication engineering (ICE) MUT Priorities for noncongestion- controlled traffic

91 Information and Communication engineering (ICE) MUT Comparison between IPv4 and IPv6 packet header

92 Information and Communication engineering (ICE) MUT Extension header format

93 Information and Communication engineering (ICE) MUT Extension header types

94 Information and Communication engineering (ICE) MUT Hop-by-hop option header format Used when the source needs to pass information to all router visited by the datagram

95 Information and Communication engineering (ICE) MUT The format of options in a hop- by-hop option header

96 Information and Communication engineering (ICE) MUT Pad1

97 Information and Communication engineering (ICE) MUT PadN

98 Information and Communication engineering (ICE) MUT Jumbo payload For: - normally the IP datagram can be a maximum of 65535 bytes - Jumbo payload =2^32-1 (4,294,967,295 bytes)

99 Information and Communication engineering (ICE) MUT Source routing

100 Information and Communication engineering (ICE) MUT Source routing example

101 Information and Communication engineering (ICE) MUT Fragmentation - Only the source could do - PATH MTU Discovery technique -If no path MTU discovery, a size of 576 bytes of smaller

102 Information and Communication engineering (ICE) MUT Authentication

103 Information and Communication engineering (ICE) MUT Calculation of authentication data The authentication header validates the message sender and ensures the integrity of data

104 Information and Communication engineering (ICE) MUT Encrypted security payload Providing confidentiality ( รักษาความลับ ) and guards against eavesdropping ( ดังฟัง )

105 Information and Communication engineering (ICE) MUT Transport mode encryption

106 Information and Communication engineering (ICE) MUT Tunnel-mode encryption

107 Information and Communication engineering (ICE) MUT Comparison between IPv4 options and IPv6 extension headers

108 Information and Communication engineering (ICE) MUT คำถาม ?

109 Information and Communication 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

110 Information and Communication 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

111 Information and Communication 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?

112 Information and Communication engineering (ICE) MUT แบบฝึกหัด Exercise 28: what is the ip-compatible address for 119.254.254.254?

113 Information and Communication engineering (ICE) MUT แบบฝึกหัด Exercise 29: what is the ip-mapped address for 119.254.254.254?

114 Information and Communication engineering (ICE) MUT หัวข้อที่บรรยาย Introduction ICMPv4 IPv6  ICMPv6

115 Information and Communication engineering (ICE) MUT ICMPv6, while similar in strategy to ICMPv4, has changes that makes it more suitable for IPv6. ICMPv6 has absorbed some protocols that were independent in version 4. The topics discussed in this section include: Error Reporting Query ICMPv6

116 Information and Communication engineering (ICE) MUT Comparison of network layers in version 4 and version 6

117 Information and Communication engineering (ICE) MUT Categories of ICMPv6 messages

118 Information and Communication engineering (ICE) MUT General format of ICMP messages

119 Information and Communication engineering (ICE) MUT Error-reporting messages Destination Unreachable: The same concept as in ICMPv4 Packet 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

120 Information and Communication engineering (ICE) MUT Comparison of error-reporting messages in ICMPv4 and ICMPv6

121 Information and Communication engineering (ICE) MUT Destination-unreachable message format 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.

122 Information and Communication engineering (ICE) MUT Packet-too-big message format

123 Information and Communication engineering (ICE) MUT Time-exceeded message format 0: a hop limit field =0 1: not arrived within the time limit for fragments of datagram

124 Information and Communication engineering (ICE) MUT Parameter-problem message format 0: Error in header fields 1:an unrecognized extension header 2: an unrecognized option

125 Information and Communication engineering (ICE) MUT Redirection message format

126 Information and Communication engineering (ICE) MUT Query messages

127 Information and Communication engineering (ICE) MUT Comparison of query messages in ICMPv4 and ICMPv6

128 Information and Communication engineering (ICE) MUT Echo request and reply messages

129 Information and Communication engineering (ICE) MUT Router-solicitation and advertisement message formats

130 Information and Communication engineering (ICE) MUT Neighbor-solicitation and advertisement message formats

131 Information and Communication engineering (ICE) MUT Group-membership messages

132 Information and Communication engineering (ICE) MUT Group-membership message formats

133 Information and Communication engineering (ICE) MUT Four situations of group- membership operation

134 Information and Communication engineering (ICE) MUT Three strategies have been devised by the IETF to provide for a smooth transition from IPv4 to IPv6. The topics discussed in this section include: Dual Stack Tunneling Header Translation TRANSITION FROM IPv4 TO IPv6

135 Information and Communication engineering (ICE) MUT Three transition strategies

136 Information and Communication engineering (ICE) MUT Dual stack

137 Information and Communication engineering (ICE) MUT Automatic tunneling

138 Information and Communication engineering (ICE) MUT Configured tunneling

139 Information and Communication engineering (ICE) MUT Header translation

140 Information and Communication engineering (ICE) MUT Header translation

141 Information and Communication engineering (ICE) MUT Summary ICMPv4 IPv6 ICMP6 Next Class  RIPv1 และ RIPv2

142 Information and Communication engineering (ICE) MUT คำถาม ?

143 Information and Communication engineering (ICE) MUT แบบฝึกหัดลองทำดู Exercise 18: what type of ICMP messages contain of the IP datagram? Why is this included?


Download ppt "Information and Communication engineering (ICE) MUT ITEC4610 Network Switching and Routing ดร. ประวิทย์ ชุมชู หัวหน้าสาขาวิชาวิศวกรรมสารสนเทศและการสื่อสาร."

Similar presentations


Ads by Google