Text only | Text with Images

Dead Men Walking

Dead Men Walking - Bricks 'n Mortar => Our Server => Topic started by: albert on December 12, 2002, 08:18:52 PM

Title: Current lag, choke and loss issues
Post by: albert on December 12, 2002, 08:18:52 PM
Hi All,
I've been suffering choke of 18 and loss of 80 on MH last night and tonight. So here are my trace routes to homer.deadmen.co.uk. The ping shoots through the roof on crosswired:
C:Documents and SettingsAdministrator>tracert homer.deadmen.co.uk

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

  1     2 ms     1 ms     1 ms  SpeedTouch.lan [10.0.0.138]
  2    18 ms    16 ms    15 ms  lo1-bba1.th.eclipse.net.uk [212.104.130.141]
  3    28 ms    21 ms    16 ms  fe6-core2.th.eclipse.net.uk [212.104.128.101]
  4    18 ms    16 ms    18 ms  fe4-core1.th.eclipse.net.uk [212.104.128.225]
  5    18 ms    19 ms    17 ms  linx1.lon1.as8553.net [195.66.224.126]
  6    19 ms    17 ms    19 ms  e2-0.lon6.as8553.net [195.10.255.194]
  7    26 ms    21 ms    21 ms  s6-1.bris1.as8553.net [195.10.255.134]
  8    23 ms    22 ms    21 ms  fa0-0-2.bris2.as8553.net [195.10.254.82]
  9    26 ms    26 ms    25 ms  s6-0.man1.as8553.net [195.10.255.14]
 10    31 ms    27 ms    29 ms  cwgtway2.crosswired.co.uk [195.10.230.11]
 11   215 ms   181 ms   143 ms  homer.deadmen.co.uk [193.110.88.20]

Trace complete.

C:Documents and SettingsAdministrator>tracert homer.deadmen.co.uk

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

  1     2 ms     1 ms     1 ms  SpeedTouch.lan [10.0.0.138]
  2    18 ms    17 ms    16 ms  lo1-bba1.th.eclipse.net.uk [212.104.130.141]
  3    18 ms    18 ms    18 ms  fe6-core2.th.eclipse.net.uk [212.104.128.101]
  4    19 ms    17 ms    19 ms  fe4-core1.th.eclipse.net.uk [212.104.128.225]
  5    18 ms    18 ms    19 ms  linx1.lon1.as8553.net [195.66.224.126]
  6    21 ms    18 ms    18 ms  e2-0.lon6.as8553.net [195.10.255.194]
  7    22 ms    21 ms    21 ms  s6-1.bris1.as8553.net [195.10.255.134]
  8   139 ms   226 ms   211 ms  fa0-0-2.bris2.as8553.net [195.10.254.82]
  9    26 ms    26 ms    32 ms  s6-0.man1.as8553.net [195.10.255.14]
 10    29 ms    28 ms    28 ms  cwgtway2.crosswired.co.uk [195.10.230.11]
 11   117 ms   189 ms   241 ms  homer.deadmen.co.uk [193.110.88.20]

Trace complete.

Stryker over to you please  :D
Title: Current lag, choke and loss issues
Post by: albert on December 12, 2002, 08:24:53 PM
Weird, I did a reboot and also rebooted my router and:
C:Documents and SettingsAdministrator>tracert homer.deadmen.co.uk

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

  1     1 ms     1 ms     1 ms  SpeedTouch.lan [10.0.0.138]
  2    17 ms    17 ms    16 ms  lo1-bba1.th.eclipse.net.uk [212.104.130.141]
  3    18 ms    19 ms    17 ms  fe6-core2.th.eclipse.net.uk [212.104.128.101]
  4    18 ms    17 ms    16 ms  fe4-core1.th.eclipse.net.uk [212.104.128.225]
  5    18 ms    18 ms    17 ms  linx1.lon1.as8553.net [195.66.224.126]
  6    18 ms    19 ms    19 ms  e2-0.lon6.as8553.net [195.10.255.194]
  7    22 ms    22 ms    22 ms  s6-1.bris1.as8553.net [195.10.255.134]
  8    26 ms    20 ms    22 ms  fa0-0-2.bris2.as8553.net [195.10.254.82]
  9    27 ms    28 ms    26 ms  s6-0.man1.as8553.net [195.10.255.14]
 10    27 ms    27 ms    27 ms  cwgtway2.crosswired.co.uk [195.10.230.11]
 11    27 ms    31 ms    28 ms  homer.deadmen.co.uk [193.110.88.20]

Trace complete.

