Saya agak awam nih dengan masalah router, Mohon ada yang bisa menjelaskan email dibawah ini ??
Adhytia WS ________________________ Adhytia, We do not control the route your ISP chooses to send traffic to us, only the route we send it back -- if you're having trouble on the way to us (ie, via global crossing), then we'll have to talk to your ISP. As far as packet loss on our router proper, you probably should read FAQ #574 -- there are reasons why it would drop traceroute packets, but still be forwarding normal packets just fine. --------------------- traceroute to 202.134.3.5 (202.134.3.5), 30 hops max, 38 byte packets 1 66.33.80.1 (66.33.80.1) 1.595 ms 1.487 ms 1.629 ms 2 216.87.220.13 (216.87.220.13) 0.550 ms 0.511 ms 0.487 ms 3 pos12-0-0.ar1.TPA1.gblx.net (64.215.187.61) 7.466 ms 7.283 ms 6.938 ms 4 pos5-2-155M.cr1.ATL1.gblx.net (208.178.116.33) 32.342 ms 32.071 ms 32.442 ms 5 pos0-0-0-155M.br1.ATL1.gblx.net (206.132.115.118) 32.214 ms 32.214 ms 32.226 ms 6 57.ATM2-0.BR1.ATL5.ALTER.NET (204.255.168.137) 25.126 ms 25.007 ms 25.092 ms 7 0.so-2-3-0.XL1.ATL5.ALTER.NET (152.63.82.198) 25.907 ms 25.845 ms 25.554 ms 8 0.so-2-1-0.TL1.ATL5.ALTER.NET (152.63.85.221) 25.555 ms 25.588 ms 25.255 ms 9 0.so-5-0-0.TL1.LAX9.ALTER.NET (152.63.10.94) 77.046 ms 77.516 ms 77.210 ms 10 0.so-1-0-0.XL1.LAX9.ALTER.NET (152.63.115.141) 77.064 ms 77.212 ms 77.158 ms 11 0.so-3-0-0.XR1.LAX9.ALTER.NET (152.63.115.157) 76.936 ms 77.189 ms 76.991 ms 12 191.at-2-0-0.TR1.LAX9.ALTER.NET (152.63.112.242) 77.085 ms 77.644 ms 77.203 ms 13 131.ATM5-0.IR1.LAX9.ALTER.NET (152.63.10.238) 77.175 ms 77.068 ms 76.781 ms 14 so-7-1-0.IR1.LAX12.ALTER.NET (137.39.31.225) 77.437 ms 76.951 ms 76.806 ms 15 0.so-3-1-0.TR1.HKG2.ALTER.NET (210.80.48.17) 232.759 ms 232.564 ms 0.so-1-0-0.TR1.HKG2.Alter.Net (210.80.50.42) 245.130 ms 16 0.so-3-2-0.XR1.HKG2.ALTER.NET (210.80.48.22) 232.131 ms 237.145 ms 237.483 ms 17 11.pos5-0-0.GW1.HKG2.ALTER.NET (210.80.3.2) 237.395 ms 237.175 ms 231.901 ms 18 PTTelkom-hk-gw.customer.alter.net (202.130.129.62) 238.356 ms 238.214 ms 238.602 ms 19 hssi1-0-gw3.cibinong.telkom.net.id (202.134.3.2) 733.178 ms 733.065 ms 727.864 ms 20 FE4-1-0-sm2.jakarta.telkom.net.id (202.134.3.133) 756.300 ms 697.721 ms 732.411 ms 21 fe-0-3-3.sm2.jakarta.telkom.net.id (202.134.3.26) 730.998 ms 742.425 ms 742.306 ms 22 so-110.surabaya.telkom.net.id (202.134.3.142) 832.399 ms 879.329 ms 902.306 ms 23 202.134.3.206 (202.134.3.206) 869.631 ms 882.356 ms 934.210 ms --------------------------------------- You'll notice that the latency doesn't really get bad until it reaches the border between UUNet and your ISP -- once it crosses the link that connects the two, it jumps by 500ms. Pinging UUNet's router on that border: --- 202.130.129.62 ping statistics --- 100 packets transmitted, 100 packets received, 0% packet loss round-trip min/avg/max/mdev = 223.545/228.988/238.650/4.536 ms Pinging telcom.net.id's router on that border: --- 202.134.3.2 ping statistics --- 100 packets transmitted, 97 packets received, 3% packet loss round-trip min/avg/max/mdev = 727.588/788.806/1236.013/115.102 ms The loss varies, though -- sometimes it's nothing, sometimes it's as high as 20%. I currently suspect that your ISP's link is oversubscribed. Generally speaking, the only times that you should see such high latency are either over a satellite line or on a line that has too much traffic traversing it -- however, the reverse DNS indicates it is not a satellite -- 'FE' usually means 'Fast Ethernet' and HSSI usually means 'high speed serial interface', which is typically something like an E3, DS3, etc. kylesparger �06-Apr-2002 �09:37:12 --------------------------------------------------------------------- Jumlah pelanggan (updated daily): 212 Untuk berhenti berlangganan, kirim email ke: [EMAIL PROTECTED] Arsip milis: http://klas.regex.com/archive/ Saat ini arsip milisnya lengkap, tapi kurang fungsional. Bila anda ingin menyumbangkan programming time untuk membuat arsip ini menjadi lebih baik, silakan hubungi [EMAIL PROTECTED]
