FSK405 Forums


  • Please post here your traceroutes that show atleast a huge ping difference. the once sent prior showed me really noting and the planet said they were fine also. Like I said about that one blanked out hop, its stealth basically because you make it past, if it was bad you would get stopped dead in your tracks.. I need real results for them to take this serious.


    Dear Mike,

    The traceroute you provide shows no connectivity issues. Hop 12 times out because our IBR routers do no accept ICMP packet types to control their load. The fact that the hops continue to the server, shows that it is not blocking the connection, simply ignoring the packet requests and relaying the signal.

    If it is a packet loss issue, the best way to trouble shoot would be a pathping (http://technet.microsoft.com/en-us/library/cc958876.aspx) or MTR (http://forums.remote-exploit.org/tutorials-guides/12007-ho w-using-mtr.html). This will show the path, as does traceroute, but will also send many packets to each hop to test their reliability in data transfer compared to their load and configuration. Similar to traceroute, some servers may block the packet type so they will show 100% loss, if the loss does not continue down the path to the server, then they are simply blocking the packet type. If the loss does continue down the path however, it is due to that server not being able to take the load and is actually causing signal loss to your server.

    If you have any questions, please let us know.

    Thank you for choosing the planet,
    Christopher G.
    Technical Support
    www.theplanet.com
     

  • Hi Ghozt,

    Not sure if a single traceroute helps you at all, but here goes:


    Tracing route to www.fsk405.com [74.53.204.82]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 10 ms 9 ms 7 ms 10.34.0.1
    3 7 ms 7 ms 7 ms g-0-1-nycmnyc-rtr2.nyc.rr.com [24.29.97.98]
    4 10 ms 7 ms 8 ms tengig-12-0-0-nycmnya-rtr1.nyc.rr.com [24.29.97.
    9]
    5 8 ms 9 ms 8 ms tenge-0-3-0-nwrknjmd-rtr.nyc.rr.com [24.29.97.6]

    6 8 ms 8 ms 7 ms ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
    7 10 ms 10 ms 9 ms ae-1-0.pr0.nyc30.tbone.rr.com [66.109.6.161]
    8 8 ms 10 ms 10 ms xe-5-3-0.edge2.Newark1.Level3.net [4.59.20.37]
    9 11 ms 17 ms 18 ms ae-32-52.ebr2.Newark1.Level3.net [4.68.99.62]
    10 14 ms 15 ms 15 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101
    ]
    11 23 ms 17 ms 17 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
    50]
    12 31 ms 33 ms 35 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.1
    33]
    13 46 ms 50 ms 53 ms ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
    14 74 ms 72 ms 71 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
    15 59 ms 59 ms 151 ms ae-4-90.edge4.Dallas3.Level3.net [4.69.145.205]

    16 65 ms 63 ms 63 ms THE-PLANET.edge4.Dallas3.Level3.net [4.59.32.30]

    17 63 ms 64 ms 65 ms te9-2.dsr02.dllstx3.theplanet.com [70.87.253.30]

    18 * * * Request timed out.
    19 65 ms 66 ms 64 ms te1-2.car06.dllstx6.theplanet.com [70.87.254.182
    ]
    20 62 ms 62 ms 60 ms 52.cc.354a.static.theplanet.com [74.53.204.82]

    Trace complete.


    Hope this helps.
     

  • I really only need to see tracert's that show a ping go from say 60ms to 150/200ms and up those will help us find the bad router. the ones that show as **** timed out are fine as long as the next hop is ok.
     


  • Tracing route to fsk405.com [74.53.204.82]
    over a maximum of 30 hops:

    1 10 ms 9 ms 9 ms user-387c781.cable.mindspring.com [208.118.29.1]

    2 11 ms 9 ms 12 ms gig-6-0-5-41.orldflaabv-rtr1.cfl.rr.com [24.95.2
    33.213]
    3 24 ms 9 ms 9 ms 24.95.228.28
    4 10 ms 9 ms 9 ms 77.228.95.24.cfl.res.rr.com [24.95.228.77]
    5 28 ms 19 ms 18 ms ge-1-3-0.cr1.atl20.tbone.rr.com [66.109.6.104]
    6 22 ms 19 ms 47 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
    7 106 ms 210 ms 243 ms TenGigabitEthernet9-2.ar1.ATL2.gblx.net [64.212.
    108.69]
    8 40 ms 38 ms 39 ms The-Planet.TenGigabitEthernet2-3.ar2.HOU1.gblx.n
    et [64.214.196.58]
    9 38 ms 38 ms 38 ms et5-4.ibr03.dllstx3.theplanet.com [70.87.253.49]

    10 40 ms 40 ms 38 ms 1a.ff.5746.static.theplanet.com [70.87.255.26]
    11 39 ms 38 ms 41 ms 82.fd.5746.static.theplanet.com [70.87.253.130]

    12 39 ms 50 ms 38 ms te1-1.car06.dllstx6.theplanet.com [70.87.254.178
    ]
    13 37 ms 38 ms 38 ms 52.cc.354a.static.theplanet.com [74.53.204.82]

    Trace complete.

    hope this helps
     

  • I did receive a request time out at hop 15 . Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>tracert 74.53.204.82 Tracing route to 52.cc.354a.static.theplanet.com [74.53.204.82] over a maximum of 30 hops: 1 3 ms <1 ms <1 ms READYSHARE [192.168.1.1] 2 1 ms 1 ms <1 ms 69.62.234.129 3 4 ms 3 ms 2 ms 172.22.11.137 4 1 ms 1 ms 1 ms 172.21.2.21 5 1 ms 1 ms 1 ms 172.21.0.250 6 2 ms 1 ms 1 ms 245.98-30-64.ftth.swbr.surewest.net [64.30.98.24 5] 7 2 ms 2 ms 1 ms te-4-1.car1.Sacramento1.Level3.net [4.53.200.9] 8 2 ms 2 ms 2 ms ae-11-11.car2.Sacramento1.Level3.net [4.69.132.1 50] 9 11 ms 4 ms 13 ms ae-4-4.ebr2.SanJose1.Level3.net [4.69.132.158] 10 17 ms 17 ms 18 ms ae-2-2.ebr2.LosAngeles1.Level3.net [4.69.132.14] 11 62 ms 54 ms 54 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78] 12 50 ms 49 ms 49 ms ae-3-80.edge4.Dallas3.Level3.net [4.69.145.141] 13 49 ms 49 ms 49 ms THE-PLANET.edge4.Dallas3.Level3.net [4.59.32.30] 14 50 ms 49 ms 50 ms 2e.ff.5746.static.theplanet.com [70.87.255.46] 15 * * * Request timed out. 16 50 ms 51 ms 53 ms te1-2.car06.dllstx6.theplanet.com [70.87.254.182 ] 17 49 ms 49 ms 50 ms 52.cc.354a.static.theplanet.com [74.53.204.82] Trace complete. C:\Documents and Settings\Administrator>
     

  • First of all, no offense to anyone, but traceroute is a piss poor tool in the wrong hands. Generally because most people don't understand what they are looking at when they get the results. And the internet has changed since the inception of traceroute. Windows tracert is even worse at telling you anything useful except that there is a route between you and another host.

    For a long winded discussion that does a good job at explaining traceroute, read this => http://www.exit109.com/~jeremy/news/providers/traceroute.html

    Earl and I tried to explain a bit the other night, but it doesn't take long to go over ppl's heads.

    1) Routes are asymentrical,
    2) Splats (*) are not a sign of problems,
    3) RTT's are not cumulative,
    4) ICMP is likely to be given low priority.

    1. The route to a destination is likely not the same route back.

    2. A hop somewhere in the middle of the route may ignore some OR all of the echo requests. This just means they don't want to reply because they are TOO busy for you or have been configure to never reply to icmp echo reqests.

    3. Traceroute uses an incrementing TTL to discover the hops and once discovered, it sends out, generally, three icmp echo requests to that hop. This is why you see the host IP followed by three (???.?? ms) RTT numbers. These numbers are the amount time it took to get the echo requests to and the replies back from THAT host. Hence the name round Trip Time.

    4. Huh? Well ... have you ever noticed a host (hop) in the middle of the path have higher RTT's than one after it? It could be that the host was busy and didn't have time to deal with your petty echo request at that moment. Deal with it. A high RTT on anybody except the destination can generally be ignored. The destination might even give you a high RTT since it can also determine that your petty echo request is not near as important as getting Relux's next UrT frame out to him.

    Lastly, for those of you running *nix's, get to know mtr. AFAIK, it is included in the core of most/all distributions? For Windows freaks there is a port called WinMTR and another tool called PathPing. FSK405|Earl mentioned another, but I forgot the name.

    http://winmtr.sourceforge.net/
    http://en.wikipedia.org/wiki/PathPing
    http://technet.microsoft.com/en-us/library/cc958876.aspx

    What you want to do is run a tool like mtr or WinMTR while you are playing and "catch" the hiccup when it happens. Multiple monitors help. What you will find is somebody along that path started dropping or having higher pings than before while your game is vomiting. All it takes is one host in the middle to give up on you. When this occurs, you should notice that the one host and everybody following went screwy.

    I must emphasize that due to asymmetrical routing, you might not notice anything yet your game is hosing up. This would be because the route back to you is having trouble while the route to the server is not.

    -R
     

  • is it really that hard to only post shit that shows your ping higher 100ms or more than it normally is.. seriously.. you all have filled this thread with unnecessary posts.. is it that hard to know when your ping has more than doubled for an extended period? do we really need to break everything down word for word? ping by ping? ok if your normal ping is 50 and tomorrow its 60 I dont give a fuck. if your normal ping is 100 and tomorrow its 110 i still don't give a shit. now if your 50ms ping jumps up to 200 than fucking post it. if your 100 ping jumps up to 200ms than post it. need more fucking clarity? does anyone want to post what ping means, what tomorrow means? what ms mean? what fuck you means.. really.. I hope the others with trouble ticket access resume work on this because i've given up all hope for fixing the issue.
     

  • I was getting packet loss today and I was able to get a good screenshot from mtr showing packet loss from hop 8 on. The game and TS (eventually disconnected) became completely unresponsive at the moment this screenshot was taken. Pretty sure that means 100% loss.


     

Moderator(s): FSKADMIN, FSK405 Earl, Frog, DankRider, Fokker, LadyHellfire*, Reflux This topic is now closed