The online racing simulator
[Sort of fixed] cargame.nl servers down?
(22 posts, started )
[Sort of fixed] cargame.nl servers down?
Quote :[root@ ~]# ping master.liveforspeed.net
PING master.liveforspeed.net (213.40.20.2) 56(84) bytes of data.

--- master.liveforspeed.net ping statistics ---
19 packets transmitted, 0 received, 100% packet loss, time 18097ms

[root@ ~]# ping lfsforum.net
PING lfsforum.net (213.40.20.4) 56(84) bytes of data.
64 bytes from delta.lfs.net (213.40.20.4): icmp_seq=1 ttl=56 time=10.9 ms
64 bytes from delta.lfs.net (213.40.20.4): icmp_seq=2 ttl=56 time=10.8 ms
64 bytes from delta.lfs.net (213.40.20.4): icmp_seq=3 ttl=56 time=11.0 ms
64 bytes from delta.lfs.net (213.40.20.4): icmp_seq=4 ttl=56 time=10.8 ms
64 bytes from delta.lfs.net (213.40.20.4): icmp_seq=5 ttl=56 time=10.7 ms

--- lfsforum.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 10.797/10.888/11.001/0.075 ms

What the?

What did I do?
what about a trace route?
how close do you get, is it hitting the lfs "subnet" or is the last response several nodes short?

I dont know if it related, but accessing the cargame website is very hit and miss this morning. More miss than hit to be honest.

I'd be inclined to think is was a routing/network issue at your end as the host list on the master servers seems to be populated and it's just the cargame servers which are missing.

you're pinging from a *nix machine, (there isn't a linux dedi host is there?) so i assume that is the webserver not the game server. is the result the same from dedicated host?

Sorry to be obvious, but have you tried a reboot of server and router platforms, if its a hosted router have you escalated to the provided to ensure it isnt a network issue?
On LFS IRC they say it might is a temporarily glitch because they can ping the master server.

I know, because I can do that too from home or from another server from the same datacenter. It specifically is the cargame server which is blocked on IP address 'from the other side'.

And yes, I send an e-mail using the webform on lfs.net...
Quote from gandlers :
I'd be inclined to think is was a routing/network issue at your end as the host list

Impossible... Look at lfsforum.net replying..

Quote from gandlers :
Sorry to be obvious, but have you tried a reboot of server and router platforms, if its a hosted router have you escalated to the provided to ensure it isnt a network issue?

Didn't reboot this server for almost 2 years. Linux servers almost never need a reboot.

And I do not believe it's a network issue because of... *see reaction on quote 1*
Quote from gandlers :what about a trace route?
how close do you get, is it hitting the lfs "subnet" or is the last response several nodes short?

Quote :[root@]# traceroute master.liveforspeed.net
traceroute to master.liveforspeed.net (213.40.20.2), 30 hops max, 40 byte packets
1 rbx-16-m2.fr.eu (91.121.67.252) 0.501 ms 0.716 ms 0.842 ms
2 * * *
3 rbx-g2-a9.fr.eu (91.121.131.14) 0.421 ms 0.605 ms 0.688 ms
4 ldn-5-6k.uk.eu (91.121.131.178) 4.063 ms ldn-5-6k.uk.eu (91.121.131.182) 4.158 ms *
5 * * *
6 * * *
7 * * *
8 * * *
9 beta.lfs.net (213.40.20.2) 10.919 ms * *

So, yes.. Clearly a block on purpose.
Results when trying to trace to cargame.nl

