1 / 19

S kills : : Use ping and traceroute and query the whois database

Ping and traceroute demonstration. S kills : : Use ping and traceroute and query the whois database Concepts : network transit time, router hops, command-line user interface, whois database, prefixes for small quantities.

steffi
Download Presentation

S kills : : Use ping and traceroute and query the whois database

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ping and traceroute demonstration Skills: : Use ping and tracerouteand query the whoisdatabase Concepts: network transit time, router hops, command-line user interface, whois database, prefixes for small quantities This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 License.

  2. Where does this topic fit? • Internet concepts • Applications • Technology (communication) • Implications • Internet skills • Application development • Content creation • User skills

  3. Ping and traceroute

  4. Ping Google C:\Users\Larry>ping www.google.com Pinging www.l.google.com [74.125.224.84] with 32 data bytes: Reply from 74.125.224.84: bytes=32 time=18ms TTL=53 Reply from 74.125.224.84: bytes=32 time=17ms TTL=53 Reply from 74.125.224.84: bytes=32 time=19ms TTL=53 Reply from 74.125.224.84: bytes=32 time=17ms TTL=53 Ping statistics for 74.125.224.84: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 19ms, Average = 17ms C:\Users\Larry>

  5. Ping Catholic University, Santiago Chile C:\Users\Larry>ping www.puc.cl Pinging www.puc.cl [146.155.99.60] with 32 bytes of data: Reply from 146.155.99.60: bytes=32 time=182ms TTL=110 Reply from 146.155.99.60: bytes=32 time=180ms TTL=110 Reply from 146.155.99.60: bytes=32 time=177ms TTL=110 Reply from 146.155.99.60: bytes=32 time=185ms TTL=110 Ping statistics for 146.155.99.60: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 180ms, Maximum = 185ms, Average = 181ms C:\Users\Larry>

  6. C:\Users\Larry>tracert www.google.com Tracing route to www.l.google.com [74.125.224.82] 1 192.168.1.1 2 cpe-76-170-200-1.socal.res.rr.com [76.170.200.1] 3 76.166.24.9 4 cpe-66-75-159-160.socal.rr.com [66.75.159.160] 5 be18-lsanca4-rtr1.socal.rr.com [66.75.159.128] 6 ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212] 7 ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133] 8 72.14.198.73 9 64.233.174.238 10 64.233.174.192 11 64.233.174.205 12 64.233.174.19 13 74.125.224.82 Trace complete. C:\Users\Larry> Traceroute home-Google

  7. C:\Users\Larry>tracert www.google.com Tracing route to www.l.google.com [74.125.224.49] over a maximum of 30 hops: 1 CDH-ERC-C112-CAT6509-CORE1.csudh.edu [10.1.0.2] 2 10.21.0.8 3 CDH-ERC-C112-7204-PRIMARY.csudh.edu [155.135.55.254] 4 dc-lax-dc1--csudominguezhills-egm.cenic.net [137.164.40.41] 5 dc-lax-core1--lax-agg1-ge.cenic.net [137.164.46.105] 6 dc-lax-peer1--lax-core1-ge.cenic.net [137.164.46.116] 7 64.57.20.226 8 74.125.49.165 9 216.239.46.40 10 64.233.174.190 11 64.233.174.205 12 64.233.174.15 13 74.125.224.49 Trace complete. Traceroute office-Google

  8. C:\Users\Larry>tracert www.puc.cl Tracing route to www.puc.cl [146.155.99.60] 1 192.168.1.1 2 cpe-76-170-200-1.socal.res.rr.com [76.170.200.1] 3 76.166.24.9 4 cpe-66-75-159-160.socal.rr.com [66.75.159.160] 5 be18-lsanca4-rtr1.socal.rr.com [66.75.159.128] 6 ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212] 7 ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133] 8 Vlan518.icore1.EQL-LosAngeles.as6453.net [206.82.129.13] 9 f-4-28.tcore2.LVW-LosAngeles.as6453.net [216.6.84.53] 10 if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1] 11 if-1-0-0-1341.core2.DTX-Dallas.as6453.net [66.110.59.106] 12 if-3-0-1150.core4.MLN-Miami.as6453.net [66.198.2.62] 13 ix-2-0-0.core4.MLN-Miami.as6453.net [66.198.82.2] 14 190.208.9.10 [190.208.9.10] 15 200.27.5.109 16 190.208.3.10 [190.208.3.10] 17 192.168.120.203 18 146.155.99.1 19 www.puc.cl [146.155.99.60] Trace complete. C:\Users\Larry> Traceroute home-Catholic U.

  9. C:\Users\Larry>tracert www.puc.cl Tracing route to www.puc.cl [146.155.99.60] 1 CDH-ERC-C112-CAT6509-CORE1.csudh.edu [10.1.0.2] 2 10.21.0.8 3 CDH-ERC-C112-7204-PRIMARY.csudh.edu [155.135.55.254] 4 dc-lax-dc1--csudominguezhills-egm.cenic.net [137.164.40.41] 5 dc-lax-core2--lax-agg1-ge.cenic.net [137.164.46.107] 6 dc-lax-isp2--lax-core2-10ge.cenic.net [137.164.47.138] 7 xe-9-3-0.edge5.LosAngeles1.Level3.net [4.59.48.177] 8 ae-4-90.edge1.LosAngeles6.Level3.net [4.69.144.208] 9 tata-level3-te.LosAngeles1.level3.net [4.68.63.66] 10 if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1] 11 if-5-0-0-1340.core2.DTX-Dallas.as6453.net [66.110.59.90] 12 if-6-0-0-1275.core4.MLN-Miami.as6453.net [66.198.2.66] 13 ix-2-0-0.core4.MLN-Miami.as6453.net [66.198.82.2] 14 190.208.9.10 [190.208.9.10] 15 200.27.5.109 16 190.208.3.10 [190.208.3.10] 17 146.155.99.1 18 www.puc.cl [146.155.99.60] Trace complete. C:\Users\Larry> Traceroute office-Catholic U.

  10. Try ping and tracert yourself Start > Run

  11. A command-line window

  12. The result

  13. A windows Ping client

  14. Whois OrgName:       California State UniversityOrgId:           CSU-13Address:         1000 East Victoria StCity:            CarsonStateProv:      CAPostalCode:    90502Country:         USRegDate:         1991-11-08Updated:         2003-05-27 http://www.dnstools.com

  15. Traceroute footnotes It’s tracert & Request timed out

  16. Prefixes for small quantities

  17. Summary

  18. Self-study questions Which organization owns the host with the IP address 74.125.0.0 ? Ping and trace the route from two different places, for example your home and your office, to www.microsoft.com. Are the ping times the same? Are the routes the same? Explain the differences? I pinged Google.com from my home and from my office. If you look at the IP addresses of the final hops, you will see that they are different. Can you explain that? Which do you like better, the command-line ping program that comes with Windows or the window-based program that I wrote? Why? Give at least one advantage for each. If you trace the route between two hosts at different times, will it always be the same? Explain your answer. If you measure ping time between two hosts at different times, will it always be the same? Explain your answer.

  19. Resources One of many Whois services on the Web: http://dnstools.com/ To find others, googlewhois. To run traceroute or ping from remote locations around the world, go to: http://www.traceroute.org/ For more on command line versus graphical user interfaces see: http://som.csudh.edu/fac/lpress//471/hout/misc/guivcli.htm

More Related