friday lag screens

[havoc]

here:

[havoc]

and here the explanation for computer-impaired people

you see, when the connection between server and somewhere is fucked up, beh and norma suffer, but havoc is ok. my route passes thru frankfurt for example. learn the computers, beh

[BEH]

We all pass through frankfurt right? server's located there, no?
anyhow, I did some fancy paint-cutting, but this was my lagometer on all maps today:

lag.gif

(5.37 KiB) Downloaded 7299 times

Btw, both Norma and me did a traceroute to dswp.de, he got 200+ lags on the last 3 servers which were all in germany he said. I had 1 big lag on the 3rd to last server, which is located.. somewhere. How am I supposed to know?
When we asked around on server, about 50 percent had these lags.
I'm guessing norma's was even worse than mine.
In-game it made every encounter with some other player a 5fps warp-show, only my pc had a stable 91fps today, for some weird reason.

But um ye, what you guys think?

Edit: did traceroute a couple more times. 193.159.226.13 is my problem. That's where I lose packets or the ping goes through the roof every now and then. Now, geniuses, how do I find out where that is?
Edit2: found some ip-tracking sites, but I didn't get any further than -somewhere- in germany.

[havoc]

here you go

whois 193.159.226.13
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.

% Information related to '193.159.224.0 - 193.159.227.255'

inetnum: 193.159.224.0 - 193.159.227.255
netname: DTAG-TRANSIT9
descr: Deutsche Telekom AG
descr: for IP-Transit
country: DE
admin-c: DTIP
tech-c: DTST
status: ASSIGNED PA
remarks: INFRA-AW
remarks: ******************************************************************
remarks: * Abuse Contact: http://www.t-com.de/ip-abuse in case of Spam, *
remarks: * Hack Attacks, Illegal Activity, Violation, Scans, Probes, etc. *
remarks: ******************************************************************
mnt-by: DTAG-NIC
source: RIPE # Filtered

person: DTAG Global IP-Addressing
address: Deutsche Telekom AG
address: D-90492 Nuernberg
address: Germany
phone: +49 180 5334332
fax-no: +49 6151 6809399
e-mail: abuse@t-online.de
nic-hdl: DTIP
mnt-by: DTAG-NIC
source: RIPE # Filtered

person: Security Team
address: Deutsche Telekom AG
address: Germany
phone: +49 180 5334332
fax-no: +49 6151 6809399
e-mail: abuse@t-online.de
nic-hdl: DTST
mnt-by: DTAG-NIC
source: RIPE # Filtered

% Information related to '193.158.0.0/15AS3320'

route: 193.158.0.0/15
descr: Deutsche Telekom AG, Internet service provider
origin: AS3320
member-of: AS3320:RS-PA-TELEKOM
mnt-by: DTAG-RR
source: RIPE # Filtered


p.s. what i mean is, when i connect to whatever in germany, my connection goes thru frankfurt first. dont know where the server is :)

p.p.s. can you please paste your traceroute result?

[felixmole]

My netgraph has always been normal to me on TDM (counting out my usual wi-fi lag spikes).

[wurst]

u mean this...
forum-gameserver-support/serwer-ci-t5023.html

[Crusher]

Looks like I go to a diferent route so I don't have any problem at all.

[wurst]

ye, theres peerings with all national providers (*excluding* deutsche telekom).
these routes seem to have been wrong for a while, dunno for that.

however, international packets come via de-cix.
its very powerful and stable cause it knows only participants, no customers.
the datacenter is kinda part of that decix, so never trouble with that international lines somehow by definition.

[BEH]

havoc: did the traceroute today, and all seems fine. That problem server disappeared out of the list entirely.
Amazing.. I'll never get these computers.

[havoc]

well its not that complicated really:

imagine the data traveling in chunks between your pc and the server.
now lets say every chunk is a little train in a huge railroad network, with every train knowing only its starting and destination stations. the stations between those two stations, lets call them routers, will try pick for your train the shortest reasonable route between them and the destination station, and send the train on its way further down the road. sometimes those stations get clogged tho, and trains get lost. usually the people who take care of those stations become aware at some point there is a problem, and do whatever is needed to get the situation under control.

thats pretty much it.

also there are some differences between udp (thats what q3 and some other apps use) and tcp (pretty much everything else these days) protocols. udp for example doesnt make sure the train sent has reached its final station, stuff like that.