0 xxx.xxx.xxx.xxx xxxxxxxx 0 ms 0 ms 0 %
1 xxx.xxx.xxx.xxx 1 ms 1 ms 0 %
2 xxx.xxx.xxx.xxx 2 ms 2 ms 0 %
3 188.39.1.26 lns17.inx.dsl.enta.net 14 ms 14 ms 0 %
4 188.39.1.25 gi1-7.inx.dist.dsl.enta.net 12 ms 12 ms 0 %
5 78.33.141.89 te2-2.interxion.dsl.enta.net 13 ms 13 ms 0 %
6 87.127.236.209 te2-3.interxion.core.enta.net 13 ms 13 ms 0 %
7 87.127.236.137 te4-2.telehouse-east.core.enta.net 13 ms 13 ms 0 %
8 195.66.224.220 sw1.tc.lon.ovh.net no response 100 %
Could not trace past sw1.tc.lon.ovh.net (195.66.224.220).

I'm in the UK along with the LFS servers and i can trace to the master servers with no issues but not to the cg forum which leads me to believe that the issues are at your end.
Are the CG servers, (LFS, airio and web) on the same subnet in the same datacenter, i.e. do they connect to the internet via the same router or are they on different routers/networks?
Quote from cargame.nl :So, yes.. Clearly a block on purpose.

Hmm, ok

the routeing seems to be working, but I wouldnt rule out network issues.
As you can see I am having issues reaching you from the UK, so your replies from the master servers could be getting lost too.

just because your packets can get to LFS servers doesn't mean that they can get reply to you! Or rather, RELIABLY reply to you.
I made the server not to respond to these kind of requests on purpose ages ago. It's a basic security measure against port scan kiddies. So I am not surprised you cannot do this.

You can reach the forum, I noticed you logged in earlier this hour.
Quote from cargame.nl :So, yes.. Clearly a block on purpose.

how can you say that when most of the hops in that traceroute fail?

not to mention, one of the packets does get through.

lfs didn't block you from the master server, get over yourself dude.

My traceroute [v0.80]
bloomfield (0.0.0.0) Sat Oct 22 04:20:15 2011
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 50 0.1 0.1 0.1 0.3 0.0
2. 10.66.64.1 0.0% 50 8.0 7.5 6.6 10.8 0.8
3. 24.226.5.145 0.0% 50 10.8 12.0 7.7 30.1 5.3
4. 24.226.6.137 0.0% 50 16.8 10.6 9.4 16.8 1.2
5. 64.34.137.61 0.0% 50 10.9 12.3 9.5 38.9 5.9
6. 216.187.114.194 0.0% 50 24.8 28.5 23.4 87.9 13.6
7. 198.32.118.106 12.0% 50 25.3 44.1 23.7 313.2 60.5
8. 213.251.128.30 16.0% 50 94.9 162.0 94.9 422.2 92.5
9. 91.121.131.177 0.0% 50 104.6 102.3 101.0 106.6 0.9
10. 91.121.131.13 12.0% 50 101.4 116.9 100.8 327.5 45.1
11. 213.251.191.43 0.0% 50 98.8 99.7 98.6 103.9 1.0
12. 91.121.67.126 0.0% 50 98.7 99.2 98.1 102.0 0.9


sounds like you need to complain to OVH.
Right... So I cannot reach 213.40.20.2 but 213.40.20.4 is no problem at all.

Must be on my end then yes. Logical.
@nl2dav
yes I managed to get on the forum earlier although there was a massive delay before the page appeared: hence I ended up here following your post. I havent been able to get onto the forum since.

@blunder
It is quite normal for hops not to respond to the ICMP requests (as nl2dav said to prevent hack, DoS attacks, exploits etc)

The traceroute software I am using isnt the standard basic OS provided version, it is a professional commercial version which uses "other" methods over and above the basic ICMP methods.

@nl2dav
the fact that my trace seems to stop in london suggests that there could be a peering issue, (maybe a BGP issue) between higher tiered providers. The servers are hosted in france?
I'm not tracing into any french nodes.
I still think it is more likely to be an internet/network issue (see enough of them at work everyday!)
OK...

Maybe it is;
--- master.liveforspeed.net ping statistics ---
620 packets transmitted, 9 received, 98% packet loss, time 623193ms

Still very strange that lfsforum, which is .4 has no problems at all...

