Dead Men Walking

Old Server Admin Section => dMw Charlie Company - Secure Channel => Archived Feb 09 => Yabba Yabba => Topic started by: Dr Sadako on March 15, 2004, 07:53:04 PM

Title: Not playing at all
Post by: Dr Sadako on March 15, 2004, 07:53:04 PM
I will not be able to play on any of our servers until the new ping issue is resolved. Atm I ping 300+ on average to all our servers. Other servers I have in my serverlist are between 30 and 60 in latency.


QuoteC:\>ping //www.deadmen.co.uk

Pinging //www.deadmen.co.uk [193.110.88.19] with 32 bytes of data:

Reply from 193.110.88.19: bytes=32 time=277ms TTL=115
Reply from 193.110.88.19: bytes=32 time=281ms TTL=115
Reply from 193.110.88.19: bytes=32 time=274ms TTL=115
Reply from 193.110.88.19: bytes=32 time=262ms TTL=115

and

QuoteC:\>tracert 193.110.88.19

Tracing route to 193.110.88.19 over a maximum of 30 hops

 1  <1 ms  <1 ms  <1 ms 192.168.2.100
 2   5 ms   5 ms   7 ms 82.182.99.1
 3   5 ms   5 ms   5 ms cr1-gig1-3.djakneg16.mlm.bostream.net [82.182.4.13]
 4  15 ms  15 ms  15 ms cr2-gig1-1.torgg4.sth.bostream.net [82.182.0.17]
 5  14 ms  14 ms  15 ms cr1-gig1-16.torgg4.sth.bostream.net [82.182.0.9]
 6  15 ms  14 ms  15 ms ge-3-0-0.ar1.ARN1.gblx.net [64.213.23.153]
 7  26 ms  25 ms  26 ms pos9-0-2488M.cr1.HAM1.gblx.net [67.17.72.234]
 8  125 ms  125 ms  124 ms pos1-0-2488M.cr2.WDC2.gblx.net [67.17.71.5]
 9  124 ms  124 ms  124 ms so5-1-0-2488M.ar1.DCA3.gblx.net [67.17.68.37]
 10  124 ms  123 ms  126 ms p1-3.pr01.iad01.atlas.psi.net [154.54.10.117]
 11  127 ms  125 ms  125 ms p1-2.core02.dca01.atlas.cogentco.com[154.54.2.253]
 12  131 ms  131 ms  133 ms p6-0.core01.jfk02.atlas.cogentco.com [66.28.4.82]
 13  131 ms  131 ms  131 ms p15-0.core02.jfk02.atlas.cogentco.com[66.28.4.14]
 14  208 ms  208 ms  207 ms p3-0.core01.lcy01.atlas.cogentco.com[130.117.1.17]
 15  133 ms  131 ms  131 ms viatel.demarc.cogentco.com [130.117.1.30]
 16  130 ms  130 ms  131 ms pos4-2.core-01.tlh.uk.viatel.net [135.196.65.125]
 17  130 ms  131 ms  132 ms pos0-1-0.acc-001.tlh.uk.viatel.net [135.196.65.21]
 18  287 ms  288 ms  292 ms fa2-0-b1-thn.lon.caladan.net.uk [80.71.4.13]
 19  309 ms  309 ms  314 ms cwgway1.crosswired.co.uk [80.71.4.10]
 20  317 ms   *   315 ms 193.110.88.19

Trace complete.

I don't know if Stryker or Dogger can do anything at Crosswired to help this problem??
Title: Not playing at all
Post by: Benny on March 15, 2004, 08:04:51 PM
Trace to another UK server please?
Title: Not playing at all
Post by: TeaLeaf on March 15, 2004, 08:45:11 PM
Tonight we all had exceptionally bad connections.  Pings looked fine, no choke, no loss, just constant 0.5 second lags and warps throughout the  match.  And no it wasn't steam downloading anything.....

