Fit-Tech-Hub

Post #4 - Traveling Through a Network

Google.com

C:\Users\tyler>ping google.com

Pinging google.com [2607:f8b0:400f:804::200e] with 32 bytes of data:

Reply from 2607:f8b0:400f:804::200e: time=20ms

Reply from 2607:f8b0:400f:804::200e: time=20ms

Reply from 2607:f8b0:400f:804::200e: time=27ms

Reply from 2607:f8b0:400f:804::200e: time=20ms

Ping statistics for 2607:f8b0:400f:804::200e:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 20ms, Maximum = 27ms, Average = 21ms

Kmart.Com.au

C:\Users\tyler>ping kmart.com.au

Pinging kmart.com.au [103.28.250.204] with 32 bytes of data:

Reply from 103.28.250.204: bytes=32 time=229ms TTL=43

Reply from 103.28.250.204: bytes=32 time=309ms TTL=43

Reply from 103.28.250.204: bytes=32 time=325ms TTL=43

Reply from 103.28.250.204: bytes=32 time=327ms TTL=43

Ping statistics for 103.28.250.204:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 229ms, Maximum = 327ms, Average = 297ms

Amazon.co.jp

C:\Users\tyler>ping amazon.co.jp

Pinging amazon.co.jp [52.119.164.121] with 32 bytes of data:

Reply from 52.119.164.121: bytes=32 time=50ms TTL=225

Reply from 52.119.164.121: bytes=32 time=56ms TTL=225

Reply from 52.119.164.121: bytes=32 time=50ms TTL=225

Reply from 52.119.164.121: bytes=32 time=54ms TTL=225

Ping statistics for 52.119.164.121:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 50ms, Maximum = 56ms, Average = 52ms



Traceroute Activity



Google.Com

C:\Users\tyler>tracert google.com

Tracing route to google.com [2607:f8b0:400f:807::200e]

over a maximum of 30 hops:

1 4 ms 1 ms 1 ms 2601:8c0:d02:2f00:fa8b:37ff:febd:1422

2 14 ms 9 ms 50 ms 2001:558:1024:74::3

3 51 ms 49 ms 48 ms po-313-442-rur202.albuquerque.nm.albuq.comcast.net [2001:558:42:9c::1]

4 51 ms 49 ms 49 ms po-2-rur201.albuquerque.nm.albuq.comcast.net [2001:558:40:5d::1]

5 54 ms 54 ms 56 ms po-200-xar01.albuquerque.nm.albuq.comcast.net [2001:558:40:21::1]

6 * 12 ms * be-306-arsc1.albuquerque.nm.albuq.comcast.net [2001:558:40:26::1]

7 20 ms 65 ms 57 ms be-36821-cs02.1601milehigh.co.ibone.comcast.net [2001:558:3:305::1]

8 87 ms 56 ms 62 ms be-1214-cr14.1601milehigh.co.ibone.comcast.net [2001:558:3:1dd::2]

9 60 ms 58 ms 59 ms be-303-cr14.champa.co.ibone.comcast.net [2001:558:3:1c2::1]

10 59 ms 61 ms 58 ms be-1214-cs02.champa.co.ibone.comcast.net [2001:558:3:17d::1]

11 58 ms 59 ms 57 ms be-3211-pe11.910fifteenth.co.ibone.comcast.net [2001:558:3:5d::2]

12 * * * Request timed out.

13 21 ms 58 ms 57 ms 2607:f8b0:82bc::1

14 22 ms 59 ms 59 ms 2001:4860:0:1::5804

15 60 ms 57 ms 75 ms 2001:4860:0:122e::a

16 65 ms 57 ms 76 ms 2001:4860:0:134d::1

17 58 ms 56 ms 57 ms 2001:4860:0:1::5835

18 57 ms 28 ms 17 ms den16s09-in-x0e.1e100.net [2607:f8b0:400f:807::200e]

Trace complete.



Kmart.Com.Au

C:\Users\tyler>tracert kmart.com.au

Tracing route to kmart.com.au [103.28.251.204]

over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.0.1

2 21 ms 9 ms 12 ms 100.92.206.131

3 14 ms 10 ms 11 ms 96.216.145.101

4 10 ms 10 ms 11 ms 68.86.182.121

5 12 ms 13 ms 10 ms po-200-xar01.albuquerque.nm.albuq.comcast.net [68.85.65.89]

6 14 ms 12 ms 11 ms 96.108.43.101

7 23 ms * 25 ms be-36811-cs01.1601milehigh.co.ibone.comcast.net [96.110.44.17]