Maybe the lfsforum and the master server are not at the same UK datacenter.. Hmm..
Quote from cargame.nl :Right... So I cannot reach 213.40.20.2 but 213.40.20.4 is no problem at all.

Must be on my end then yes. Logical.

I'm not going to "teach grandma to suck eggs", but just because those two addresses are virtually next to each other doesnt mean that they are co-located, connected to the same subnet or are even "real" hosts.
they could be virtual IP's which are then farmed out / redirected to any number of internal servers. Not knowing the LFS infrastructure I cant comment. But 10+ years in data networking has taught me never to assume and never to be stuborn; someone may know some information you dont have access to.

I've exhausted my suggestions, so good luck with getting to the bottom of it!
Quote from gandlers :has taught me never to assume and never to be stuborn; someone may know some information you dont have access to.

If I do a trace from my homeline both follow the same route. Doesn't say everything of course.

Quote from gandlers :
I've exhausted my suggestions, so good luck with getting to the bottom of it!

Hmm no.

If you experience problems from your own connection then it's indeed a network issue between UK/France. I'm afraid. Just going to wait now first then. Thanks for your replies
I have no problems tracing lfsforum.net or master.lfs.net.


[madcat@Qosmio-X300 ~]$ traceroute lfsforum.net
traceroute to lfsforum.net (213.40.20.4), 30 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.057 ms 0.864 ms 0.847 ms
2 88.103.200.43 (88.103.200.43) 10.201 ms 9.794 ms 10.407 ms
3 88.103.203.1 (88.103.203.1) 10.135 ms 10.161 ms 9.984 ms
4 194.228.190.1 (194.228.190.1) 30.369 ms 29.683 ms 12.710 ms
5 194.228.190.193 (194.228.190.193) 12.878 ms 11.585 ms 11.565 ms
6 Ae0-0-grtprach1.red.telefonica-wholesale.net.7.16.84.in-addr.arp (84.16.7.29) 12.010 ms 10.531 ms 11.626 ms
7 Xe-6-0-3-0-grtfraix4.red.telefonica-wholesale.net.12.16.84.in-ad (84.16.12.254) 19.711 ms Xe0-1-0-0-grtfraix2.red.telefonica-wholesale.net (213.140.43.186) 17.812 ms 18.147 ms
8 Xe5-0-0-0-grtlontl3.red.telefonica-wholesale.net (84.16.14.126) 80.320 ms Xe-0-1-2-0-grtlontl3.red.telefonica-wholesale.net.127.142.94.in- (94.142.127.34) 32.028 ms Xe-0-0-2-0-grtlontl3.red.telefonica-wholesale.net.121.142.94.in- (94.142.121.74) 31.801 ms
9 kpn-6-3-0-0-grtlontl3.red.telefonica-wholesale.net (213.140.52.94) 31.594 ms 31.278 ms 31.851 ms
10 ldn-s2-rou-1041.UK.eurorings.net (134.222.228.94) 56.511 ms 32.824 ms 34.669 ms
11 ldn-s10-rou-1041.UK.eurorings.net (134.222.231.26) 31.749 ms 31.956 ms 31.555 ms
12 134.222.146.53 (134.222.146.53) 50.040 ms 32.647 ms 31.996 ms
13 86.54.183.201 (86.54.183.201) 39.673 ms 39.832 ms 39.176 ms
14 man02-ge-man01.core.netline.net.uk (212.111.130.6) 39.976 ms 39.175 ms 41.175 ms
15 lon01-stm1-man01.core.netline.net.uk (212.111.130.2) 42.595 ms 43.967 ms 42.681 ms
16 ldscat01-ge-lds01.core.netline.net.uk (213.40.3.73) 39.025 ms 39.887 ms 39.095 ms
17 delta.lfs.net (213.40.20.4) 40.126 ms 39.623 ms 39.681 ms