TL.
Title: Not playing at all
Post by: Anonymous on March 15, 2004, 08:51:11 PM
I reckon your problems start at hop 18 which is outwith Stryker and DMs remit although they may be able to question the provider to see if they can do anything. Hop 14 is a bit loaded too.
Title: Not playing at all
Post by: FATAL on March 15, 2004, 08:51:24 PM
i had probs and it was updating, check the moniter ,thats wot mine was.
Title: Not playing at all
Post by: Anonymous on March 15, 2004, 08:52:25 PM
QuoteOriginally posted by FATAL@Mar 15 2004, 08:51 PM
i had probs and it was updating, check the moniter ,thats wot mine was.
But with Sadako's bandwidth a full steam reinstall only takes 14 seconds :D
Title: Not playing at all
Post by: Dr Sadako on March 15, 2004, 09:07:53 PM
QuoteOriginally posted by Benny@Mar 15 2004, 09:04 PM
Trace to another UK server please?

This is to CoFR25

QuoteC:\>ping 82.136.20.11

Pinging 82.136.20.11 with 32 bytes of data:

Reply from 82.136.20.11: bytes=32 time=48ms TTL=113
Reply from 82.136.20.11: bytes=32 time=51ms TTL=113
Reply from 82.136.20.11: bytes=32 time=50ms TTL=113
Reply from 82.136.20.11: bytes=32 time=49ms TTL=113

and


QuoteC:\>tracert 82.136.20.11

Tracing route to neo.sov.inetgaming.co.uk [82.136.20.11]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.2.100
 2   5 ms   6 ms   6 ms 82.182.99.1
 3   5 ms   5 ms   5 ms cr1-gig1-3.djakneg16.mlm.bostream.net [82.182.4.13]
 4  15 ms  15 ms  15 ms cr2-gig1-1.torgg4.sth.bostream.net [82.182.0.17]
 5  14 ms  15 ms  14 ms cr1-gig1-16.torgg4.sth.bostream.net [82.182.0.9]
 6  16 ms  16 ms  17 ms ge-3-0-0.ar1.ARN1.gblx.net [64.213.23.153]
 7  15 ms  14 ms  15 ms s-b3-pos15-2.telia.net [213.248.101.37]
 8  15 ms  15 ms  15 ms s-bb2-pos7-1-0.telia.net [213.248.66.9]
 9  24 ms  24 ms  23 ms kbn-bb2-pos0-0-0.telia.net [213.248.65.29]
 10  36 ms  36 ms  36 ms hbg-bb2-pos5-0-0.telia.net [213.248.65.125]
 11  46 ms  47 ms  46 ms adm-bb2-pos7-0-0.telia.net [213.248.65.161]
 12  46 ms  46 ms  46 ms ldn-bb2-pos7-2-0.telia.net [213.248.65.157]
 13  45 ms  45 ms  46 ms ldn-b1-pos5-0.telia.net [213.248.74.14]
 14  47 ms  48 ms  47 ms claranet-01638-ldn-b1.c.telia.net [213.248.75.74]
 15  49 ms  48 ms  46 ms t40-cr1-ge-5-0.router.uk.clara.net [195.8.86.149]
 16  48 ms  46 ms  48 ms fe-4-0-1119-redbus-queequeg.router.clara.net [195.8.86.118]
 17  49 ms  48 ms  48 ms fe-1-0-hex-niobium.burstfire.net.uk [217.158.78.6]
 18  80 ms  48 ms  47 ms fe-1-1-700-dubnium.as25492.net [82.136.0.199]
 19  48 ms  47 ms  47 ms neo.sov.inetgaming.co.uk [82.136.20.11]
Title: Not playing at all
Post by: Anonymous on March 15, 2004, 09:35:39 PM
In view of your second post I would say that your problems start at hop 8 of your first trace. That is where your routing starts to jump to over 100ms. Your traces start to take different paths at hop 7 and then your trace to Meathook starts to hit probs as it seems that the routers from there on are more heavily loaded than on the other route.
Title: Not playing at all
Post by: Stryker on March 16, 2004, 09:51:33 AM
It does seem you hit problems half way to crosswired.  As a result I'm going to make the route via caladan less appealing for the time being to see if that forces your traffic to take a different path.

I'm afraid it is pretty difficult to influence the routing decissions of remote sites, but please let me know how it goes on the hook for you from today onwards.

Right I'm off to make some changes :-)
Title: Not playing at all
Post by: Dr Sadako on March 16, 2004, 10:09:38 AM
QuoteOriginally posted by Stryker@Mar 16 2004, 10:51 AM
It does seem you hit problems half way to crosswired. As a result I'm going to make the route via caladan less appealing for the time being to see if that forces your traffic to take a different path.

