143 replies to this topic

[Viz0r]

what's up with the last switch? on the majority they time out at the last switch....

[Squee]

Tracing route to 83.142.229.110 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms linux4.brighton.climax.co.uk [10.0.0.4]
2 <1 ms <1 ms <1 ms shaper.brighton.climaxgroup.com [193.129.86.189]
3 2 ms 2 ms 2 ms router.brighton.climaxgroup.com [193.129.86.190]
4 2 ms 2 ms 2 ms uuk200361-gw.customer.uk.uu.net [158.43.12.66]
5 10 ms 10 ms 10 ms ser1-1-0.cr3.man3.gbb.uk.uu.net [158.43.241.73]
6 10 ms 10 ms 10 ms pos0-2.cr1.man3.gbb.uk.uu.net [158.43.162.74]
7 14 ms 14 ms 14 ms POS7-0.CR1.LND8.ALTER.net [158.43.254.58]
8 14 ms 14 ms 14 ms srp1-0.br1.lnd8.gbb.uk.uu.net [158.43.189.1]
9 15 ms 14 ms 14 ms linx.lon20.ip.tiscali.net [195.66.226.32]
10 15 ms 14 ms 14 ms ge0-1.lon.rapidswitch.ip.tiscali.net [213.200.78.194]
11 * * * Request timed out.
12 16 ms 15 ms 15 ms 83.142.229.110

Trace complete.

[SellersUK]

can some one tel me how to do a tracert plz

[tef]

Have reported this to our datacenter to see if they can shed any light.

Since I never play, I don't give a f00k what we have on there
But I would suggest ditching all except manny to see if that improves things.
It may be that a steam update and/or a mod update has f00ked things a bit.

[Darunia]

haha dave. seriously though. what does it mean? and sellers, to do a tracert, go to start menu, run, and type in cmd. then in the window that opens, type tracert cs.biatch-clan.co.uk

hope that helps

[tef]

* * * Request timed out.

This bit is normal it seems - the DC have a firewall and it does not respond to pings full stop.

Shipppyyyyyyy - where are ya m8?

[tef]

BTW, there are reports on the HLDS lists like this:

Ever since the last update, we have had admins and players complaining
of some new type of lag.

A player seems to be walking, but gets stuck in a positional time warp.
They are in this position for some
10 to 30 seconds. They cannot move in any position, and sometimes they
are warped backwards to a previous position.

I experienced it on 3 sessions so far, running CSS. Looking at netgraph,
shows no network lag or spikes.

and

In addition to the lag problems that have already been described, there
seems to be a lot of complaints of high choke and loss on servers that
were previously pretty much choke and loss free.  Also, and I can't say
if this is wide spread or not, but I've noticed players, myself
included, getting stuck in/on landscape quite a lot too.

so it could "simply" be a fcuk up (again) by Valve :/

[Snowman]

Yeah I keep getting stuck on parts of landscape. On malitia, twice now near a cable reel when crounching.

[Darunia]

Yeh, I sometimes get stuck, and I also regularly jump back and forth, as described in that quote of tef's. Kinda annoying when your just about to deal some pain...

[TheShipsMast]

* * * Request timed out.

all that means is the router is not configured to pass on ICMP requests.. stops DOS attacks

[TheShipsMast]

I will do some reading when I can be arsed..

I just got back from Les Arc.. 6 feet of powder.. yummy!

[tef]

What about linux attacks?

Any thoughts on why everyone is lagging like a mofo?
Or why snowy likes being near laid cables?

[tef]

Ah, just saw ur last post so ignore my 2nd question

Did u see a bunch of kn0bs arsing about on the slopes?
Some "people" from work were there the weekend just gone too.
OR were u too busy arsing about urself?

[tef]

Right, can one of you with problems (on the server, I don't mean in ur life generally ), who is experiencing said problems now, please run ping plotter:
http://www.pingplotter.com/download.html

Set the interval at 0.1s, and number of samples to include in the report as 10,000. Then run it for 20 minutes from your computer to the server with no other applications running on your computer.

Then send me the resulting report.

[TheShipsMast]

I will take a look at the server too.. god forbid it might need a reboot!!!

The slopes were empty.. only 57% occupancy in the hotels.. was wikid..

[Snowman]

KNIFE MUGGING, BETTING, BOUNTY and QUAKE sounds disabled on server to see if it helps the lag problem people seem to be getting. Please report back if it makes a difference.

Left Eventscripts running as it runs RATES checking.

[Snowman]

Well that hasnt made much difference, we just had a few lag spikes again

[TheShipsMast]

checked the server out, no memory leaks, restarted the srcds processess, everything looks clean..

traceroutes from the servers to www.google.co.uk and www.bbc.co.uk are VERY quick..

traceroute: Warning: www.google.co.uk has multiple addresses; using 216.239.59.147
traceroute to www.l.google.com (216.239.59.147), 30 hops max, 38 byte packets
1 ge-edge.kit.sov.lon.rapidswitch.com (83.142.229.1) 0.403 ms 2.692 ms 0.486 ms
2 ge-4-1_2.cat2.sov.lon.rapidswitch.com (83.142.224.2) 0.359 ms 0.316 ms 0.233 ms
3 ae0-209.lon22.ip.tiscali.net (213.200.78.193) 0.606 ms 0.477 ms 0.485 ms
4 ge-7-1.core2.london1.level3.net (213.200.77.130) 0.705 ms 0.724 ms 0.618 ms
5 ae-0-54.gar2.london1.level3.net (212.187.131.154) 0.855 ms ae-0-55.gar1.london1.level3.net (212.187.131.169) 1.223 ms ae-0-54.gar2.london1.level3.net (212.187.131.154) 1.108 ms
6 so-6-0.metro2-londencyh00.london1.level3.net (212.113.3.26) 0.951 ms 0.894 ms so-2-0.metro2-londencyh00.london1.level3.net (212.113.0.117) 0.860 ms
7 195.50.116.70 (195.50.116.70) 1.087 ms 0.948 ms 1.108 ms
8 72.14.238.240 (72.14.238.240) 1.105 ms 1.164 ms 1.107 ms
9 216.239.49.254 (216.239.49.254) 22.950 ms 22.351 ms 27.690 ms
10 216.239.48.158 (216.239.48.158) 21.701 ms 21.566 ms 216.239.49.114 (216.239.49.114) 23.479 ms
11 216.239.59.147 (216.239.59.147) 21.690 ms 22.045 ms 22.083 ms
[root@mofo steam]# traceroute www.bbc.co.uk
traceroute to www.bbc.net.uk (212.58.224.82), 30 hops max, 38 byte packets
1 ge-edge.kit.sov.lon.rapidswitch.com (83.142.229.1) 0.422 ms 2.177 ms 0.360 ms
2 ge-4-1_2.cat1.sov.lon.rapidswitch.com (83.142.224.1) 0.354 ms 0.350 ms 0.238 ms
3 rt-lonap-a.thdo.bbc.co.uk (193.203.5.90) 13.993 ms 0.821 ms 0.606 ms
4 212.58.238.153 (212.58.238.153) 0.407 ms 0.455 ms 0.359 ms
5 www31.thdo.bbc.co.uk (212.58.224.82) 0.864 ms 0.512 ms 0.687 ms


this stinks of application net code rather than a specific network issue..

[[-=63rd=-]chester]

could it not be the fact that that old things do tend to die....
and get ill before they die????

[tef]

Like I said too, if one of u laggy cnuts could run pingplotter then we can determine if there are any connectivity problems...