Jeszcze jeden temat o lagach. New info.

[Ozon18]

Jak donosi tibianews.net lagi na serwerach sa spowodowane awaria routera we Frankfurcie:

Oryginalnie napisane przez Tibianews

The LAG explained (updated by TibiaNews)
Last days, the lag in Tibia for some European countries is a hot topic. Fad van Nal, server administrator of CipSoft, knows certainly what is going on. In this thread, he explains how you can see for yourself what the reason is for the lag, a little manual to investigate your own connection. In the same thread, Kanttar Don Doggy posts about a certain important router in Frankfurt, which is down and seems to be the reason of the bad connection for many people. On or own forum, Xadam gives technical details: The big lag is caused by the fact that one of the biggest routers in Europe just doesn't work. You can see proof here: http://www.internettrafficreport.com/details.htm:
r01-ffm1.treml-sturm.net Germany (Frankfurt) 100% packet loss.

Tłumaczenie: Problem lagów wyjaśniony!


Ostatnio w swiecie tibijskim glosno jest o lagach ktorych doswiadczaja gracze z niektorych krajow. Fad van Nal, administrator CIPsoftu, wyjasnia wreszcie o co chodzi (Link macie powyzej) i jak mozecie sprawdzic czy was to dotyczy.


W tym samym temacie, Kanttar Don Doggy donosi o problemach waznego routera we frankfurcie. Na forum tibianews mozemy zobaczyc detale na ten temat.

Oryginalnie napisane przez Fad van Nal, Administrator Techniczny CIP

It's known that currently lags are infuencing the gameplay heavily for some people. Especially players from Poland and Sweden are affected.

Those problems are NOT caused by the CipSoft servers, our network or our providers network.

You can test this yourself:
Do a traceroute to www.tibia.com (on windows type in tracert www.tibia.com at the command prompt) and look at the output. Usually you'll get 3 data per hop until you reach the target. Some hops do not answer (like www.tibia.com itself), ignore them. Just track those that answer and find out the one where the times are getting up alot. Usually you should be around 100 ms or less when reaching the last hop that is answering. If this is the case everything should be fine for now. If it takes alot longer you should check which hop is causing the high delay and you will find the source of the problem.

It may happen that you do not see any problems. That can happen due to the fact that the network traffic is changing constantly. Try again when you experience lags and compare the new figures you will get.

If you've successfully tracked down the issue to a certain router you may safe the output and contact your provider and explain the situation to him. Only your provider can fix the problem.

Tłumaczenie: Jak wszystkim wiadomo ostatnimi dniami wielu ludziom powazne lagi przeszkadzaja w grze, a szczegolnie graczom z Polski oraz Szwecji. Te problemy NIE sa spowodowane przez CIPsoft.


Mozecie to przetestowac sami:


Dajemy Start->Uruchom i wpisujemy Tracert www.tibia.com. Przewaznie powinno to pojsc bardzo szybko, ale przez awarie routera zobaczymy przez co sie laczymy: Londyn, New York itd. Jak wam to idzie ponizej 100ms jest ok. Mi idzie jakies 3 minuty -.-


Mozliwe ze nie zauwazycie zadnych problemow. Moze to byc spowodowane ze ruch w necie sie szybko zmienia. Sprobujcie ponownie jak bedziecie mieli lagi.


Jak juz przeanalizowales cala sciezke i masz wykaz routerow przez ktore sie nie powinno laczyc, wyslij to do administratora netu. Tylko administrator moze naprawic problem.

[Rothes]

Ten temat na pewno wyjaśni wszystko noobkom, które wciąż zakładają nowe topicy na temat lagów... Chociaż jeżeli ktoś chciał to dowiedziałby się o tym wcześniej (od dobrych paru dni jest o tym post w dziale Help na forum www.tibia.com).

[Solero]

hmm to ja chyba zakończe moją przygodę z tibią powód:



a mojemu adminowi to zwisa

[Smiti]

Me to czemu wybralem niemiecki serv?- żeby nie było lagów OMG

[Sowa]

a co ja mam powiedziec ? -.-

[S1wy]

Ty to masz za***iscie!

[Karlos]

a co wogole wyswietla ten tracert?

[Ozon18]

Droge wedrowania sygnalu.
Im wiecej macie pozycji tym gorzej

