rajaah thunder Posted March 28, 2013 Share Posted March 28, 2013 I tried to detect lag in the ET silEnT server using mtr . this was the output . rajaah@rajaah-Aspire-5540:~$ mtr --report 108.61.21.93 HOST: rajaah-Aspire-5540 Loss% Snt Last Avg Best Wrst StDev 1.|-- MyDslModem.local.lan 0.0% 10 0.5 0.4 0.4 0.5 0.0 2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 I am unable to understand what is goin on . Is this the reason for my lag ? p.s : If i must post it in ET support section , please move it there . Quote Link to comment Share on other sites More sharing options...
Clan Friend SunLight Posted March 28, 2013 Clan Friend Share Posted March 28, 2013 $ man mtr [cut] --report This option puts mtr into report mode. When in this mode, mtr will run for the number of cycles specified by the -c option, and then print statistics and exit.[cut] I guess it defaults to 10, since I can omit -c and I get 10 cycles, so that's not the problem. Have you waited long enough for it to run? Have you tried without --report first? (you can still pause it with 'p', so you can copy the text, and space to resume) Anyway, if you want the report, you should redirect it to some file, for example for 20 cycles: $ mtr -c 20 -r 108.61.21.93 > report.txt I would try it without -r (the same as --report) first, and see what I get Quote Link to comment Share on other sites More sharing options...
rajaah thunder Posted March 29, 2013 Author Share Posted March 29, 2013 $ man mtr I guess it defaults to 10, since I can omit -c and I get 10 cycles, so that's not the problem. Have you waited long enough for it to run? Have you tried without --report first? (you can still pause it with 'p', so you can copy the text, and space to resume) Anyway, if you want the report, you should redirect it to some file, for example for 20 cycles: $ mtr -c 20 -r 108.61.21.93 > report.txt I would try it without -r (the same as --report) first, and see what I get i got the same output in the report too HOST: rajaah-Aspire-5540 Loss% Snt Last Avg Best Wrst StDev 1.|-- MyDslModem.local.lan 0.0% 20 0.5 0.4 0.3 0.5 0.0 2.|-- ??? 100.0 20 0.0 0.0 0.0 0.0 0.0 edit : whn i do it without report also , it shows the same . Do you think there is problem with my drivers ? Quote Link to comment Share on other sites More sharing options...
Clan Friend SunLight Posted March 29, 2013 Clan Friend Share Posted March 29, 2013 edit : whn i do it without report also , it shows the same . Do you think there is problem with my drivers ? so you don't get past second hop? can you just ping that server's ip, or try something else, like mtr google.com try this: $ mtr --no-dns -u 108.61.21.93 $ traceroute 108.61.21.93 Quote Link to comment Share on other sites More sharing options...
rajaah thunder Posted March 29, 2013 Author Share Posted March 29, 2013 this was what i got after 50 cycles . My traceroute [v0.80] rajaah-Aspire-5540 (0.0.0.0) Fri Mar 29 18:25:36 2013 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 192.168.1.1 0.0% 50 0.4 0.4 0.3 0.5 0.0 2. 117.202.80.1 91.8% 50 14.6 15.1 14.6 15.6 0.5 3. 218.248.161.234 93.9% 50 15.4 14.6 14.1 15.4 0.8 4. 218.248.255.30 93.9% 50 14.8 14.8 14.6 15.0 0.2 5. 115.114.130.49 95.9% 50 15.2 15.2 15.2 15.2 0.0 6. 180.87.36.9 98.0% 50 15.7 15.7 15.7 15.7 0.0 7. 180.87.12.53 95.9% 50 478.2 475.9 473.7 478.2 3.2 8. 180.87.12.110 98.0% 50 483.8 483.8 483.8 483.8 0.0 9. ??? 10. ??? 11. 66.198.127.1 93.9% 50 475.1 469.0 465.6 475.1 5.4 12. 66.198.127.82 93.9% 50 492.7 483.3 470.1 492.7 11.7 13. ??? 14. 193.251.251.102 98.0% 50 583.9 583.9 583.9 583.9 0.0 15. 108.61.93.105 95.8% 49 579.7 575.4 571.1 579.7 6.1 108.61.1.13 16. 108.61.79.38 95.8% 49 566.6 571.5 566.6 576.4 6.9 17. ??? P.s : my net is a bit shitty at that moment . I will paste the result when my net works normal . Quote Link to comment Share on other sites More sharing options...
Clan Friend SunLight Posted March 29, 2013 Clan Friend Share Posted March 29, 2013 wow lots of packet loss, that was made with udp, right? (-u option) can you try just: $ ping -c 20 108.61.21.93 or $ ping -c 20 117.202.80.1 (that should be your isp, right?) Quote Link to comment Share on other sites More sharing options...
rajaah thunder Posted March 30, 2013 Author Share Posted March 30, 2013 wow lots of packet loss, that was made with udp, right? (-u option) can you try just: $ ping -c 20 108.61.21.93 or $ ping -c 20 117.202.80.1 (that should be your isp, right?) this is ping to isp : rajaah@rajaah-Aspire-5540:~$ ping -c 20 117.202.80.1 PING 117.202.80.1 (117.202.80.1) 56(84) bytes of data. 64 bytes from 117.202.80.1: icmp_req=1 ttl=254 time=14.0 ms 64 bytes from 117.202.80.1: icmp_req=2 ttl=254 time=14.6 ms 64 bytes from 117.202.80.1: icmp_req=3 ttl=254 time=14.6 ms 64 bytes from 117.202.80.1: icmp_req=4 ttl=254 time=13.8 ms 64 bytes from 117.202.80.1: icmp_req=5 ttl=254 time=14.2 ms 64 bytes from 117.202.80.1: icmp_req=6 ttl=254 time=15.0 ms 64 bytes from 117.202.80.1: icmp_req=7 ttl=254 time=14.9 ms 64 bytes from 117.202.80.1: icmp_req=8 ttl=254 time=14.5 ms 64 bytes from 117.202.80.1: icmp_req=9 ttl=254 time=14.8 ms 64 bytes from 117.202.80.1: icmp_req=10 ttl=254 time=14.9 ms 64 bytes from 117.202.80.1: icmp_req=11 ttl=254 time=15.8 ms 64 bytes from 117.202.80.1: icmp_req=12 ttl=254 time=15.6 ms 64 bytes from 117.202.80.1: icmp_req=13 ttl=254 time=14.5 ms 64 bytes from 117.202.80.1: icmp_req=14 ttl=254 time=14.3 ms 64 bytes from 117.202.80.1: icmp_req=15 ttl=254 time=15.0 ms 64 bytes from 117.202.80.1: icmp_req=16 ttl=254 time=15.0 ms 64 bytes from 117.202.80.1: icmp_req=17 ttl=254 time=13.8 ms 64 bytes from 117.202.80.1: icmp_req=18 ttl=254 time=14.5 ms 64 bytes from 117.202.80.1: icmp_req=19 ttl=254 time=14.5 ms 64 bytes from 117.202.80.1: icmp_req=20 ttl=254 time=15.4 ms --- 117.202.80.1 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19029ms rtt min/avg/max/mdev = 13.848/14.742/15.829/0.526 ms this is ping to server : rajaah@rajaah-Aspire-5540:~$ ping -c 20 108.61.21.93 PING 108.61.21.93 (108.61.21.93) 56(84) bytes of data. 64 bytes from 108.61.21.93: icmp_req=1 ttl=114 time=265 ms 64 bytes from 108.61.21.93: icmp_req=2 ttl=114 time=263 ms 64 bytes from 108.61.21.93: icmp_req=3 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=4 ttl=114 time=263 ms 64 bytes from 108.61.21.93: icmp_req=5 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=6 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=7 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=8 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=9 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=10 ttl=114 time=263 ms 64 bytes from 108.61.21.93: icmp_req=11 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=12 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=13 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=14 ttl=114 time=263 ms 64 bytes from 108.61.21.93: icmp_req=15 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=16 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=17 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=18 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=19 ttl=114 time=264 ms 64 bytes from 108.61.21.93: icmp_req=20 ttl=114 time=263 ms --- 108.61.21.93 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19020ms rtt min/avg/max/mdev = 263.061/264.374/265.635/0.567 ms Edit : I had not tried the traceroute you mentioned earlier but i am unable to understand the output . here's it though . rajaah@rajaah-Aspire-5540:~$ traceroute 108.61.21.93 traceroute to 108.61.21.93 (108.61.21.93), 30 hops max, 60 byte packets 1 MyDslModem.local.lan (192.168.1.1) 2.207 ms 2.144 ms 2.105 ms 2 117.193.224.1 (117.193.224.1) 31.926 ms 31.907 ms 31.869 ms 3 218.248.161.238 (218.248.161.238) 31.830 ms 31.796 ms 31.754 ms 4 218.248.255.82 (218.248.255.82) 32.160 ms 34.508 ms 36.536 ms 5 115.114.130.49.STATIC-Chennai.vsnl.net.in (115.114.130.49) 39.382 ms 42.356 ms 49.350 ms 6 172.29.250.34 (172.29.250.34) 81.397 ms 52.137 ms 53.332 ms 7 * * if-2-590.tcore2.L78-London.as6453.net (80.231.131.113) 561.636 ms 8 * * * 9 Vlan524.icore2.LDN-London.as6453.net (195.219.83.86) 287.426 ms 287.404 ms 288.044 ms 10 * * * 11 * * * 12 108.61.1.13.choopa.net (108.61.1.13) 278.258 ms ve66-br2.pnj1.choopa.net (108.61.93.105) 283.869 ms 108.61.1.13.choopa.net (108.61.1.13) 282.246 ms 13 ethernet1-2-2-c1-16-b2-1.pnj1.choopa.net (108.61.79.38) 274.632 ms 278.721 ms ethernet1-2-1-c1-16-b2-1.pnj1.choopa.net (108.61.79.34) 275.370 ms 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Quote Link to comment Share on other sites More sharing options...
Clan Friend SunLight Posted March 30, 2013 Clan Friend Share Posted March 30, 2013 this is ping to server : rajaah@rajaah-Aspire-5540:~$ ping -c 20 108.61.21.93 [cut] --- 108.61.21.93 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19020ms rtt min/avg/max/mdev = 263.061/264.374/265.635/0.567 ms so it seems your ping is stable (0.567ms mdev is good) and you have no packet loss... it could be that some nodes cut mtr traffic, or that you had lag only that day but your ping to the server is really stable Quote Link to comment Share on other sites More sharing options...
rajaah thunder Posted March 30, 2013 Author Share Posted March 30, 2013 yeah , but still , when i use the udp method , i get the same output [ lots of packet loss ] . any specific reason for it ? Quote Link to comment Share on other sites More sharing options...
Clan Friend SunLight Posted March 30, 2013 Clan Friend Share Posted March 30, 2013 yeah , but still , when i use the udp method , i get the same output [ lots of packet loss ] . any specific reason for it ? it could be that they limit traffic for those packets in some nodes you have to pass through anyway, if your ping to the destination is stable and without packet loss, I don't think it's necessary to use mtr. You use that when you have an unstable or higher than usual ping, and you want to know where exactly the slowdown occurs. Quote Link to comment Share on other sites More sharing options...
rajaah thunder Posted March 30, 2013 Author Share Posted March 30, 2013 it could be that they limit traffic for those packets in some nodes you have to pass through anyway, if your ping to the destination is stable and without packet loss, I don't think it's necessary to use mtr. You use that when you have an unstable or higher than usual ping, and you want to know where exactly the slowdown occurs. okay thanks for the info . May be dare should create a new level for you , admin level 99 "THE DOCTOR" i'll report it in tracker provided he is in a good mood Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.