The online racing simulator
Official DoP Train
(12 posts, started )
Official DoP Train
-----------------
No.1

The BurnoutCrew:
The next trainings-race of the DoP2016 will be held on 11.01.2016
The NGT will be driven at Aston Grand Touring rev [AS6r] and we hope for many sign-ins from you!

Details for the race:
* date: Monday, 11.01.2016
* car: N- GTR (UFR / XFR)
* track: Aston Grand Touring rev [AS6r]
* race-length: 2 Hours
* LfS-server: DoP- Grid1
* password: dopas
* training: from 19.00h until 20.00h (German time!)
* qualification: 20.00h until 20.15h (German time!) ( qualification of 15 min.)
* start of the race: 20.25h (-+ 5 min, German time!)
* drivers: max. 40 on one server (In the case of more than 40 sign-ins, the field will be splitted onto 2 servers)

Who wants to, may join the seperate channel of the BC-TeamSpeak:
*IP: 78.111.75.162


Infos:
Guest-starters are always welcome!
***push***

Guests and LFS Fanatics are welcome, too Na-na
#3 - pik_d
There's one today (11th), right?
Yes!
Maybe someone is interested to have a look at the replay from the training race yesterday.

Download here.

We have seen a few drivers yesterday who haven't signed in for the main race yet. We hope you'll take the chance to be part of this event and sign in the next days Smile
#6 - pik_d
Is the race today 90 minutes or 2 hours?
#8 - troy
Server was pretty laggy there, I've checked my ping and things are clearly fine on my end, no package loss nothing. So I would guess something is wrong on your end with the routing guys?

Ping-Statistik für 193.99.144.80:
Pakete: Gesendet = 210, Empfangen = 210, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 13ms, Maximum = 23ms, Mittelwert = 15ms

Not the first time this happens either, you may want to double check this before the 24h race!
I was curious if I was the only one having internet issues..turns out not.
A word to the connection problems
It is easy to say, all is fine at my side, it has to be you - but that's not half the truth...

Server DoP - Grid 1 showed up laggy yesterday. Yes, that's what we've all seen. I don't remember exactly, but 7-9 people disconnected due to network problems. More than 40 were online - having more or less lag.
We had also an issue with teamspeak and our homepage. Maybe it's important to know that these two things are hosted on a totally different server. I don't really know but I was told that one is hosted in Cologne and the other in Frankfurt.

So analyses may start with an eye on the facts.

First of all I don't want to conceal that the server hosting the LfS-Dedicated Hosts is used for other things too. Yesterday there were some people uploading some backups via FTP. Although the ftp-connections are limited to a maximum, they could cause lag to some people. Those backups are made from Monday till Friday in the evening, so that may be the reason why troy experienced lag more than once in the past.
But this is no explanation for the trouble with teamspeak!

Next thing is to check the connection from point too point. A simple ping to "wherever" doesn't really help. (The answers from Windows are in german language. If you perform the commands on your machines you'll get them in your preferred one. The words doesn't matter too much in my explanation.)

A ping to google.de may show:

Ping-Statistik für 173.194.32.216:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 21ms, Maximum = 21ms, Mittelwert = 21ms

A ping to the BurnoutCrew-Server shows from my current location:
Ping-Statistik für 81.20.142.84:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 18ms, Maximum = 23ms, Mittelwert = 19ms

Not much information when everything is ok.

Sad but true, the internet isn't a thing of Clients an Servers as we see with a simple ping. A network packet is travelling to different points in the world before it - hopefully - finally reaches the server. A simple thing to have a look after that routing is to perform a trace route (tracert in Windows console). This should give you some information about the time a packet looses during its way through the net.

In case of google it looks like this in my case:
Command:
tracert www.google.de

