0% found this document useful (0 votes)
104 views19 pages

Introducing Internet Control Message Protocol (Icmp) For Ipv4 and Ipv6

ICMP is used to provide network connectivity information and error reporting. It is used by ping to test connectivity and traceroute to trace the route packets take to their destination. ICMP provides important network monitoring and troubleshooting functions for both IPv4 and IPv6.

Uploaded by

Like Her
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
104 views19 pages

Introducing Internet Control Message Protocol (Icmp) For Ipv4 and Ipv6

ICMP is used to provide network connectivity information and error reporting. It is used by ping to test connectivity and traceroute to trace the route packets take to their destination. ICMP provides important network monitoring and troubleshooting functions for both IPv4 and IPv6.

Uploaded by

Like Her
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Introducing Internet Control

Message Protocol (ICMP) for IPv4


and IPv6
Rick Graziani
Cabrillo College
[email protected]
IP

 IP is a best effort delivery system.


 No mechanism to ensure that the data is delivered
 So how do we know if a packet encountered a problem along the way?
 Internet Control Message Protocol (ICMP)
Internet Control
Message Protocol
(ICMP)

 ICMP is available for both IPv4 and IPv6.


 ICMPv4 is the messaging protocol for IPv4.
 ICMPv6 provides these same services for IPv6 but includes additional
functionality.
 ICMP messages common to ICMPv4 and ICMPv6 include:
 Host confirmation
 Destination or Service Unreachable
 Route redirection
 Time exceeded
 ICMPv6 includes additional functionality.
 ICMP is used for:
 Informational messages (ping, traceroute)
 Error messages (network unreachable)
 ICMP is a layer 3 protocol directly encapsulated in another layer 3 protocol IP.
 No transport header
 Knowledge of ICMP control messages is an essential part of network troubleshooting.
 The ICMP packets
are identified by
type and code
fields.

5
ICMPv6 Neighbor Discover Protocol
ICMPv6 Neighbor Discovery defines 5 different packet types:
• Router Solicitation Message
• Router Advertisement Message Router-Device
Messaging
Used with dynamic address allocation

• Neighbor Solicitation Message


• Neighbor Advertisement Message Device-Device
Used with address resolution (IPv4 ARP) Messaging

• Redirect Message
Similar to ICMPv4 redirect message See these processes with:
Router-to-Device messaging R1# debug ipv6 nd
NA and NS Messages: Address Resolution
ARP Request: Broadcast
IPv4: ARP over Ethernet Ethernet ARP Request/Reply
ARP
Cache Know
IPv4, what
My IPv4! 2 1
PC2 PC1 is the
Here is the ARP Reply MAC?
MAC?
ARP Request

2 1 Neighbor
Know
My IPv6!
Here is the Neighbor Neighbor Cache IPv6, what
Advertisement Solicitation is the
MAC?
MAC?

IPv6: ICMPv6 over IPv6 over Ethernet


NS: Multicast NS: Solicited Node Multicast
Ethernet IPv6 Header ICMPv6: Neighbor Solicitation/Advertisement
RA and RS Messages: Dynamic Address Allocation
Multicast: To all
Router(config)# ipv6 unicast-routing IPv6 routers, I need
IPv6 address
ICMPv6 Router Advertisement
information
DHCPv6
ICMPv6 Router Solicitation Server

Multicast: To all
IPv6 devices, I might not even be
let me tell you how needed. 
to do this …
• An ICMPv6 Router Advertisement (RA) suggests to all IPv6 devices on the
link how it will receive IPv6 Address Information.
• Sent periodically by an IPv6 router or…
• … when the router receives a Router Solicitation message from a host.
• Routers can be configured with IPv6 addresses without being an IPv6 router.
DAD (Duplicate Address Detection)
Global Unicast - 2001:db8:cafe:1:50a5:8a35:a5bb:66e1
Link-local - fe80::50a5:8a35:a5bb:66e1

Neighbor Solicitation

Not received = unique address Neighbor Advertisement?


Received = duplicate address

• SLAAC is stateless, no entity (DHCPv6 server) maintaining a state address-


to-device mappings.
• How can we guarantee the address is unique?
• Duplicate Address Detection (DAD)
• Once required for all unicast addresses (static or dynamic), RFC was
updated that DAD is only recommended.
• /64 Interface IDs!
Introducing Internet Control
Message Protocol (ICMP) for IPv4
and IPv6
Rick Graziani
Cabrillo College
[email protected]
Introducing Ping and Traceroute
Rick Graziani
Cabrillo College
[email protected]
Apples-MacBook-Pro:~ rigrazia$ ping www.google.com
 Use the ping command
