"Marusia" - feedback please
79 replies · 18 participants · 🔒 Locked by AncientEagleHelm on Jun 26, 2011
Jul 12, 2010, 10:22 PM#1
Oki, so, Marusia is now running a copy of the Badwater/Goldrush server. Anyone notice any improvements? Anything that I've missed/forgotten to copy over? You don't need to give any feedback right now, though I'd really appreciate it maybe within a few days after you've played on the server when it's full. 
The Badwater/Goldrush server will soon be closed down very shortly, to forward/get the word out that we've moved to a different IP
The Badwater/Goldrush server will soon be closed down very shortly, to forward/get the word out that we've moved to a different IP
Page 3
Jul 25, 2010, 12:11 AM#41
C:\Users\Chris>ping 87.238.173.154
Pinging 87.238.173.154 with 32 bytes of data:
Reply from 87.238.173.154: bytes=32 time=34ms TTL=44
Reply from 87.238.173.154: bytes=32 time=31ms TTL=44
Reply from 87.238.173.154: bytes=32 time=33ms TTL=44
Reply from 87.238.173.154: bytes=32 time=33ms TTL=44
Ping statistics for 87.238.173.154:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 34ms, Average = 32ms
C:\Users\Chris>
___
C:\Users\Chris>tracert 87.238.173.154
Tracing route to 87.238.173.154 over a maximum of 30 hops
1 27 ms 99 ms 99 ms api.home
2 23 ms 21 ms 21 ms esr18.kingston6.broadband.bt.net
3 22 ms 23 ms 24 ms 217.47.159.77
4 22 ms 21 ms 22 ms 217.47.46.174
5 22 ms 23 ms 22 ms 217.41.171.29
6 22 ms 22 ms 23 ms 217.41.171.118
7 22 ms 23 ms 23 ms 217.41.171.62
8 22 ms 23 ms 21 ms 217.47.46.99
9 23 ms 22 ms 22 ms 194.72.3.125
10 23 ms 23 ms 24 ms core2-pos0-7-0-0.ilford.ukcore.bt.net
11 23 ms 24 ms 23 ms transit1-xe-11-1-0.ilford.ukcore.bt.net
12 25 ms 23 ms 23 ms t2c1-ge8-0-0.uk-ilf.eu.bt.net
13 154 ms 210 ms 32 ms POS4-0-2.ar6.LON3.gblx.net
14 31 ms 31 ms 30 ms DUOCAST.gigabitethernet3-1.ar4.AMS2.gblx.net
15 33 ms 33 ms 32 ms 87.238.173.154
Trace complete.
C:\Users\Chris>
Pinging 87.238.173.154 with 32 bytes of data:
Reply from 87.238.173.154: bytes=32 time=34ms TTL=44
Reply from 87.238.173.154: bytes=32 time=31ms TTL=44
Reply from 87.238.173.154: bytes=32 time=33ms TTL=44
Reply from 87.238.173.154: bytes=32 time=33ms TTL=44
Ping statistics for 87.238.173.154:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 34ms, Average = 32ms
C:\Users\Chris>
___
C:\Users\Chris>tracert 87.238.173.154
Tracing route to 87.238.173.154 over a maximum of 30 hops
1 27 ms 99 ms 99 ms api.home
2 23 ms 21 ms 21 ms esr18.kingston6.broadband.bt.net
3 22 ms 23 ms 24 ms 217.47.159.77
4 22 ms 21 ms 22 ms 217.47.46.174
5 22 ms 23 ms 22 ms 217.41.171.29
6 22 ms 22 ms 23 ms 217.41.171.118
7 22 ms 23 ms 23 ms 217.41.171.62
8 22 ms 23 ms 21 ms 217.47.46.99
9 23 ms 22 ms 22 ms 194.72.3.125
10 23 ms 23 ms 24 ms core2-pos0-7-0-0.ilford.ukcore.bt.net
11 23 ms 24 ms 23 ms transit1-xe-11-1-0.ilford.ukcore.bt.net
12 25 ms 23 ms 23 ms t2c1-ge8-0-0.uk-ilf.eu.bt.net
13 154 ms 210 ms 32 ms POS4-0-2.ar6.LON3.gblx.net
14 31 ms 31 ms 30 ms DUOCAST.gigabitethernet3-1.ar4.AMS2.gblx.net
15 33 ms 33 ms 32 ms 87.238.173.154
Trace complete.
C:\Users\Chris>
Jul 25, 2010, 06:07 AM#42
Badanie 87.238.173.154 z 32 bajtami danych:
Odpowiedź z 87.238.173.154: bajtów=32 czas=49ms TTL=54
Odpowiedź z 87.238.173.154: bajtów=32 czas=47ms TTL=54
Odpowiedź z 87.238.173.154: bajtów=32 czas=47ms TTL=54
Odpowiedź z 87.238.173.154: bajtów=32 czas=48ms TTL=54
Statystyka badania ping dla 87.238.173.154:
Pakiety: Wysłane = 4, Odebrane = 4, Utracone = 0
(0% straty),
Szacunkowy czas błądzenia pakietów w millisekundach:
Minimum = 47 ms, Maksimum = 49 ms, Czas średni = 47 ms
Śledzenie trasy do 87.238.173.154 z maksymalną liczbą 30 przeskoków.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 13 ms 12 ms Jaworzno-bras2.inetia.pl
3 14 ms 14 ms 13 ms JawoH001RT10-JawoH001RT09.inetia.pl
4 19 ms 19 ms 19 ms JawoH001RT09-WarsH002RT22.inetia.pl
5 22 ms 22 ms 22 ms WarsH002rt22-WarsB010rt03.inetia.pl
6 20 ms 19 ms 20 ms xe-2-3-0.waw10.ip4.tinet.net
7 41 ms 41 ms 76 ms xe-2-0-0.fra20.ip4.tinet.net
8 41 ms 41 ms 42 ms as3549.ip4.tinet.net
9 104 ms 135 ms 57 ms 89.188.3.2
10 50 ms 49 ms 48 ms 87.238.173.154
Śledzenie zakończone.
Odpowiedź z 87.238.173.154: bajtów=32 czas=49ms TTL=54
Odpowiedź z 87.238.173.154: bajtów=32 czas=47ms TTL=54
Odpowiedź z 87.238.173.154: bajtów=32 czas=47ms TTL=54
Odpowiedź z 87.238.173.154: bajtów=32 czas=48ms TTL=54
Statystyka badania ping dla 87.238.173.154:
Pakiety: Wysłane = 4, Odebrane = 4, Utracone = 0
(0% straty),
Szacunkowy czas błądzenia pakietów w millisekundach:
Minimum = 47 ms, Maksimum = 49 ms, Czas średni = 47 ms
Śledzenie trasy do 87.238.173.154 z maksymalną liczbą 30 przeskoków.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 13 ms 12 ms Jaworzno-bras2.inetia.pl
3 14 ms 14 ms 13 ms JawoH001RT10-JawoH001RT09.inetia.pl
4 19 ms 19 ms 19 ms JawoH001RT09-WarsH002RT22.inetia.pl
5 22 ms 22 ms 22 ms WarsH002rt22-WarsB010rt03.inetia.pl
6 20 ms 19 ms 20 ms xe-2-3-0.waw10.ip4.tinet.net
7 41 ms 41 ms 76 ms xe-2-0-0.fra20.ip4.tinet.net
8 41 ms 41 ms 42 ms as3549.ip4.tinet.net
9 104 ms 135 ms 57 ms 89.188.3.2
10 50 ms 49 ms 48 ms 87.238.173.154
Śledzenie zakończone.
Jul 25, 2010, 11:44 AM#43
Remember that if you do the ping and tracert from an online homepage, you might not get the right result. I tried 3 different pages, in one I had 9ms, another 140ms, another 90ms.
Jul 25, 2010, 01:22 PM#44
From my home connection (Dundee, Scotland):
From my Dedicated Server (Roubaix, France):
james$ ping 87.238.173.154
PING 87.238.173.154 (87.238.173.154): 56 data bytes
64 bytes from 87.238.173.154: icmp_seq=0 ttl=59 time=37.751 ms
64 bytes from 87.238.173.154: icmp_seq=1 ttl=59 time=37.121 ms
64 bytes from 87.238.173.154: icmp_seq=2 ttl=59 time=36.933 ms
64 bytes from 87.238.173.154: icmp_seq=3 ttl=59 time=36.322 ms
64 bytes from 87.238.173.154: icmp_seq=4 ttl=59 time=36.150 ms
^C
--- 87.238.173.154 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 36.150/36.855/37.751/0.576 ms
james$ traceroute 87.238.173.154
traceroute to 87.238.173.154 (87.238.173.154), 64 hops max, 52 byte packets
1 safe.internal.router.int (192.168.0.1) 2.154 ms 0.708 ms 0.681 ms
2 94-192-87-1.zone6.bethere.co.uk (94.192.87.1) 20.486 ms 20.968 ms 20.351 ms
3 10.1.3.245 (10.1.3.245) 21.716 ms 21.398 ms 20.415 ms
4 * * *
5 ams-ix.gs.ams.duocast.net (195.69.145.98) 35.312 ms 35.084 ms 35.176 ms
6 87.238.173.154 (87.238.173.154) 35.503 ms !Z 34.883 ms !Z 36.671 ms !ZFrom my Dedicated Server (Roubaix, France):
[james@ks356550 ~]# ping 87.238.173.154
PING 87.238.173.154 (87.238.173.154) 56(84) bytes of data.
64 bytes from 87.238.173.154: icmp_seq=1 ttl=60 time=7.66 ms
64 bytes from 87.238.173.154: icmp_seq=2 ttl=60 time=6.19 ms
64 bytes from 87.238.173.154: icmp_seq=3 ttl=60 time=6.61 ms
64 bytes from 87.238.173.154: icmp_seq=4 ttl=60 time=7.36 ms
64 bytes from 87.238.173.154: icmp_seq=5 ttl=60 time=7.36 ms
^C
--- 87.238.173.154 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 6.192/7.038/7.661/0.549 ms
[james@ks356550 ~]# traceroute 87.238.173.154
traceroute to 87.238.173.154 (87.238.173.154), 30 hops max, 40 byte packets
1 rbx-43-m2.routers.ovh.net (91.121.142.252) 0.613 ms 0.662 ms 0.672 ms
2 * * *
3 40g.ams-1-6k.routers.chtix.eu (213.251.130.66) 5.564 ms * *
4 ams-ix.gs.ams.duocast.net (195.69.145.98) 5.425 ms 5.639 ms 5.454 ms
5 87.238.173.154 (87.238.173.154) 6.136 ms !X 6.075 ms !X 6.243 ms !XJul 25, 2010, 01:47 PM#45
Holland bad idea!
Jul 25, 2010, 03:41 PM#46
BTW Karl, you know how you wanted a Kimisufi but couldn't? Well, with that server provider you technically do, it appears that the server is either located in the OVH DC in Amsterdam, or is routed through it before the final end point. 
It goes through the ams-ix.gs router, which is located in ams-1-6k Datacenter in Amsterdam, which is only 1 backbone hop away from my server (which is in rbx-1-6k) on the OVH Backbone.
It goes through the ams-ix.gs router, which is located in ams-1-6k Datacenter in Amsterdam, which is only 1 backbone hop away from my server (which is in rbx-1-6k) on the OVH Backbone.
Jul 25, 2010, 03:58 PM#47
BTW Karl, you know how you wanted a Kimisufi but couldn't? Well, with that server provider you technically do, it appears that the server is either located in the OVH DC in Amsterdam, or is routed through it before the final end point.
It goes through the ams-ix.gs router, which is located in ams-1-6k Datacenter in Amsterdam, which is only 1 backbone hop away from my server (which is in rbx-1-6k) on the OVH Backbone.
It probably just routes through it, afaik all OVH servers are in Roubaix
Jul 25, 2010, 04:13 PM#48
BTW Karl, you know how you wanted a Kimisufi but couldn't? Well, with that server provider you technically do, it appears that the server is either located in the OVH DC in Amsterdam, or is routed through it before the final end point.
It goes through the ams-ix.gs router, which is located in ams-1-6k Datacenter in Amsterdam, which is only 1 backbone hop away from my server (which is in rbx-1-6k) on the OVH Backbone.
It probably just routes through it, afaik all OVH servers are in Roubaix
Not all of them. Their largest DC is Roubaix and houses most of their servers, but they also have Datacenters in London, Paris, Brussels, Warsaw, Frankfurt, Amsterdam, Madrid and more which I can't remember.
Jul 26, 2010, 01:10 PM#49
Within two weeks.
Jul 26, 2010, 08:20 PM#50
Here are our reserved IP addresses, I've already added A records for them (they're rdns'd too ).
89.188.29.96 -> mio.aprilon.net
89.188.29.97 -> ritsu.aprilon.net
89.188.29.98 -> yui.aprilon.net
89.188.29.99 -> azusa.aprilon.net
).89.188.29.96 -> mio.aprilon.net
89.188.29.97 -> ritsu.aprilon.net
89.188.29.98 -> yui.aprilon.net
89.188.29.99 -> azusa.aprilon.net
Jul 26, 2010, 08:49 PM#51
Awful names are awful.
Jul 26, 2010, 09:05 PM#52
Awful names are awful.
They are awesome!
Jul 27, 2010, 07:33 AM#53
It's like you just named a bunch of anime characters.
;_;
;_;
Jul 27, 2010, 07:44 AM#54
It's like you just named a bunch of anime characters.
;_;
That's exactly what I did
Jul 27, 2010, 08:51 AM#55
It's like you just named a bunch of anime characters.
;_;
That's exactly what I did
;_;
Jul 27, 2010, 09:45 AM#56
First of all: why 4 servers? 
it pretty much scatters all the cool players I use to play with around.
And: How many maps are all the 4 servers running in total? (sorry, but I can't check from here)
AND CHANGE THE GODDAMN ANIME NAMES FFS!
it pretty much scatters all the cool players I use to play with around.And: How many maps are all the 4 servers running in total? (sorry, but I can't check from here)
AND CHANGE THE GODDAMN ANIME NAMES FFS!
Jul 27, 2010, 09:47 AM#57
First of all: why 4 servers?
And: How many maps are all the 4 servers running in total? (sorry, but I can't check from here)
We'll decide everything once we actually have the server.
Jul 27, 2010, 03:53 PM#58
Who cares what the names are?.. :]
And are we actually getting 4 servers?
And are we actually getting 4 servers?
Jul 27, 2010, 04:29 PM#59
Who cares what the names are?.. :]
And are we actually getting 4 servers?
It's one dedicated server that will be able to host 4 gameservers. So yes.
Jul 27, 2010, 06:31 PM#60
First of all: why 4 servers?
And: How many maps are all the 4 servers running in total? (sorry, but I can't check from here)
AND CHANGE THE GODDAMN ANIME NAMES FFS!
1) It would be a waste if we didn't use the resources of the dedicated server. Thus 4 servers, 1 each core.
2) You can still play on the same server with everybody else.
3) The servers aren't online yet.
4) The anime names aren't harmful.
Edit: also these A records will point to the IP addresses
:ixion.aprilon.net -> 89.188.29.96
ixion2.aprilon.net -> 89.188.29.97
ixion3.aprilon.net -> 89.188.29.98
ixion4.aprilon.net -> 89.188.29.99