I'm afraid it is pretty difficult to influence the routing decissions of remote sites, but please let me know how it goes on the hook for you from today onwards.

Right I'm off to make some changes :-)
Cheers! I am most grateful. This is the latest tracert I have made. It is better than before but I am nowhere near 60 latency. Floating at 150 atm.

QuoteC:\>tracert 193.110.88.20

Tracing route to homer.deadmen.co.uk [193.110.88.20]
over a maximum of 30 hops:

 1   1 ms  <1 ms  <1 ms 192.168.2.100
 2   5 ms   5 ms   5 ms 82.182.99.1
 3   5 ms   5 ms   5 ms cr1-gig1-3.djakneg16.mlm.bostream.net [82.182.4.13]
 4  14 ms  14 ms  13 ms cr2-gig1-1.torgg4.sth.bostream.net [82.182.0.17]
 5  14 ms  14 ms  14 ms cr1-gig1-16.torgg4.sth.bostream.net [82.182.0.9]
 6  14 ms  14 ms  14 ms ge-3-0-0.ar1.ARN1.gblx.net [64.213.23.153]
 7  25 ms  25 ms  25 ms pos9-0-2488M.cr1.HAM1.gblx.net [67.17.72.234]
 8  122 ms  123 ms  123 ms pos1-0-2488M.cr2.WDC2.gblx.net [67.17.71.5]
 9  124 ms  123 ms  124 ms so5-1-0-2488M.ar1.DCA3.gblx.net [67.17.68.37]
 10  124 ms  124 ms  124 ms p1-3.pr01.iad01.atlas.psi.net [154.54.10.117]
 11  124 ms  125 ms  125 ms p1-1.core02.dca01.atlas.cogentco.com [154.54.1.189]
 12  130 ms  130 ms  131 ms p6-0.core01.jfk02.atlas.cogentco.com [66.28.4.82]
 13  131 ms  131 ms  130 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.14]
 14  208 ms  207 ms  207 ms p3-0.core01.lcy01.atlas.cogentco.com [130.117.1.17]
 15  130 ms  131 ms  132 ms viatel.demarc.cogentco.com [130.117.1.30]
 16  130 ms  130 ms  130 ms pos4-2.core-01.tlh.uk.viatel.net [135.196.65.125]
 17  130 ms  130 ms  130 ms pos0-1-0.acc-001.tlh.uk.viatel.net [135.196.65.21]
 18  130 ms  131 ms  130 ms fa2-0-b1-thn.lon.caladan.net.uk [80.71.4.13]
 19  145 ms  139 ms  175 ms cwgway1.crosswired.co.uk [80.71.4.10]
 20  142 ms   *   145 ms homer.deadmen.co.uk [193.110.88.20]

Trace complete.

I'll check again later when you have made the changes. Thanks again.
Title: Not playing at all
Post by: Dr Sadako on March 16, 2004, 10:39:58 AM
Quote
C:\>tracert 193.110.88.20

Tracing route to homer.deadmen.co.uk [193.110.88.20]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.2.100
 2   5 ms   5 ms   5 ms 82.182.99.1
 3   5 ms   5 ms   5 ms cr1-gig1-3.djakneg16.mlm.bostream.net [82.182.4.13]
 4  14 ms  14 ms  14 ms cr2-gig1-1.torgg4.sth.bostream.net [82.182.0.17]
 5  14 ms  14 ms  14 ms cr1-gig1-16.torgg4.sth.bostream.net [82.182.0.9]
 6  14 ms  14 ms  14 ms ge-3-0-0.ar1.ARN1.gblx.net [64.213.23.153]
 7  25 ms  26 ms  26 ms pos9-0-2488M.cr1.HAM1.gblx.net [67.17.72.234]
 8  123 ms  122 ms  123 ms pos1-0-2488M.cr2.WDC2.gblx.net [67.17.71.5]
 9  123 ms  123 ms  124 ms so5-1-0-2488M.ar1.DCA3.gblx.net [67.17.68.37]
 10  124 ms  123 ms  123 ms p1-3.pr01.iad01.atlas.psi.net [154.54.10.117]
 11  125 ms  124 ms  125 ms p1-1.core02.dca01.atlas.cogentco.com [154.54.1.189]
 12  130 ms  130 ms  130 ms p6-0.core01.jfk02.atlas.cogentco.com [66.28.4.82]
 13  130 ms  130 ms  130 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.14]
 14  207 ms  207 ms  207 ms p3-0.core01.lcy01.atlas.cogentco.com [130.117.1.17]
 15  130 ms  130 ms  130 ms viatel.demarc.cogentco.com [130.117.1.30]
 16  129 ms  130 ms  130 ms pos4-2.core-01.tlh.uk.viatel.net [135.196.65.125]
 17  130 ms  130 ms  131 ms pos0-1-0.acc-001.tlh.uk.viatel.net [135.196.65.21]
