332 replies to this topic

[BumbleBee]

My ping is stable at ~255ms using iiNet from Wagga (500km west of Sydney), so basically the same as it was before the move, maybe even a little more stable.

Most of the issues seem to be with Telstra customers.

[Tsig]

I think it's safe to say that N0MAD works for Telstra and doesn't appreciate the rest of you badmouthing his place of employment.

[Wingbreaker]

N0MAD, on 03 September 2014 - 04:45 AM, said:

But point taken my contribution to this thread is done.

Because a routing issue is totally not the fault of the ISP, right?

"Contribution"

Edited by Wingbreaker, 03 September 2014 - 04:55 AM.

[Oderint dum Metuant]

BumbleBee, on 03 September 2014 - 04:49 AM, said:

My ping is stable at ~255ms using iiNet from Wagga (500km west of Sydney), so basically the same as it was before the move, maybe even a little more stable.

Most of the issues seem to be with Telstra customers.

It must just be coincidence you guys on different ISPS don't have this problem

[Aznox]

This routing problem could be solved in one hour : just have an OVH network engineer contact a Telstra network engineer, both check what's wrong in their BGP config.

/THREAD

[Impyrium]

N0MAD, on 03 September 2014 - 04:45 AM, said:

Mate to true, im cool with it, but i goto tell you when some guys blame ISPs for whats happening to the ping in MWO ( especially taking into account MWO has just changed its servers and the problem has manifested itself at the same time) and then go onto say that it affects no other game then i feel compelled to point to common sense.
But point taken my contribution to this thread is done.

NOMAD, I'm guessing you're not from Australia, and haven't dealt with the ISPs here. There are very little, if any, decent ISPs in Australia, at least for those of us that don't live in one of the major capitals. Telstra is pretty much all we have. Telstra is not a reasonable ISP- it knows it can get away with a shoddy service because it often provides the only service. It is quite different to what I hear you guys get in America and Europe.

I would not be surprised if Telstra has something borked up regarding this. I also know getting them to do something about it is going to be nigh impossible.

[Clobba]

Meh turns out I still am over WoTs....anyway tried VPN and first set it for Montreal and knocked 100 off my ping down to 280 odd, then reading through this I tried L.A. and am now 245-60 which is almost old premove ping so I guess I am shelling out for VPN once the trial finishes

[0verClock]

I believe most south east asian player like Singapore, Malaysia & Indonesia also got a higher ping since migration. Is it possible to switch back to the old data center after u re-furbished it? I live in Indonesia and my ping increased about 20-30ms in general.

[Oderint dum Metuant]

0verClock, on 03 September 2014 - 07:33 AM, said:

I believe most south east asian player like Singapore, Malaysia & Indonesia also got a higher ping since migration. Is it possible to switch back to the old data center after u re-furbished it? I live in Indonesia and my ping increased about 20-30ms in general.

You misunderstand what's happened here. PGI don't host the servers a 3rd party do.

They swapped host for financial cost reasons; there is no going back

[Almond Brown]

The Route taken to the new Servers is from "your end". The likely cause is the IP address change. PGI does not "connect, or route" to anyone, we "connect , or route" to them via our ISP's. So yes, it is a ISP issue for everyone.

Edited by Almond Brown, 03 September 2014 - 07:52 AM.

[ShinVector]

0verClock, on 03 September 2014 - 07:33 AM, said:

I believe most south east asian player like Singapore, Malaysia & Indonesia also got a higher ping since migration. Is it possible to switch back to the old data center after u re-furbished it? I live in Indonesia and my ping increased about 20-30ms in general.

Cancel Singapore from that list. The few I know.. lower ping... Mine is -30ms++ Less jitter too.

[Clit Beastwood]

Lol my ISP says "There's no problem" - check out the first couple hops lol