Routenverfolgung zu google.de [173.194.39.31] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms 192.168.250.254
2 1 ms 1 ms 1 ms 217.89.123.97
3 10 ms 8 ms 9 ms 80.154.240.37
4 16 ms 14 ms 15 ms hh-ea7-i.HH.DE.NET.DTAG.DE [62.154.33.2]
5 14 ms 14 ms 14 ms 80.150.170.98
6 15 ms 15 ms 15 ms 209.85.249.124
7 15 ms 15 ms 15 ms 209.85.245.165
8 15 ms 15 ms 15 ms ham02s13-in-f31.1e100.net [173.194.39.31]

Ablaufverfolgung beendet.

And for our server:
tracert 81.20.142.84

Routenverfolgung zu 81.20.142.84 über maximal 30 Abschnitte

1 <1 ms <1 ms <1 ms 192.168.250.254
2 1 ms 1 ms 1 ms 217.89.123.97
3 9 ms 9 ms 9 ms 80.154.240.37
4 18 ms 18 ms 17 ms 217.239.50.81
5 18 ms 17 ms 17 ms 80.157.131.218
6 19 ms 18 ms 18 ms core-sto2-po9.netcologne.de [81.173.192.9]
7 19 ms 19 ms 19 ms rtkds-sto-po2.netcologne.de [87.79.16.58]
8 28 ms 19 ms 19 ms backbone-nc-cgn.surfplanet.de [85.88.20.62]
9 19 ms 18 ms 18 ms 81.20.142.84

Ablaufverfolgung beendet.

We can see most loss of time happens from point 2 to 3 and 4. This is the local in-house router to the local provider. Step 8 and 9 are localized in the data center, well step 9 is the server itself.
In case of lag or connection problems I would like to see this trace route to get more than an idea where the time loss happens.
I tested this trace route during a bigger ftp-upload without limited traffic speed. The connection is less stable than before. The worst report I found was this:
Routenverfolgung zu 81.20.142.84 über maximal 30 Abschnitte

1 <1 ms <1 ms <1 ms 192.168.250.254
2 4 ms 1 ms 1 ms 217.89.123.97
3 10 ms 18 ms 27 ms 80.154.240.37
4 16 ms 16 ms 57 ms 217.239.50.81
5 26 ms 34 ms 17 ms 80.157.131.218
6 31 ms 35 ms 18 ms core-sto2-po9.netcologne.de [81.173.192.9]
7 18 ms 18 ms 19 ms rtkds-sto-po2.netcologne.de [87.79.16.58]
8 19 ms 19 ms 19 ms backbone-nc-cgn.surfplanet.de [85.88.20.62]
9 52 ms 38 ms 32 ms 81.20.142.84

Ablaufverfolgung beendet.

Not that bad anyway but a possible cause for lag experiences.

Ok, this was what you can do to check your connection to the server and help me to find problems if there are some at server side.

What we do to get the server as stable as possible:
1) FTP will be disabled
2) Tools for Sign-In and Qualify and so on will be stopped
3) There are many LfS-Hosts on this machine. Most of them will be stopped as well.

So hopefully no one has to disconnect due to network problems but I feel like some people will have problems as every year.
#11 - troy
Thanks for the detailed infos, I know of course that the internet can be a strange mistress. Smile Could've been anything from routing problems on a certain carrier to problems caused by your mentioned ftp backups.

It may be worth opening a support ticket at your provider next time it happens so they could investigate further.

A good tool to investigate where you lose packets is MTR (or WinMTR http://sourceforge.net/projects/winmtr/ for Windows), sadly I forgot to run it yesterday but will be running it tonight in case I do see lag spikes again.
Some good news:

Sign In is always open. So new teams can join at the last moment, till friday.
Now, we have realistic 17 Teams, same or better level than last year! This is for us a little surprise and not expected. Thanks a lot all these trusty lfs fans. Only these fans can make such an endurance 24h race happen!

We really enjoy it year by year! Great!

Starting Grid by now:
http://www.burnoutcrew.net/BurnoutCrew/Joomla/index.php/dop-teams

Na-na

Official DoP Train
(12 posts, started )
FGED GREDG RDFGDR GSFDG