Alan, not sure where your getting blocked at, I was able to get almost there several times. Here is the last trace I did. THis originates in Omaha NE. Trent
1 promisenet (208.47.115.1) 197.716 ms 199.458 ms 199.921 ms 2 kcm-edge-10.inet.qwest.net (65.116.32.249) 200.037 ms 199.723 ms 199.904 ms 3 kcm-core-03.inet.qwest.net (205.171.29.89) 200.173 ms 199.789 ms 199.879 ms 4 cer-core-02.inet.qwest.net (205.171.8.169) 199.881 ms 199.732 ms 199.927 ms 5 cer-core-01.inet.qwest.net (205.171.139.1) 199.901 ms 200.011 ms 199.756 ms 6 chi-core-02.inet.qwest.net (205.171.205.33) 199.928 ms 199.843 ms 200.004 ms 7 chi-brdr-03.inet.qwest.net (205.171.20.138) 199.799 ms 199.842 ms 199.891 ms 8 205.171.1.162 (205.171.1.162) 200.005 ms 207.115 ms 192.413 ms 9 144.232.26.113 (144.232.26.113) 199.905 ms 199.612 ms 199.825 ms 10 144.232.20.156 (144.232.20.156) 199.930 ms 199.899 ms 199.849 ms 11 144.232.6.89 (144.232.6.89) 199.926 ms 201.194 ms 199.020 ms 12 144.232.9.151 (144.232.9.151) 199.515 ms 199.432 ms 209.881 ms 13 144.232.17.182 (144.232.17.182) 209.903 ms 199.773 ms 199.935 ms 14 144.232.20.194 (144.232.20.194) 439.902 ms 399.775 ms 399.898 ms 15 sl-gw10-hk-15-0.sprintlink.net (203.222.38.42) 399.984 ms 399.677 ms 399.595 ms 16 sla-chnet-2-0.sprintlink.net (203.222.39.106) 599.890 ms 599.693 ms 599.905 ms 17 210.53.126.5 (210.53.126.5) 399.886 ms 399.950 ms 399.897 ms 18 210.52.132.233 (210.52.132.233) 399.877 ms 400.062 ms 449.447 ms 19 2p0-gsr2-wh1.cncnet.net (210.52.130.70) 399.924 ms 399.868 ms 399.841 ms 20 3p0-gsr2-bj1.cncnet.net (210.52.130.25) 399.996 ms 399.835 ms 399.974 ms 21 210.52.148.54 (210.52.148.54) 399.843 ms 399.421 ms 399.893 ms 22 210.82.1.29 (210.82.1.29) 599.911 ms 399.827 ms 399.906 ms 23 210.82.1.77 (210.82.1.77) 599.910 ms 599.232 ms 400.327 ms 24 210.82.98.153 (210.82.98.153) 449.457 ms 599.814 ms 599.930 ms 25 211.155.191.253 (211.155.191.253) 599.901 ms 599.400 ms 599.881 ms 26 * * * 27 211.155.170.178 (211.155.170.178) 407.652 ms 599.834 ms * 28 * * * 29 * * * -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alan Rader Sent: Tuesday, March 23, 2004 7:49 AM To: [EMAIL PROTECTED] Subject: [mrtg] Re: OT: Overseas Network Connections We cannot test pings or trace routes all the way, the ISP says their upstream provider, I think China Netcom blocks this kind of stuff and it is there policy and they block it both ways. I think they are one of the main pipes into China. If you have time, check out how far you can get and what you see to ip 211.155.170.161 and let me know. I get as far as Sprintlink Asia Pacific Region 203.222.38.42. >From another location I get stopped at 210.82.1.29 which is China Netcom. Thanks -----Original Message----- From: Gary Smith [mailto:[EMAIL PROTECTED] Sent: Monday, March 15, 2004 4:39 PM To: Alan Rader; [EMAIL PROTECTED] Subject: RE: [mrtg] OT: Overseas Network Connections Alan, Some of the things that you might want to try would be to do an extended ping. Send a larget packet out and set the wait time to 30 seconds or so. See if you are still seeing drops or extended delays. My full time job has a T3 from NY to Croyden and SF to Croyden and we see some horrible latency during different times of the day. I guess there's just not enough fiber in the ocean :). Sometimes the delays are inevitable. BTW, you should conduct these tests against the external interfaces of each location and not the VPN portion. If the external tests are fine then you probably have a problem with something in your VPN configuration. Without more details I really can't comment on it. We have setup a 5 legged VPN with 3 locations in California, 1 in Florida and Tennessee. We did it using Linux, poptop and pptpd clients. 3 of the locations are T1's and the other two are low end DSL's (IDSL actually). We get latency but never packet loss. In either event I would also contact the remote ISP and raise the issue with them. Gary -----Original Message----- From: [EMAIL PROTECTED] on behalf of Alan Rader Sent: Mon 3/15/2004 11:20 AM To: [EMAIL PROTECTED] Cc: Subject: [mrtg] OT: Overseas Network Connections We are opening an office in China (Beijing) and our office supposedly has a E1 to the Internet. We have setup a site to site VPN and I don't know if this is normal or what, but I think it sucks :(. Average response time is over 300ms and I am seeing about 15% packet loss. Response times and packet loss are jumping up and down constantly. Even right now when it is 3:00am over there, response times are around 250ms and packet loss is still up and down from %5 - 30%. We have a T3 out of our US office that is barely used. Pings and traceroutes are dropped somewhere in China, I think China Netcom or someone like that. Thanks for any help. -------------------------------------------- ATTENTION: This message and all attachments are PRIVATE, and may contain information that is CONFIDENTIAL and PRIVILEGED. If you received this message in error, please notify the sender by reply e-mail and delete the message immediately. -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi -------------------------------------------- ATTENTION: This message and all attachments are PRIVATE, and may contain information that is CONFIDENTIAL and PRIVILEGED. If you received this message in error, please notify the sender by reply e-mail and delete the message immediately. -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi -- Attached file removed by Ecartis and put at URL below -- -- Type: application/octet-stream -- Size: 1k (1975 bytes) -- URL : http://www.ee.ethz.ch/~slist/p/outfile -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