1 192.168.1.1 (192.168.1.1) 0.566 ms 0.438 ms 0.299 ms
2 192.168.0.1 (192.168.0.1) 1.041 ms 0.653 ms 0.464 ms
3 cpe-172-251-240-1.socal.res.rr.com (172.251.240.1) 485.246 ms 264.064 ms 254.317 ms
4 tge7-2.brwdcaae01h.socal.rr.com (76.166.7.185) 238.488 ms 223.686 ms 226.666 ms
5 tge0-9-0-2.cyprcabw01r.socal.rr.com (72.129.21.192) 232.299 ms 227.779 ms 224.395 ms
6 agg27.lsancarc01r.socal.rr.com (72.129.21.0) 223.900 ms 227.199 ms 239.538 ms
7 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 219.932 ms 136.909 ms 191.951 ms
8 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 183.546 ms 178.530 ms 236.215 ms
9 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 233.044 ms 218.826 ms 219.990 ms
10 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 230.540 ms 225.402 ms 235.817 ms
11 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 226.739 ms 222.166 ms 227.718 ms
12 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 229.547 ms 236.312 ms 243.938 ms
13 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 240.618 ms 234.981 ms 239.943 ms
14 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 227.665 ms 236.114 ms 247.556 ms
15 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 218.190 ms 195.260 ms 231.395 ms
16 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 234.759 ms 235.495 ms 244.366 ms
17 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 247.244 ms 244.239 ms 251.178 ms
18 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 237.558 ms 233.065 ms 222.948 ms
19 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 228.307 ms 239.561 ms 75.856 ms
20 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 55.642 ms 35.181 ms 35.894 ms
21 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 49.623 ms 23.881 ms 27.630 ms
22 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 30.456 ms 23.220 ms 28.218 ms
23 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 22.779 ms 31.278 ms 23.893 ms
24 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 30.094 ms 23.486 ms 28.300 ms
25 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 28.266 ms 55.681 ms 27.918 ms
26 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 31.227 ms 36.058 ms 71.717 ms
27 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 29.014 ms 24.012 ms 28.048 ms
28 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 31.087 ms 42.786 ms 56.542 ms
29 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 59.357 ms 27.001 ms 32.059 ms
30 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 58.068 ms 38.931 ms 32.500 ms
31 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 48.318 ms 27.930 ms 31.482 ms
32 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 54.885 ms 32.120 ms 35.877 ms
33 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 56.909 ms 47.628 ms 28.267 ms
34 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 34.048 ms 55.807 ms 33.167 ms
35 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 57.518 ms 48.150 ms 39.509 ms
36 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 30.548 ms 42.809 ms 31.889 ms
37 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 32.744 ms 35.347 ms 32.778 ms
38 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 34.696 ms 39.504 ms 31.488 ms
39 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 34.570 ms 30.333 ms 32.230 ms
40 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 34.730 ms 30.919 ms 36.228 ms
41 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 62.980 ms 35.110 ms 32.344 ms
42 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 33.512 ms 35.950 ms 35.494 ms
43 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 88.687 ms 35.180 ms 35.960 ms
44 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 55.179 ms 31.508 ms 32.202 ms
45 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 32.975 ms 36.125 ms 43.635 ms
46 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 42.931 ms 55.353 ms 40.214 ms
47 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 34.647 ms 47.313 ms 55.739 ms
48 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 34.096 ms 35.752 ms 71.572 ms
49 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 124.816 ms 43.930 ms 43.437 ms
50 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 63.621 ms 78.714 ms 48.268 ms
51 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 106.207 ms 210.964 ms 103.717 ms
52 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 107.373 ms 106.564 ms 272.238 ms
53 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 391.046 ms 327.324 ms 48.248 ms
54 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 57.851 ms 51.095 ms 56.989 ms
55 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 44.161 ms 43.224 ms 47.925 ms
56 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 47.273 ms 43.725 ms 47.744 ms
57 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 61.329 ms 47.790 ms 39.973 ms
58 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 54.709 ms 43.387 ms 45.524 ms
59 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 53.041 ms 47.836 ms 60.230 ms
60 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 49.442 ms 51.520 ms 44.674 ms
61 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 115.835 ms 51.154 ms 44.351 ms
62 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 99.409 ms 187.838 ms 152.266 ms
63 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 148.715 ms 139.508 ms 147.934 ms
64 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 154.517 ms 155.336 ms 160.972 ms

[Draven Darkshadow]

guys... try reading my post and using that small app to find out which is the best dns server to use

http://mwomercs.com/...07#entry3687707

right now i'm using google's dns service and i'm getting 20% improvement

[Clit Beastwood]

as evidenced by some of the traceroutes above, the issue for many is routing, NOT dns.

[Sprouticus]

Fierostetz, on 03 September 2014 - 09:28 AM, said:

Lol my ISP says "There's no problem" - check out the first couple hops lol