8 23 ms 20 ms 18 ms be-1114-cr14.1601milehigh.co.ibone.comcast.net [96.110.39.114]

9 23 ms 19 ms 19 ms be-302-cr14.champa.co.ibone.comcast.net [96.110.39.5]

10 23 ms 26 ms 19 ms be-1314-cs03.champa.co.ibone.comcast.net [96.110.37.249]

11 23 ms 19 ms 19 ms be-1312-cr12.champa.co.ibone.comcast.net [96.110.37.218]

12 41 ms 43 ms 41 ms be-301-cr11.sunnyvale.ca.ibone.comcast.net [96.110.39.18]

13 42 ms 43 ms 41 ms be-1411-cs04.sunnyvale.ca.ibone.comcast.net [96.110.46.37]

14 45 ms 43 ms 43 ms be-3402-pe02.529bryant.ca.ibone.comcast.net [96.110.41.222]

15 43 ms 50 ms 43 ms 75.149.231.242

16 45 ms 43 ms 42 ms 203.208.172.233

17 247 ms 305 ms 315 ms 203.208.152.213

18 207 ms 290 ms 305 ms 203.208.166.206

19 276 ms 307 ms 303 ms 203.208.166.241

20 214 ms 280 ms 303 ms 203.208.152.1

21 294 ms 305 ms 305 ms 203.208.158.189

22 249 ms 305 ms 306 ms 203.208.182.249

23 263 ms 257 ms 252 ms 203.208.172.174

24 306 ms 220 ms 286 ms 203.208.174.66

25 228 ms 304 ms 305 ms 103.28.251.204.ip.incapdns.net [103.28.251.204]

Trace complete.



Amazon.co.jp

C:\Users\tyler>tracert amazon.co.jp

Tracing route to amazon.co.jp [52.119.164.121]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1

2 10 ms 10 ms 12 ms 100.92.206.131

3 11 ms 10 ms 10 ms 96.216.145.101

4 22 ms 10 ms 11 ms 68.86.182.121

5 12 ms 10 ms 12 ms po-200-xar01.albuquerque.nm.albuq.comcast.net [68.85.65.89]

6 14 ms 43 ms 11 ms 96.108.43.101

7 20 ms 18 ms 22 ms be-36821-cs02.1601milehigh.co.ibone.comcast.net [96.110.44.21]

8 20 ms 18 ms 19 ms be-1214-cr14.1601milehigh.co.ibone.comcast.net [96.110.39.118]

9 23 ms 20 ms 18 ms be-304-cr14.champa.co.ibone.comcast.net [96.110.39.13]

10 21 ms 19 ms 21 ms be-1414-cs04.champa.co.ibone.comcast.net [96.110.37.253]

11 22 ms 19 ms 19 ms be-3412-pe12.910fifteenth.co.ibone.comcast.net [96.110.33.142]

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 38 ms 26 ms 25 ms 52.93.74.95

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 53 ms 52 ms 59 ms 108.166.232.57

25 59 ms 52 ms 50 ms 108.166.232.57

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

Trace complete.



Traveling Through a Network Reflection 

Network diagnostic tools that assist you in understanding how packets move via a network include the ping and traceroute commands. They are very helpful for diagnosing network connectivity issues and finding routing or latency issues. Here is a quick explanation of how these commands function:

Ping is a straightforward command used to determine whether a host on an Internet Protocol (IP) network can be reached. Hosts are often servers or other computers.

Your computer transmits a series of tiny data packets to the target host when you issue the ping command with the target host's IP address or domain name.

The host will receive these packets and send back corresponding packets to your computer if it is reachable and responsive.

A packet's round-trip time—the amount of time it takes to go from your computer to the target host and back—is measured and reported by the ping command. This transit delay is often referred to as "ping latency."

With the aid of the more sophisticated network diagnostic program traceroute, you can see the route that packets take as they travel from your computer to a destination host.

Your computer sends a series of packets in the direction of the destination when you run the traceroute command with the IP address or domain name of a target host.

The value of each processed packet is decreased by each router or other network device between your computer and the destination.

When a packet hits zero, the router discards it and returns to your computer a Time Exceeded notification.

Traceroute can identify the path that packets cross as well as the IP addresses of the intermediary routers or hops by examining these Time Exceeded notifications.

Using traceroute, you can see the network path and any potential bottlenecks by viewing the list of hops along with their IP addresses and round-trip times.

Ping and traceroute aid in locating reachability, network, and routing concerns. It's critical to take into account variables like host availability, network congestion, security settings, and router behavior while experiencing timeouts or failures in order to identify the underlying reason for connectivity problems.