You are on page 1of 5

Running head: FUNCTION OF ROUTING PROTOCOLS IN AN IP NETWORK

Function of Routing Protocols in an IP Network Catherine Cotton Kaplan University IT-283-02 January 24, 2012 Mr. Ralph Argiento

FUNCTION OF ROUTING PROTOCOLS IN AN IP NETWORK Unit 3

1. Open a command prompt. Open Wireshark and set it to capture. In the command prompt type ping google.com. Take a screen capture of the Wireshark window. Analyze the output of the PING. Explain the process the ICMP messages are using.

While using the command prompt to ping google.com there was a DNS to query google.com with an address of 74.125.255.148 returned. Four ICMP echo messages (ICMP type 8) were sent and four ICMP Echo reply (ICMP type 0) messages were received (Davies, 2008). 2. Open a command prompt. Open Wireshark and set it to capture. In the command prompt type tracert google.com. Take a screen capture of the Wireshark window. Analyze the output. Explain the process the ICMP messages are using.

FUNCTION OF ROUTING PROTOCOLS IN AN IP NETWORK

While using the command prompt to tracert google.com there was a DNS to query google.com with an address of 74.125.255.148 returned. My system sends an ICMP Echo message to the IP router. The IP router sends back an ICMP Time exceeded Time to live exceeded in transmit). Tracert sends two more ICMP echo messages. ICMP Echo message is send to 74.125.255.148 with the IP headers TTL set to 2. Tracert sends two more ICMP echo messages. This continues until ttl-5 is reached which I received Destination unreachable (Network unreachable). In other words, there were five hops before receiving Destination unreachable (Network unreachable). 3. Give the pathping output: D:\>pathping -n testpc1. Explain the process as well as what the output tells you. Pathping n transmits a total of 100 ICMP Echo messages from the host (172.16.87.35) to the destination host (7.54.1.198) across four routers (172.16.87.218, 192.168.52.1, 192.168.80.1, and 7.54.247.14). The n instructs Pathping to not perform a DNS reverse query

FUNCTION OF ROUTING PROTOCOLS IN AN IP NETWORK

on every router IP address (Davies, 2008). The Pingpath shows there were no packets lost on the link between the host (172.16.87.35) to the first router (172.16.87.218). There were zero packets lost and the average round trip was 41ms on the path between the host and the first router. There were 13 packets lost on the link between the first router (172.16.87.218) to the second router (192.168.52.1). There were 16 packets lost and the average round trip was 22ms on the path between the host and second router. There were zero packets lost on the link between the second router (192.168.52.1) to the third router (192.168.80.1). There were 13 packets lost and the average round trip was 24ms on the path between the host and third router. There were zero packets lost on the link between the third router (192.168.80.1) to the fourth router (7.54.247.14). There were 14 packets lost and the average round trip was 21ms on the path between the host and fourth router. There were zero packets lost on the link between the fourth router (7.54.247.14) to the destination host (7.54.1.198). There were 13 packets lost and the average round trip was 24ms on the path between the host and destination host (Davies, 2008). 4. Write a brief synopsis on IGMP. What is it? What is its use? How is it used? Be sure to use your own words. The Internet Group Management Protocol (IGMP) is defined by RFC 1112 as the standard for IP multicasting on the internet. In other words, IGMP can broadcast from one-tomany services/devices. IGMP is used by IP hosts to report their host group memberships to any directly neighboring multicast routers (Deering, 1989). IGMP can be used for online streaming video and gaming, on-line classes, IP video teleconferencing, or any other devices that need to broadcast information to multiple systems.

FUNCTION OF ROUTING PROTOCOLS IN AN IP NETWORK References Davies, J. (2008). Windows Server 2008 TCP/IP Protocols and Services. Redmond, WA: Microsoft Press. Deering, S., (1989, August). Host Extensions for IP Multicasting. Retrieved from http://www.ietf.org/rfc/rfc1112.txt

You might also like