1 192.168.1.1 (192.168.1.1) 0.566 ms 0.438 ms 0.299 ms
2 192.168.0.1 (192.168.0.1) 1.041 ms 0.653 ms 0.464 ms
3 cpe-172-251-240-1.socal.res.rr.com (172.251.240.1) 485.246 ms 264.064 ms 254.317 ms
4 tge7-2.brwdcaae01h.socal.rr.com (76.166.7.185) 238.488 ms 223.686 ms 226.666 ms
5 tge0-9-0-2.cyprcabw01r.socal.rr.com (72.129.21.192) 232.299 ms 227.779 ms 224.395 ms
6 agg27.lsancarc01r.socal.rr.com (72.129.21.0) 223.900 ms 227.199 ms 239.538 ms
7 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 219.932 ms 136.909 ms 191.951 ms
8 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 183.546 ms 178.530 ms 236.215 ms
9 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 233.044 ms 218.826 ms 219.990 ms
10 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 230.540 ms 225.402 ms 235.817 ms
11 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 226.739 ms 222.166 ms 227.718 ms
12 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 229.547 ms 236.312 ms 243.938 ms
13 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 240.618 ms 234.981 ms 239.943 ms
14 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 227.665 ms 236.114 ms 247.556 ms
15 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 218.190 ms 195.260 ms 231.395 ms
16 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 234.759 ms 235.495 ms 244.366 ms
17 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 247.244 ms 244.239 ms 251.178 ms
18 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 237.558 ms 233.065 ms 222.948 ms
19 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 228.307 ms 239.561 ms 75.856 ms
20 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 55.642 ms 35.181 ms 35.894 ms
21 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 49.623 ms 23.881 ms 27.630 ms
22 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 30.456 ms 23.220 ms 28.218 ms
23 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 22.779 ms 31.278 ms 23.893 ms
24 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 30.094 ms 23.486 ms 28.300 ms
25 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 28.266 ms 55.681 ms 27.918 ms
26 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 31.227 ms 36.058 ms 71.717 ms
27 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 29.014 ms 24.012 ms 28.048 ms
28 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 31.087 ms 42.786 ms 56.542 ms
29 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 59.357 ms 27.001 ms 32.059 ms
30 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 58.068 ms 38.931 ms 32.500 ms
31 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 48.318 ms 27.930 ms 31.482 ms
32 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 54.885 ms 32.120 ms 35.877 ms
33 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 56.909 ms 47.628 ms 28.267 ms
34 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 34.048 ms 55.807 ms 33.167 ms
35 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 57.518 ms 48.150 ms 39.509 ms
36 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 30.548 ms 42.809 ms 31.889 ms
37 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 32.744 ms 35.347 ms 32.778 ms
38 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 34.696 ms 39.504 ms 31.488 ms
39 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 34.570 ms 30.333 ms 32.230 ms
40 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 34.730 ms 30.919 ms 36.228 ms
41 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 62.980 ms 35.110 ms 32.344 ms
42 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 33.512 ms 35.950 ms 35.494 ms
43 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 88.687 ms 35.180 ms 35.960 ms
44 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 55.179 ms 31.508 ms 32.202 ms
45 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 32.975 ms 36.125 ms 43.635 ms
46 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 42.931 ms 55.353 ms 40.214 ms
47 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 34.647 ms 47.313 ms 55.739 ms
48 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 34.096 ms 35.752 ms 71.572 ms
49 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 124.816 ms 43.930 ms 43.437 ms
50 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 63.621 ms 78.714 ms 48.268 ms
51 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 106.207 ms 210.964 ms 103.717 ms
52 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 107.373 ms 106.564 ms 272.238 ms
53 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 391.046 ms 327.324 ms 48.248 ms
54 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 57.851 ms 51.095 ms 56.989 ms
55 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 44.161 ms 43.224 ms 47.925 ms
56 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 47.273 ms 43.725 ms 47.744 ms
57 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 61.329 ms 47.790 ms 39.973 ms
58 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 54.709 ms 43.387 ms 45.524 ms
59 agg10.grdncadd01r.socal.rr.com (72.129.33.4) 53.041 ms 47.836 ms 60.230 ms
60 agg25.lsancarc01r.socal.rr.com (72.129.33.0) 49.442 ms 51.520 ms 44.674 ms
61 agg1.lsaicaev01r.socal.rr.com (72.129.17.1) 115.835 ms 51.154 ms 44.351 ms
62 agg10.lsaicaev02r.socal.rr.com (72.129.17.5) 99.409 ms 187.838 ms 152.266 ms
63 agg26.tustcaft01r.socal.rr.com (72.129.17.2) 148.715 ms 139.508 ms 147.934 ms
64 agg1.grdncadd02r.socal.rr.com (72.129.33.3) 154.517 ms 155.336 ms 160.972 ms

Wow that is a LOT of hops. That many devices alone will add a ton of latency.

As for the first 2 hops, there are other reasons latency can be high at specific hope, the most obviousl is an overloaded/high CPU router. Remember, traceroute uses TTL so that a packet 'ends' at each hop. If the device take a (relatively) long time to respond it can cause this kind of issue where hop 2-3 are horrible but after that it is ok.