[madcat@Qosmio-X300 ~]$ traceroute master.lfs.net
traceroute to master.lfs.net (213.40.20.2), 30 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.933 ms 1.062 ms 1.720 ms
2 88.103.200.43 (88.103.200.43) 10.058 ms 9.870 ms 10.070 ms
3 88.103.203.1 (88.103.203.1) 10.325 ms 11.103 ms 9.842 ms
4 194.228.190.1 (194.228.190.1) 11.349 ms 12.026 ms 11.573 ms
5 194.228.190.193 (194.228.190.193) 12.136 ms 11.049 ms 12.128 ms
6 Ae0-0-grtprach1.red.telefonica-wholesale.net.7.16.84.in-addr.arp (84.16.7.29) 10.816 ms 10.857 ms 11.573 ms
7 Xe-6-0-3-0-grtfraix4.red.telefonica-wholesale.net.12.16.84.in-ad (84.16.12.254) 17.232 ms Xe0-1-0-0-grtfraix2.red.telefonica-wholesale.net (213.140.43.186) 18.200 ms 18.518 ms
8 Xe-0-1-2-0-grtlontl3.red.telefonica-wholesale.net.127.142.94.in- (94.142.127.34) 31.434 ms Xe-0-0-2-0-grtlontl3.red.telefonica-wholesale.net.121.142.94.in- (94.142.121.74) 31.730 ms Xe-0-1-2-0-grtlontl3.red.telefonica-wholesale.net.127.142.94.in- (94.142.127.34) 32.564 ms
9 kpn-6-3-0-0-grtlontl3.red.telefonica-wholesale.net (213.140.52.94) 31.454 ms 32.777 ms 31.044 ms
10 ldn-s2-rou-1041.UK.eurorings.net (134.222.228.94) 68.984 ms 32.379 ms 32.739 ms
11 ldn-s10-rou-1041.UK.eurorings.net (134.222.231.26) 32.734 ms 32.041 ms 30.940 ms
12 134.222.146.53 (134.222.146.53) 33.276 ms 30.684 ms 31.775 ms
13 86.54.183.201 (86.54.183.201) 38.417 ms 37.887 ms 40.165 ms
14 man02-ge-man01.core.netline.net.uk (212.111.130.6) 39.835 ms 38.975 ms 38.349 ms
15 lon01-stm1-man01.core.netline.net.uk (212.111.130.2) 42.644 ms 41.661 ms 42.472 ms
16 ldscat01-ge-lds01.core.netline.net.uk (213.40.3.73) 39.946 ms 39.154 ms 39.647 ms
17 beta.lfs.net (213.40.20.2) 39.158 ms 39.678 ms 39.615 ms

According to this the servers appear to be topologically close, they might be even running on the same machine in different virtualized guests.
No something indeed is wrong with the UK<->France routing. Sorry guys, I had the focus too much on master/lfsforum.net ping output. No idea why these differ so much from each other but thanks for assistance.

I get confirms from other places in the UK that the cargame server is not reliably reachable.

Raised a ticket @hoster.
yeah weird. But at least I can confirm we're not blocking you. If we'd block you, you'd know the reason why!

Anyway, just confirming what you've already discovered. There appear to be some problems on the route. I assume this will get fixed soon.
Attached images
cargametrace.gif
LOL

Just when you did that, it seems to start to work again.

Nice timing
#19 - Xone
is cargame.nl S2 and cargame.nl-forum down?
No. At least not right now.
Quote from THE WIZARD DK :
is this related???

22 October 2011, yes, probably.

Xone has a three year ban, no idea what he wants to do anyway other then seeking attention.

Quote from THE WIZARD DK :

oh cargame is back on lfs remote

Because you reminded me to switch it back on

.
#22 - Xone
Quote from cargame.nl :22 October 2011, yes, probably.

Xone has a three year ban, no idea what he wants to do anyway other then seeking attention.


Because you reminded me to switch it back on

.

second S2 Account

[Sort of fixed] cargame.nl servers down?
(22 posts, started )
FGED GREDG RDFGDR GSFDG