razumevanje traceroute i pinga

[bmaxa]

Elem traceroute i ping su alati za otkrivanje problema na mrezhi, traceroute pokazuje da li je na odredjenom hopu problem,
dok ping pokazuje da li je negde u stazi hopova problem. Dakle traceroute je precizniji.
Primer kod mene trenutno:

bmaxa@Branimirs-Air odinprograms % traceroute google.rs
traceroute to google.rs (142.250.184.227), 64 hops max, 52 byte packets
 1  rt-ax86u-91c8 (192.168.101.1)  3.498 ms  2.960 ms  4.450 ms
 2  10.15.0.1 (10.15.0.1)  12.544 ms  10.484 ms  11.760 ms
 3  vlan151.as04.beg1.rs.m247.com (89.38.224.73)  12.260 ms  11.774 ms  10.871 ms
 4  193.27.15.42 (193.27.15.42)  35.364 ms  33.071 ms  21.380 ms
 5  xe-0-0-2-0.bb1.beg1.rs.m247.com (212.103.51.176)  10.259 ms  11.302 ms  10.813 ms
 6  xe-4-3-3-0.core1.fra2.de.m247.com (212.103.51.227)  28.022 ms  29.877 ms  29.136 ms
 7  212.103.51.63 (212.103.51.63)  30.222 ms  28.596 ms  29.618 ms
 8  no-mans-land.m247.com (185.206.226.71)  27.359 ms  29.380 ms  28.739 ms
 9  * * *
10  142.250.46.244 (142.250.46.244)  30.323 ms
    142.250.229.58 (142.250.229.58)  28.133 ms
    108.170.252.65 (108.170.252.65)  29.220 ms
11  108.170.252.82 (108.170.252.82)  29.027 ms
    142.251.64.183 (142.251.64.183)  29.701 ms  29.253 ms
12  108.170.238.60 (108.170.238.60)  30.702 ms
    108.170.229.168 (108.170.229.168)  30.939 ms
    108.170.238.60 (108.170.238.60)  30.994 ms
13  108.170.228.8 (108.170.228.8)  28.267 ms
    209.85.241.70 (209.85.241.70)  30.235 ms
    209.85.252.28 (209.85.252.28)  29.183 ms
14  fra24s12-in-f3.1e100.net (142.250.184.227)  29.257 ms  31.982 ms
    108.170.251.129 (108.170.251.129)  30.139 ms
bmaxa@Branimirs-Air odinprograms % traceroute6 google.rs
traceroute6 to google.rs (2a00:1450:400d:80c::2003) from 2a06:5b00:1504:47f0:3dcc:ef3d:50ee:e346, 64 hops max, 12 byte packets
 1  2a06:5b00:1504:47f0::1  2.552 ms  4.511 ms  3.030 ms
 2  * * *
 3  bg-tkc-vf-c-1-bu1-900.sn.co.rs  10.389 ms  14.607 ms  11.079 ms
 4  bg-tkc-vf-m-1-be3.sn.co.rs  10.043 ms  15.214 ms  10.475 ms
 5  bg-tkc-m-0-hu0-0-0-24.sn.co.rs  10.320 ms  12.834 ms  11.874 ms
 6  bg-zl-m-0-be2.sn.co.rs  10.479 ms  10.974 ms  10.079 ms
 7  bg-zl-m-1-be1-904.sn.co.rs  11.837 ms  15.882 ms  12.904 ms
 8  bg-zl-m-0-be3.sn.co.rs  11.641 ms  10.825 ms  11.321 ms
 9  2a00:e90:0:b::66  18.458 ms  10.860 ms  12.087 ms
10  2a00:e90::212:200:6:5  11.553 ms  12.898 ms  11.581 ms
11  2a00:e90::212:200:6:8  10.884 ms  11.661 ms  12.839 ms
12  2a00:e90:0:a::3  17.993 ms  18.418 ms  21.071 ms
13  2001:4860::1c:4001:2d38  16.920 ms *  18.469 ms
14  * * *
15  bud02s37-in-x03.1e100.net  17.385 ms  17.366 ms  16.917 ms
bmaxa@Branimirs-Air odinprograms % ping -c 10 google.rs
PING google.rs (142.250.184.227): 56 data bytes
64 bytes from 142.250.184.227: icmp_seq=0 ttl=115 time=29.305 ms
64 bytes from 142.250.184.227: icmp_seq=1 ttl=115 time=29.145 ms
64 bytes from 142.250.184.227: icmp_seq=2 ttl=115 time=31.493 ms
64 bytes from 142.250.184.227: icmp_seq=3 ttl=115 time=30.839 ms
64 bytes from 142.250.184.227: icmp_seq=4 ttl=115 time=29.255 ms
64 bytes from 142.250.184.227: icmp_seq=5 ttl=115 time=29.765 ms
64 bytes from 142.250.184.227: icmp_seq=6 ttl=115 time=33.723 ms
64 bytes from 142.250.184.227: icmp_seq=7 ttl=115 time=28.884 ms
64 bytes from 142.250.184.227: icmp_seq=8 ttl=115 time=27.358 ms
64 bytes from 142.250.184.227: icmp_seq=9 ttl=115 time=28.486 ms

--- google.rs ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 27.358/29.825/33.723/1.698 ms
bmaxa@Branimirs-Air odinprograms % ping6 -c 10 google.rs
PING6(56=40+8+8 bytes) 2a06:5b00:1504:47f0:3dcc:ef3d:50ee:e346 --> 2a00:1450:4014:80b::2003
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=0 hlim=49 time=33.450 ms
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=1 hlim=49 time=32.288 ms
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=2 hlim=49 time=32.359 ms
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=3 hlim=49 time=32.398 ms
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=4 hlim=49 time=35.340 ms
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=5 hlim=49 time=38.831 ms
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=6 hlim=49 time=32.136 ms
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=7 hlim=49 time=31.689 ms
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=8 hlim=49 time=35.550 ms
16 bytes from 2a00:1450:4014:80b::2003, icmp_seq=9 hlim=49 time=31.712 ms

--- google.rs ping6 statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 31.689/33.575/38.831/2.197 ms

Dakle prvi hop je ruter, pa ide CMTS, pa prvi internet hop.
Tri brojke vremena znachi tri staze koje prolaze ovaj broj treba da bude priblizhno
isti.
Ukoliko negde brojke u ms odskachu, to znachi da je tu problem.
Ovo kod mene na ipv4 je VPN, a na ipv6 direktno. Dakle VPN je brz
Nishta ne odslikava neki problem..
inache do rutera mi je 3ms, jer wifi ima latenciju, poshto je ovo sa laptopa...

 

[Truman]

Mi na poslu stalno pingujemo IP adrese, rutere i servere u command promptu i otprilike izlaze slicni rezultati u milisekundama. To radimo kad treba da utvrdimo da li je device online. Koliko znam to je echo. A za traceroute i hop nisam cuo.