18  185 ms  287 ms  315 ms fa2-0-b1-thn.lon.caladan.net.uk [80.71.4.13]
 19  141 ms  140 ms  139 ms cwrt1.crosswired.co.uk [193.110.88.1]
 20  139 ms  140 ms  140 ms homer.deadmen.co.uk [193.110.88.20]


Seems like Caladan has some issues.
Title: Not playing at all
Post by: Anonymous on March 16, 2004, 10:42:01 AM
Yes but your problems start in gblx ( step 7 or 8 )
Title: Not playing at all
Post by: Dr Sadako on March 20, 2004, 08:51:00 PM
Whatever you did Stryker it worked!!!

QuoteC:\>tracert //www.deadmen.co.uk

Tracing route to //www.deadmen.co.uk [193.110.88.19]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.2.100
 2   5 ms   5 ms   6 ms 82.182.99.1
 3   5 ms   5 ms   5 ms cr1-gig1-3.djakneg16.mlm.bostream.net [82.182.4.13]
 4  14 ms  14 ms  13 ms cr2-gig1-1.torgg4.sth.bostream.net [82.182.0.17]
 5  14 ms  13 ms  14 ms cr1-gig1-16.torgg4.sth.bostream.net [82.182.0.9]
 6  14 ms  14 ms  14 ms ge-3-0-0.ar1.ARN1.gblx.net [64.213.23.153]
 7  25 ms  25 ms  25 ms pos9-0-2488M.cr1.HAM1.gblx.net [67.17.72.234]
 8  34 ms  34 ms  34 ms pos10-0-2488M.cr1.FRA2.gblx.net [67.17.92.213]
 9  34 ms  34 ms  34 ms so3-0-0-2488M.ar2.FRA3.gblx.net [67.17.65.82]
 10  34 ms  34 ms  34 ms de-cix.fra.above.net [80.81.192.226]
 11  51 ms  51 ms  51 ms so-0-1-0.cr1.fra1.de.mfnx.net [216.200.116.213]
 12  51 ms  51 ms  51 ms pos1-0.mpr1.fra2.de.above.net [216.200.115.254]
 13  51 ms  51 ms  51 ms so-4-2-0.cr1.lhr3.uk.above.net [64.125.29.77]
 14  51 ms  51 ms  50 ms pos1-0.mpr1.lhr1.uk.above.net [208.184.231.173]
 15  51 ms  51 ms  51 ms avensys-mfn.lhr1.mfnx.net [208.185.188.214]
 16  51 ms  50 ms  51 ms fa0-1.lon7.as8553.net [193.111.29.22]
 17  51 ms  51 ms  51 ms fa1-0.lon6.as8553.net [195.10.255.194]
 18  55 ms  54 ms  55 ms s6-1.bris1.as8553.net [195.10.255.134]
 19  56 ms  55 ms  55 ms fa0-0-2.bris2.as8553.net [195.10.254.82]
 20  59 ms  59 ms  60 ms s6-0.man1.as8553.net [195.10.255.14]
 21  61 ms  60 ms  62 ms cwrt2.crosswired.co.uk [193.110.88.2]
 22  64 ms  76 ms  68 ms 193.110.88.19

Trace complete.
Title: Not playing at all
Post by: JonnyAppleSeed on March 20, 2004, 09:38:18 PM
Stryker our cunning plan to keep him from killing me failed  :P
Title: Not playing at all
Post by: Aga on March 20, 2004, 09:48:28 PM
It looks like a 26meg connection just isn't fast enough. Have you tried dial up?

I'm not being much help am I.

I'll get me coat.
Title: Not playing at all
Post by: Stryker on March 22, 2004, 10:46:54 AM
Caladan were having problems with one of their upstreams.... seems said upstreams connectivity was far from peachy.