Oddly enough the bad response time on the routers has minimal impact on your traffic. The last few hops are the really important ones. (unless one is timing out.

[Egomane]

Sprouticus, on 03 September 2014 - 11:09 AM, said:

Wow that is a LOT of hops. That many devices alone will add a ton of latency.

Look closer! He is going in circles.

[Heffay]

Tsig, on 03 September 2014 - 04:54 AM, said:

I think it's safe to say that N0MAD works for Telstra and doesn't appreciate the rest of you badmouthing his place of employment.

Careful, he might sue you and your employer if you say something about him!

FWIW: The servers moved 600km further away from me (AZ) and my ping times went from 90-100 ms to 70-80 ms. Go figure.

Edited by Heffay, 03 September 2014 - 11:15 AM.

[Darth Futuza]

AssaultPig, on 31 August 2014 - 11:35 PM, said:

PGI apparently doesn't consider VPN use cheating (for some insane reason), so people who are really having trouble might try using one to get a better/more stable route to the servers.

...why would that be cheating?

[Clit Beastwood]

Sprouticus, on 03 September 2014 - 11:09 AM, said:

Wow that is a LOT of hops. That many devices alone will add a ton of latency.

As for the first 2 hops, there are other reasons latency can be high at specific hope, the most obviousl is an overloaded/high CPU router. Remember, traceroute uses TTL so that a packet 'ends' at each hop. If the device take a (relatively) long time to respond it can cause this kind of issue where hop 2-3 are horrible but after that it is ok.

Oddly enough the bad response time on the routers has minimal impact on your traffic. The last few hops are the really important ones. (unless one is timing out.

Yeah the router at present is a cisco asa 5505, I've switched between a few. It's definitely outside the network. Time Warner/roadrunner insists there are no issues but....

I'm a network engineer by trade, I ran my traceroute and started laughing because they insist repeatedly there's no slowdown on the network, and no excessive hops. All traceroutes from me to anywhere look like this - ISP is coming out to replace some equipment on the pole today, so... :fingers crossed:

I really want FIOS, but it stopped 12 houses down the street from me :facepalm:

Darth Futuza, on 03 September 2014 - 11:15 AM, said:

...why would that be cheating?

yeah, same here - if your ISP throttles unidentified UDP traffic or something, the only way to play consistently is vpn.

[Sprouticus]

Enileph, on 03 September 2014 - 04:19 AM, said:

I am playing in Hong Kong, and since the move HK and Taiwan players have almost unplayable games.
Ping is increased by a huge amount, my ping goes from the previous 200ish max to the current high 300ish.

Lots of lag spike and rubberbanding, at first I though it was my pc's problem but other games I play in are just fine as is.

Current tracert, takes 13 steps. It is being sent through europe instead of crossing the pacific ocean like it used to be. Frankly speaking I am quite disappointed at the whole situation. I see it being routed through it.eu then de.eu and fr.eu. NOT a good sign. Please help find a solution asap. I really love this game and really want to see it playable (right now you cannot even LRM nicely). Thanks.


Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 20 ms 42 ms 45 ms 192.168.8.1
2 9 ms 8 ms 8 ms 10.193.231.54
3 9 ms 9 ms 8 ms wtsc3a054.netvigator.com [218.102.40.54]
4 9 ms 9 ms 13 ms tenge4-4.br02.hkg05.pccwbtn.net [63.218.254.69]

5 24 ms 24 ms 28 ms 63-218-107-38.static.pccwglobal.net [63.218.107.
38]
6 * 108 ms 108 ms 195.22.192.103
7 135 ms * 136 ms mil-1-6k.it.eu [91.121.131.25]
8 * * 154 ms fra-1-6k.de.eu [213.251.128.66]
9 140 ms 136 ms 137 ms sbg-g1-a9.fr.eu [91.121.128.127]
10 137 ms 136 ms 136 ms 37.187.36.153
11 * * * Request timed out.
12 * * * Request timed out.
13 142 ms 150 ms 140 ms mwomercs.com [192.99.109.192]

Trace complete.

Still got timeouts when tracing. That is all.

the 'request timeout' hops you can ignore. That is just the device in quesiton being setup not to respond to trace routes.

The singular ones though....that is an issue.

Here is another test.

1) open 5 or 6 command windows
2) select the Ip of the 2nd or 3rd hop
3) in one window, do a ping {ip address from step 2} -t
4) Select another hope 1-2 up and repeat in another window.
5) Repeat up the line.

then watch all the windows and see if you can find the hop where the timeout occurs. Remember, just because a packet fails to return on one hop does not mean it is that hop. It cold be ANY up up to and including that one.

Egomane, on 03 September 2014 - 11:11 AM, said:

Look closer! He is going in circles.

Holy crap, I didnt even see that because the names are so similar.

Yea, totally a routing loop! That is a REALLY poorly designed network.