[$corcerer]

Jak coś zobaczycie, to dobrze dla was, jak nie to trudno :>
xtraceroute
www.tibia.com


To jedno zdjecie, ale byscie nie zobaczyli dokladnie :> musialem troche obrócić :>
EDIT
A dla tych co nie umieją dorzucę też normalnego trace'a

1  192.168.1.1 (192.168.1.1)  0.405 ms  0.362 ms  0.329 ms
 2  80.50.215.210 (80.50.215.210)  15.972 ms  15.866 ms  15.896 ms
 3  80.50.215.209 (80.50.215.209)  24.912 ms  25.280 ms  25.053 ms
 4  z.kat-r2.do.war-r3.tpnet.pl (194.204.175.113)  29.803 ms  29.840 ms *
 5  do-war-tr3.tptransit.pl (195.149.232.133)  30.078 ms  29.787 ms  29.917 ms
 6  so-4-0-0-0.wrsbb1.Warsawa.opentransit.net (193.251.248.57)  29.880 ms  29.818 ms  29.907 ms
7 so-2-2-0-0.fftcr1.Frankfurt.opentransit.net (193.251.240.161) 52.903 ms 52.901 ms so-3-1-0-0.fftcr1.Frankfurt.opentransit.net (193.251.240.165) 52.863 ms
 8  so-1-0-0-0.fftcr2.Frankfurt.opentransit.net (193.251.132.90)  100.811 ms  52.917 ms  52.799 ms
9 so-3-0-0-0.loncr1.London.opentransit.net (193.251.128.205) 69.018 ms so-7-0-0-0.loncr2.London.opentransit.net (193.251.242.138) 68.834 ms 68.552 ms
10 bcr2-so-4-0-0.Londonlnx.savvis.net (206.24.169.157) 68.940 ms so-3-0-0-0.loncr1.London.opentransit.net (193.251.128.205) 100.719 ms 69.783 ms
11 bcs2-so-2-1-0.Londonlnx.savvis.net (204.70.193.126) 69.897 ms bcr2-so-4-0-0.Londonlnx.savvis.net (206.24.169.157) 68.886 ms bcs2-so-2-1-0.Londonlnx.savvis.net (204.70.193.126) 69.811 ms
12 bcs2-so-2-1-0.Londonlnx.savvis.net (204.70.193.126) 69.839 ms bcs1-so-2-1-0.Londonlnx.savvis.net (204.70.193.118) 69.851 ms bcs2-so-2-1-0.Londonlnx.savvis.net (204.70.193.126) 69.836 ms
13  bcs2-so-0-0-0.NewYork.savvis.net (204.70.192.121)  148.018 ms  148.111 ms  148.622 ms
14 bcs1-so-6-0-0.NewYork.savvis.net (204.70.192.37) 137.855 ms bcs2-so-0-0-0.NewYork.savvis.net (204.70.192.121) 147.866 ms bcs1-so-6-0-0.NewYork.savvis.net (204.70.1
92.37)  136.847 ms
15  mar1-pos-5-0.NewYorknyd.savvis.net (204.70.193.25)  145.823 ms  145.966 ms  145.868 ms
16  kpn-eurorings-bv.NewYorknyd.savvis.net (208.173.134.70)  137.865 ms  137.824 ms  136.888 ms
17  ledn-rou-1001.NL.eurorings.net (134.222.230.97)  232.923 ms  233.013 ms  233.062 ms
18  ffm-s1-rou-1001.DE.eurorings.net (134.222.230.14)  237.672 ms  237.867 ms  237.862 ms
19  nbg-s1-rou-1073.DE.eurorings.net (134.222.228.70)  237.863 ms  237.783 ms  237.880 ms
20  * * *
21  oc48-srp4-0.gsr320.nuernberg.gpf1.core.ip-exchange.de (212.123.127.33)  144.078 ms  143.806 ms  143.928 ms
22 oc48-srp4-0.gsr320.nuernberg.gpf1.core.ip-exchange.de (212.123.127.33) 143.861 ms ge1-1-953.rtr3.nuernberg.gpf.colo1.ip-exchange.de (212.123.127.214) 144.288 ms *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

[Kamil-1990]

jak ja to wpisuje to umnie jest git