C:Documents and SettingsAdministrator>tracert homer.deadmen.co.uk

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

  1     1 ms     1 ms     1 ms  SpeedTouch.lan [10.0.0.138]
  2    17 ms    17 ms    17 ms  lo1-bba1.th.eclipse.net.uk [212.104.130.141]
  3    17 ms    17 ms    17 ms  fe6-core2.th.eclipse.net.uk [212.104.128.101]
  4    18 ms    17 ms    16 ms  fe4-core1.th.eclipse.net.uk [212.104.128.225]
  5    22 ms    18 ms    19 ms  linx1.lon1.as8553.net [195.66.224.126]
  6    29 ms    18 ms    19 ms  e2-0.lon6.as8553.net [195.10.255.194]
  7    20 ms    21 ms    22 ms  s6-1.bris1.as8553.net [195.10.255.134]
  8    21 ms    23 ms    21 ms  fa0-0-2.bris2.as8553.net [195.10.254.82]
  9   203 ms    49 ms    39 ms  s6-0.man1.as8553.net [195.10.255.14]
 10    28 ms    26 ms    28 ms  cwgtway2.crosswired.co.uk [195.10.230.11]
 11    27 ms    28 ms    26 ms  homer.deadmen.co.uk [193.110.88.20]

Trace complete.

C:Documents and SettingsAdministrator>

Something obviously cleared between 8:20pm and 8:25pm.
Title: Current lag, choke and loss issues
Post by: Gandalf on December 12, 2002, 10:24:48 PM
no probs this end. Has been fine all evening.

Amazing what a re-boot can do :)


(http://www.greenberry.co.uk/images/trace.jpg)
Title: Current lag, choke and loss issues
Post by: Stryker on December 13, 2002, 09:15:20 AM
FYI peeps, that "as8553.net" route is that of a provider that feeds us a top notch feed of bandwidth.

At the moment we are capped with that provider, however in JAN it will be openened up to wire speed!

Our other (once-was) primary bandwidth provider has gone to dogs somewhat just latley forcing me to prematurley route traffic with the as8553.net provider.... just this morning I had to route the remainder of Crosswired Ltd's traffic via as8553.net as t'other provider has had pings of 500-700ms over the past few days... (thats a ping of 500 in CS).

This means it *may* be a little bumpy in the lead up till Jan, however I figured it was better to keep the paying customers happy :-)
Title: Current lag, choke and loss issues
Post by: OldBloke on December 13, 2002, 10:02:49 AM
Stryker - you do what you gotta do.

I'm sure I speak for all when I say that we're extremely grateful for the service and support that Crosswired provides for our little community.
Title: Current lag, choke and loss issues
Post by: albert on December 13, 2002, 10:48:46 AM
QuoteStryker - you do what you gotta do.

I'm sure I speak for all when I say that we're extremely grateful for the service and support that Crosswired provides for our little community.


I agree too, thanks a lot Stryker, crosswired is king!

This little slowdown has only happened to me twice since I have played on MH. A far better performance than any other CS server I have played on, so round of applause to you mate.

It also played the old reboot trick on me, after rebooting everything was fine all night, but I got these traces earlier so there had to have been congestion (other than my nose) but for the problem record, I'll log it as a windows issue  :lol: .
Title: Current lag, choke and loss issues
Post by: Stryker on December 13, 2002, 11:13:26 AM
awww thanks guys.
Title: Current lag, choke and loss issues
Post by: Benny on December 13, 2002, 11:13:53 AM
Took me 2 reboots and a cable modem reset...'kin broadband is a pain in the ass, eh Tealeaf :wink:
Title: Current lag, choke and loss issues
Post by: Doorman on December 13, 2002, 11:18:12 AM
Yeah, broadband, who bloody needs it?  :D
Title: Current lag, choke and loss issues
Post by: albert on December 13, 2002, 11:40:49 AM
QuoteYeah, broadband, who bloody needs it? :D

He who is about to spash out on a new router  :lol:
Title: Current lag, choke and loss issues
Post by: TeaLeaf on December 13, 2002, 05:27:06 PM
QuoteTook me 2 reboots and a cable modem reset...'kin broadband is a pain in the ass, eh Tealeaf :wink:
I'll let you know when I 'get' the PITA  :x   Bloody no good dog gawn BT, mutter, mutter, mutter...  :evil:

TL.  8)