PING www.google.com (74.125.239.115): 56 data bytes
to help you troubleshoot /
64 bytes from 74.125.239.115: icmp_seq=0 ttl=55 time=27.417 ms
64 bytes from 74.125.239.115: icmp_seq=1 ttl=55 time=42.574 ms
verify connectivity.
--- www.google.com ping statistics ---  Steps to verify:
3 packets transmitted, 3 packets received, 0.0% packet loss  Ping the remote host
round-trip min/avg/max/stddev = 25.898/31.963/42.574/7.529 ms
using the domain
Apples-MacBook-Pro:~ rigrazia$ ping 74.125.239.115
name
PING 74.125.239.115 (74.125.239.115): 56 data bytes
64 bytes from 74.125.239.115: icmp_seq=0 ttl=55 time=23.232 ms  Ping the remote host
64 bytes from 74.125.239.115: icmp_seq=1 ttl=55 time=22.104 ms using its IP address
--- 74.125.239.115 ping statistics ---  Ping your default
Apples-MacBook-Pro:~ rigrazia$ ping 192.168.1.1
gateway
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=7.207 ms  Ping your system
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=9.859 ms
--- 192.168.1.1 ping statistics ---
Apples-MacBook-Pro:~ rigrazia$ ping 192.168.1.119
PING 192.168.1.119 (192.168.1.119): 56 data bytes
64 bytes from 192.168.1.119: icmp_seq=0 ttl=64 time=0.073 ms
64 bytes from 192.168.1.119: icmp_seq=1 ttl=64 time=0.067 ms
--- 192.168.1.119 ping statistics ---
Apples-MacBook-Pro:~ rigrazia$ 14
Ping Command
PCA 2001:DB8:CAFE:1::/64
G0/0 R1

2001:DB8:CAFE:1::100 2001:DB8:CAFE:1::1
FE80::50A5:8A35:A5bb:66E1 FE80::1
PCA> ping 2001:db8:cafe:1::1

Pinging 2001:db8:cafe:1::1 from 2001:db8:cafe:1::100 with 32 bytes of data:

Reply from 2001:db8:cafe:1::1: time=1ms


Reply from 2001:db8:cafe:1::1: time=1ms
Reply from 2001:db8:cafe:1::1: time=1ms
Reply from 2001:db8:cafe:1::1: time=1ms

<rest of output omitted>


PCA>
Windows implementation of traceroute (tracert) uses pings
(ICMP Echo Requests and Echo Replies).
Traceroute
TTL 1

TTL 1 – 1 =0

ICMP Time
Exceeded

TTL 2 TTL 1

TTL 2 – 1 =1 TTL 1 – 1 =0

ICMP Time
Exceeded

TTL 3 TTL 2 TTL 1

TTL 3 – 1 =2 TTL 2 – 1 =1 TTL 2 – 1 =0

ICMP Time
Exceeded
C:\> tracert cern.ch
Tracing route to cern.ch [137.138.144.169]
over a maximum of 30 hops:

1 6 ms 8 ms 6 ms Home-Net [192.168.1.1]
2 * * * Request timed out.
3 14 ms 17 ms 24 ms 24-139-15-1.eastlink.ca [24.139.15.1]
4 11 ms 17 ms 17 ms 10.250.35.1
5 * 17 ms 11 ms on-sdbr-dr001.on.eastlink.ca [24.139.7.66]
6 19 ms 23 ms 14 ms 24-139-15-26.eastlink.ca [24.139.15.26]
7 37 ms 26 ms 33 ms te-4-3.car1.Montreal2.Level3.net [4.59.176.237]
8 137 ms 197 ms 138 ms ae-5-5.ebr2.NewYork1.Level3.net [4.69.141.6]
9 141 ms 138 ms 139 ms ae-45-45.ebr2.NewYork2.Level3.net [4.69.141.22]
10 133 ms 139 ms 136 ms ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253]
11 140 ms 139 ms 137 ms 4.69.201.93
12 137 ms 137 ms 139 ms ae-43-43.ebr2.Paris1.Level3.net [4.69.137.57]
13 254 ms 289 ms 267 ms ae-9-9.car1.Lyon1.Level3.net [4.69.134.49]
14 299 ms 210 ms 229 ms ae-5-5.car1.Geneva1.Level3.net [4.69.137.81]
15 135 ms 127 ms 138 ms h4allr1.safe-order.ch [213.242.73.22]
16 129 ms 137 ms 143 ms e513-e-rbrxl-2-ne0.cern.ch [192.65.184.38]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 134 ms 141 ms 145 ms webr8.cern.ch [137.138.144.169]
21 132 ms 128 ms 129 ms webr8.cern.ch [137.138.144.169]
Trace complete.
C:\Users\Bob>
Error Message: Time Exceeded
Apples-MacBook-Pro-9:~ rigrazia$ traceroute6 www.netflix.com
traceroute6 to www.us-west-2.prodaa.netflix.com (2620:108:700f::3428:3c77)
from 2601:642:c300:cfa9:3d11:f46f:2db9:7e51, 64 hops max, 12 byte
packets
1 2601:642:c300:cfa9:5e8f:e0ff:fe4d:f437 3.075 ms 2.618 ms 2.020 ms
2 2001:558:4000:7::1 11.539 ms 11.435 ms 11.283 ms
3 te-0-7-0-7-sur03.monterey.ca.sfba.comcast.net 11.766 ms 11.961 ms
11.637 ms
4 be-222-ar01.santaclara.ca.sfba.comcast.net 15.150 ms 13.812 ms
13.577 ms
5 be-3651-cr02.sunnyvale.ca.ibone.comcast.net 15.185 ms 17.160 ms
15.309 ms
6 be-11083-pe02.529bryant.ca.ibone.comcast.net 23.074 ms 14.251 ms
14.328 ms
7 . . .
19 2620:108:700f::3428:3c77 32.758 ms 34.255 ms 31.358 ms
Apples-MacBook-Pro-9:~ rigrazia$

• Windows uses tracert (IPv4 and IPv6) or tracert -6 (IPv6 only)


Introducing Ping and Traceroute
Rick Graziani
Cabrillo College
[email protected]

You might also like