Still stuck on ISDN and still pinging at over 100ms  :(
Title: Current lag, choke and loss issues
Post by: Dr Sadako on December 13, 2002, 05:32:29 PM
Ping doesn't matter ...  :lol:

Sorry peeps, I couldn't resist it.  :wink:
Title: Current lag, choke and loss issues
Post by: JB on December 13, 2002, 05:40:20 PM
I totally agree Sadako my old chum buddy, look at Tutonic, he's able to keep up with the best low pingers on meathook, and same with me too when i was 56k and playing on meathook.
Title: Current lag, choke and loss issues
Post by: Dr Sadako on December 13, 2002, 05:44:39 PM
JB is right. I kicked major ass when playing UT (3 years ago) on 56k modem.

Ping isn't the issue. Choke and packet loss are the real bandits as far as I understand it. I leave this to the network dudes to clear up.

I saw a bumper sticker with the text "Ping doesn't matter!" not long ago. I hate that I didn't have my camera that time.
Title: Current lag, choke and loss issues
Post by: albert on December 13, 2002, 05:47:32 PM
Yep ping doesn't matter agreed. You'll notice that on NS next week  :D . Loss and inconsistant delay are the killers. Modem users can optimise their config to fully match their connection speed and be as near as damned as real time as broadband.
Title: Current lag, choke and loss issues
Post by: Stryker on December 15, 2002, 10:20:24 AM
right, noted for all those who say ping dont matter.  Next match you'll be getting your data stream by royal mail printed on perferated paper!!!! HA! :-)
Title: Current lag, choke and loss issues
Post by: Dr Sadako on December 15, 2002, 10:33:43 AM
Quoteright, noted for all those who say ping dont matter. Next match you'll be getting your data stream by royal mail printed on perferated paper!!!! HA! :-)

That is pretty darn good!  :D
Title: Current lag, choke and loss issues
Post by: albert on December 15, 2002, 11:24:05 AM
QuoteYep ping doesn't matter agreed. You'll notice that on NS next week :D . Loss and inconsistant delay are the killers. Modem users can optimise their config to fully match their connection speed and be as near as damned as real time as broadband.

When I say it don't matter I mean within reason. I mean 250ms + is a bit crap, but I've seen a number of players at the top of the kills board with silly high pings so they must know something that  we don't.
Title: Current lag, choke and loss issues
Post by: JB on December 15, 2002, 11:40:46 AM
QuoteWhen I say it don't matter I mean within reason. I mean 250ms + is a bit crap, but I've seen a number of players at the top of the kills board with silly high pings so they must know something that we don't.

Its just one simple download albert.   :wink:

Eermm..  Ask sadako..
Title: Current lag, choke and loss issues
Post by: albert on December 15, 2002, 04:54:27 PM
Quote
QuoteWhen I say it don't matter I mean within reason. I mean 250ms + is a bit crap, but I've seen a number of players at the top of the kills board with silly high pings so they must know something that we don't.

Its just one simple download albert.   :wink:

Eermm..  Ask sadako..[/b]

 :?:   :?
Title: Current lag, choke and loss issues
Post by: JB on December 15, 2002, 05:20:19 PM
'cough'  Bad download OGC joke, failed yet again.  

Can we move this thread to the Piss poor jokes section?   :?
Title: Current lag, choke and loss issues
Post by: Dr Sadako on December 15, 2002, 05:31:28 PM
Quote'cough' Bad download OGC joke, failed yet again.

Can we move this thread to the Piss poor jokes section?  :?

My aim isn't that good. Have I killed you too much lately or something?  :roll:
Title: Current lag, choke and loss issues
Post by: JB on December 15, 2002, 05:37:47 PM
Nah, it's nothing personal like that.  Just a one man crusade to see you ruined and living in the gutter.   :wink:

Have a nice day !!   :twisted:
Title: Current lag, choke and loss issues
Post by: TeaLeaf on December 15, 2002, 05:38:03 PM
Quote'cough' Bad download OGC joke, failed yet again.

Can we move this thread to the Piss poor jokes section?  :?
Nah, it's waaay too bad for that....  :lol:

TL.  8)
Title: Current lag, choke and loss issues
Post by: Anonymous on January 03, 2003, 08:04:39 PM
We seem to be having probs again. My ping in game is over 200 on 1 mb cable. Part of the prob is BlueBlunder but there is also latency issues on one of the routes into homer. Traceroute below:

TraceRoute - Friday, January 03, 2003 20:01:56
Generated by CyberKit Version 2.5
Copyright © 1996-2000 by Luc Neijens

Address: homer.deadmen.co.uk
Number of Packets: 1
Packet size: 1000
Trace Hop 1 through 30
Timeout: 5
Resolve Addresses: No
Don't Fragment: No

#1  (10.125.64.1): TTL Exceeded, ttl=255, 60 ms
#2  (62.31.64.33): TTL Exceeded, ttl=254, 60 ms
#3  (194.117.136.10): TTL Exceeded, ttl=248, 110 ms
#4  (194.117.136.6): TTL Exceeded, ttl=249, 100 ms
#5  (194.117.154.9): TTL Exceeded, ttl=251, 150 ms
#6  (195.66.224.126): TTL Exceeded, ttl=249, 140 ms
#7  (195.10.255.194): TTL Exceeded, ttl=249, 61 ms
#8  (195.10.255.134): TTL Exceeded, ttl=248, 110 ms
#9  (195.10.254.82): TTL Exceeded, ttl=247, 130 ms
#10  (195.10.255.14): TTL Exceeded, ttl=246, 210 ms
#11  (195.10.230.11): TTL Exceeded, ttl=245, 130 ms
#12  (193.110.88.20): Echo Reply, ttl=244, 60 ms

Statistics: Out 12, in 12, loss 0%, times (min/avg/max) 60/110/210 ms
 I'm gonna post the trace to BY too.
Text only | Text with Images