No response?
#1 Guest_LoLLneSS
Отправлено 16 August 2010 - 01:36 PM
For me it's:
http://css.setti.inf...244.3.141:27022
&
http://css.setti.inf...11.116.21:27022
I added this addresses to setti & everything was OK, but 1 day server ip 94.244.3.141:27022 stopped being monitored on setti. On main page I get 'No response' answer. On my server setti's ip isn't banned, and ppl from hosting company said that fire wall doesn't refers to CS server ports so it can't block any kind of packets from setti send to server. I'm confused that really strange. If someone knows the reason why that can be, please help me.
#2 Guest_LoLLneSS
Отправлено 16 August 2010 - 02:08 PM
#3
Отправлено 16 August 2010 - 02:17 PM
Unless the physical location of the servers is different then there's no difference in the ping either. IP address doesn't have anything to do with ping. If the other IP address is just a redirect server then it's even worse as players connect to the actual server and find that their ping is higher than what they saw in the serverbrowser.If you ask why 2 ip adresses, the reason is that. On first server ping is good for one part on people, and on second for other.
#4 Guest_LoLLneSS
Отправлено 16 August 2010 - 05:27 PM
+ip 0.0.0.0 doesn't work.Start your server with +ip 0.0.0.0 startup parameter and it should listen to all open network interfaces. I'm not 100% sure it'll work then either. It's about how the CS server handles connections.
Unless the physical location of the servers is different then there's no difference in the ping either. IP address doesn't have anything to do with ping. If the other IP address is just a redirect server then it's even worse as players connect to the actual server and find that their ping is higher than what they saw in the serverbrowser.If you ask why 2 ip adresses, the reason is that. On first server ping is good for one part on people, and on second for other.
Btw on ip #1 I have ping ~30, and on ip #2 ping is ~65. And my friend hase ~50ping on ip #1, and ~5ping on ip #2. Isn't not just redirecting like you said.
Is there any other solution? Please.
#5
Отправлено 16 August 2010 - 06:33 PM
#6 Guest_LoLLneSS
Отправлено 17 August 2010 - 08:52 AM
#7 Guest_LoLLneSS
Отправлено 17 August 2010 - 08:57 AM
tracert 94.244.3.141
tracert 91.211.116.21
That is 2 ips of my server. You will see they have diffent routes. So it's not just redirects.
#8
Отправлено 17 August 2010 - 01:52 PM
For example, when I connect to your server from Finland how do you make the packets go faster to your country? Don't think about the IP address, if the physical server is in Ukraine the data must travel there somehow. So the packets leave Helsinki... where do they go? You don't control it. I don't control it. Still the packets get there.
It is possible that in Ukraine some mainline cables get more stressed than the others and that affects your ping. In any other modern country mainlines don't get stressed.
As an example here are some ping times from Hetzner (Germany) to other countries. The latencies rise depending on how fast the connection is to the target server. Latencies come from either local (Hetzner) slowdowns or target slowdowns. Occasionally the server itself which you ping might be stressed and causes latency. Also the pinging server (in images it's Setti server) might be stressed and cause latency.
http://img62.imagesh...pinganispro.png
http://img231.images...pingsaunala.png
http://img809.images...pingsgwcore.png
You can see that the latency to a Finnish hosting company is quite stable except those two spikes. Then it's quite good to Romanian ISP too but not as good. The Latvian gateway is not good at all, ping times vary from 50ms to 120ms. The two spikes are caused by slowness in Setti server or in Hetzner network.
It's physical impossibility that a server in the same physical location would be faster on one IP and slower on the other. It's just the initial "exit" that the data packets take when they leave your server.
It is quite possible that the hosting company is doing their routing wrong or they try to do load balancing between routes. That is the reason why the ping is sometimes better or worse on the IPs. So in a way you may be correct but if you had good enough hosting that would be an issue at all - you would always get the best possible latency.
#9
Отправлено 17 August 2010 - 01:55 PM
When IPv6 gets more popular they say it should provide better packet handling in large network nodes all around the world and make internet work much faster than it is today. For example latency from Europe to USA is often too high to play any online games. I'm not sure whether that will actually happen though.
#10 Guest_LoLlneSS
Отправлено 17 August 2010 - 08:04 PM
Thx for telling that, now I understand the way it works beter. But I steel don't understand one thing. Explain that pleaseIt's just not technically possible unless they limit the rate on the other IP themselves. When the packets get off from Ukraine or enter Ukraine from Europe it's impossible for you to control where the packets travel. You only control how they travel near your own network - that is, your hosting company controls.
For example, when I connect to your server from Finland how do you make the packets go faster to your country? Don't think about the IP address, if the physical server is in Ukraine the data must travel there somehow. So the packets leave Helsinki... where do they go? You don't control it. I don't control it. Still the packets get there.
It is possible that in Ukraine some mainline cables get more stressed than the others and that affects your ping. In any other modern country mainlines don't get stressed.
As an example here are some ping times from Hetzner (Germany) to other countries. The latencies rise depending on how fast the connection is to the target server. Latencies come from either local (Hetzner) slowdowns or target slowdowns. Occasionally the server itself which you ping might be stressed and causes latency. Also the pinging server (in images it's Setti server) might be stressed and cause latency.
http://img62.imagesh...pinganispro.png
http://img231.images...pingsaunala.png
http://img809.images...pingsgwcore.png
You can see that the latency to a Finnish hosting company is quite stable except those two spikes. Then it's quite good to Romanian ISP too but not as good. The Latvian gateway is not good at all, ping times vary from 50ms to 120ms. The two spikes are caused by slowness in Setti server or in Hetzner network.
It's physical impossibility that a server in the same physical location would be faster on one IP and slower on the other. It's just the initial "exit" that the data packets take when they leave your server.
It is quite possible that the hosting company is doing their routing wrong or they try to do load balancing between routes. That is the reason why the ping is sometimes better or worse on the IPs. So in a way you may be correct but if you had good enough hosting that would be an issue at all - you would always get the best possible latency.
When I:
1) cmd > ping 91.211.116.21 I ALWAYS get ~65 ping.
2) cmd > ping 94.244.3.141 I ALWAYS get ~30 ping.
(THERE IS NO JUMPS OF PING I ALWAYS GET VALUE CLOSE TO WHAT I WROTE)
So I always play on 94.244.3.141 ip, and has awesome latency there.
When My friend:
1) cmd > ping 91.211.116.21 MY FRIEND ALWAYS GET ~5 ping.
2) cmd > ping 94.244.3.141 MY FRIEND ALWAYS GET ~40 ping.
(HE ALWAYS GETS THIS VALUES)
So He is always playing on 91.211.116.21 ip, and has awesome latency there.
#11
Отправлено 18 August 2010 - 06:23 AM
1) cmd > ping 91.211.116.21 SETTI ALWAYS get ~35 ping.
2) cmd > ping 94.244.3.141 SETTI ALWAYS get no response.
Here's how traceroute shows the route.
traceroute to 91.211.116.21 (91.211.116.21), 30 hops max, 40 byte packets 1 static.193.40.40.188.clients.your-server.de (188.40.40.193) 0.918 ms 0.926 ms 0.951 ms 2 hos-tr4.juniper2.rz10.hetzner.de (213.239.227.225) 0.155 ms 0.174 ms hos-tr2.juniper1.rz10.hetzner.de (213.239.227.161) 0.152 ms 3 213-239-240-230.clients.your-server.de (213.239.240.230) 4.846 ms 4.849 ms 4.836 ms 4 de-cix.netassist.kiev.ua (80.81.192.66) 35.314 ms 35.298 ms 35.299 ms 5 proline-cl-939.netassist.ua (62.205.159.205) 35.295 ms 35.295 ms 35.291 ms 6 slots6.playground.org.ua (91.211.116.21) 35.540 ms 35.644 ms 35.590 msWhat you should see is that the route is very short - only 6 hops. That is because Hetzner is in Germany and has good connections to everywhere in Europe. Same way your hosting company Playground is well connected - thus the route is short. Now look at the 4th router, it's IP 80.81.192.66. Then there's one router between and then your server.
Let's trace your other IP address.
traceroute to 94.244.3.141 (94.244.3.141), 30 hops max, 40 byte packets 1 static.193.40.40.188.clients.your-server.de (188.40.40.193) 0.731 ms 0.759 ms 0.785 ms 2 hos-tr1.juniper1.rz10.hetzner.de (213.239.227.129) 0.149 ms 0.176 ms hos-tr3.juniper2.rz10.hetzner.de (213.239.227.193) 0.158 ms 3 213-239-240-230.clients.your-server.de (213.239.240.230) 4.820 ms 4.834 ms hos-bb1.juniper2.ffm.hetzner.de (213.239.240.226) 4.794 ms 4 de-cix.netassist.kiev.ua (80.81.192.66) 35.060 ms 35.066 ms 35.279 ms 5 q9-juniper-gw.netassist.ua (62.205.134.93) 35.624 ms 35.515 ms 35.457 ms 6 * * * 7 * * * ...This trace never completes as the router at 6th point doesn't reply anything to the "traceroute query". It doesn't forward the query forward either because routers after that don't reply anything either. Now again look at the 4th router on the route. It's the same router as tracing your other IP address. So if the data packet was sent through the same route it would reach your server with only 1 intermediary router. Now because the target IP is different the router is instructed to route the packet elsewhere - to router 6 which doesn't reply. This is the "Cisco routing" they are referring to.
Router 6 might be just connected to Ukrainian own network and the other IP is for international connections. That doesn't make much sense but sometimes hosting companies do weird stuff for weird reasons. Does your friend also live in UA? That's just my guess what is happening, there might be some other reason as well. Something as simple as "load balancing" so that all the traffic is not put through the same routers which might get overloaded.
IP 94.244.3.141 is not reachable from Setti and that is why it can't be queried and listed in Masterserver.
#12 Guest_LoLLneSS
Отправлено 18 August 2010 - 08:28 AM
Bad news, but a month ago 2 ips were reachable Thx anyway. Yes my friend is also from UkraineFrom Setti:
1) cmd > ping 91.211.116.21 SETTI ALWAYS get ~35 ping.
2) cmd > ping 94.244.3.141 SETTI ALWAYS get no response.
Here's how traceroute shows the route.traceroute to 91.211.116.21 (91.211.116.21), 30 hops max, 40 byte packets 1 static.193.40.40.188.clients.your-server.de (188.40.40.193) 0.918 ms 0.926 ms 0.951 ms 2 hos-tr4.juniper2.rz10.hetzner.de (213.239.227.225) 0.155 ms 0.174 ms hos-tr2.juniper1.rz10.hetzner.de (213.239.227.161) 0.152 ms 3 213-239-240-230.clients.your-server.de (213.239.240.230) 4.846 ms 4.849 ms 4.836 ms 4 de-cix.netassist.kiev.ua (80.81.192.66) 35.314 ms 35.298 ms 35.299 ms 5 proline-cl-939.netassist.ua (62.205.159.205) 35.295 ms 35.295 ms 35.291 ms 6 slots6.playground.org.ua (91.211.116.21) 35.540 ms 35.644 ms 35.590 msWhat you should see is that the route is very short - only 6 hops. That is because Hetzner is in Germany and has good connections to everywhere in Europe. Same way your hosting company Playground is well connected - thus the route is short. Now look at the 4th router, it's IP 80.81.192.66. Then there's one router between and then your server.
Let's trace your other IP address.traceroute to 94.244.3.141 (94.244.3.141), 30 hops max, 40 byte packets 1 static.193.40.40.188.clients.your-server.de (188.40.40.193) 0.731 ms 0.759 ms 0.785 ms 2 hos-tr1.juniper1.rz10.hetzner.de (213.239.227.129) 0.149 ms 0.176 ms hos-tr3.juniper2.rz10.hetzner.de (213.239.227.193) 0.158 ms 3 213-239-240-230.clients.your-server.de (213.239.240.230) 4.820 ms 4.834 ms hos-bb1.juniper2.ffm.hetzner.de (213.239.240.226) 4.794 ms 4 de-cix.netassist.kiev.ua (80.81.192.66) 35.060 ms 35.066 ms 35.279 ms 5 q9-juniper-gw.netassist.ua (62.205.134.93) 35.624 ms 35.515 ms 35.457 ms 6 * * * 7 * * * ...This trace never completes as the router at 6th point doesn't reply anything to the "traceroute query". It doesn't forward the query forward either because routers after that don't reply anything either. Now again look at the 4th router on the route. It's the same router as tracing your other IP address. So if the data packet was sent through the same route it would reach your server with only 1 intermediary router. Now because the target IP is different the router is instructed to route the packet elsewhere - to router 6 which doesn't reply. This is the "Cisco routing" they are referring to.
Router 6 might be just connected to Ukrainian own network and the other IP is for international connections. That doesn't make much sense but sometimes hosting companies do weird stuff for weird reasons. Does your friend also live in UA? That's just my guess what is happening, there might be some other reason as well. Something as simple as "load balancing" so that all the traffic is not put through the same routers which might get overloaded.
IP 94.244.3.141 is not reachable from Setti and that is why it can't be queried and listed in Masterserver.
#13 Guest_LoLLneSS
Отправлено 18 August 2010 - 08:36 AM
#14
Отправлено 18 August 2010 - 09:01 AM
... not reachable from Setti ...IP 94.244.3.141 is not reachable from Setti and that is why it can't be queried and listed in Masterserver.
If I block your IP you can't reach Setti. It has nothing to do with GameTracker or GameMonitor.
#15 Guest_LoLLneSS
Отправлено 18 August 2010 - 09:11 AM
#16
Отправлено 18 August 2010 - 09:40 AM
http://css.setti.inf...11.116.21:27022
#17 Guest_LoLLneSS
Отправлено 18 August 2010 - 05:39 PM
I contacted them I just get answers like the problem is in setti configuration and we didn't changed anything when our servers stopped being monitored. Yes it's full now with 14 players, but I'm planing to take it to 32 slots when this problem would be solved. K1ller you are a great guy, listening to my problems, and if you would try to help in my problem like to add server 94.244.3.141:27022 that would really amazing. Just try that pleaseI think you should contact your hosting company and ask why they have such a configuration. Your server seems to be extremely popular just as it is now so let's just leave it that way.
http://css.setti.inf...11.116.21:27022
#18
Отправлено 18 August 2010 - 06:22 PM
I explored more this problem and your other IP is indeed reachable from other places. We have two servers at Hetzner in different locations and neither one can connect to your IP (94.244.3.141). From other servers it's possible to ping both of your servers.I contacted them I just get answers like the problem is in setti configuration
How does traceroute look for you to 94.244.3.141? It's a bit strange that there seem to be two replies from 94.244.3.141 when tracerouting it:
... 5 5 ms 62 ms 5 ms ae1-10.bbr2.hel1.fi.eunetip.net 213.192.191.49] 6 41 ms 41 ms 41 ms as0-0.bbr1.ams1.nl.eunetip.net 213.192.191.226] 7 48 ms 48 ms 48 ms amsix.ett.com.ua [195.69.145.183] 8 72 ms 72 ms 72 ms 80.93.127.197.ett.ua [80.93.127.197] 9 72 ms 72 ms 72 ms 80.93.125.122.ett.ua [80.93.125.122] 10 73 ms 73 ms 73 ms 94.244.3.141 11 73 ms 73 ms 72 ms 94.244.3.141
For completeness' sake here's the traceroute to the 91.211.116.21:
... 5 6 ms 5 ms 90 ms ae1-10.bbr2.hel1.fi.eunetip.net 213.192.191.49] 6 41 ms 41 ms 41 ms as0-0.bbr1.ams1.nl.eunetip.net 213.192.191.226] 7 80 ms 48 ms 48 ms amsix.ett.com.ua [195.69.145.183] 8 72 ms 72 ms 72 ms 80.93.127.197.ett.ua [80.93.127.197] 9 73 ms 76 ms 72 ms 80.93.125.122.ett.ua [80.93.125.122] 10 75 ms 73 ms 74 ms 94.244.0.154 11 74 ms 73 ms 73 ms slots6.playground.org.ua [91.211.116.21]
#19 Guest_LoLLneSS
Отправлено 18 August 2010 - 06:55 PM
1 * * * Превышен интервал ожидания для запроса. 2 32 ms 32 ms 32 ms 10.50.19.34 3 32 ms 32 ms 97 ms 246-95-207-82.ip.ukrtel.net [82.207.95.246] 4 34 ms 32 ms 32 ms 194.44.35.70 5 34 ms 32 ms 32 ms delta2.lecos.net.ua [195.78.59.202] 6 32 ms 34 ms 32 ms 94.244.3.141 7 32 ms 34 ms 32 ms 94.244.3.14191.211.116.21
1 * * * Превышен интервал ожидания для запроса. 2 32 ms 32 ms 32 ms 10.50.19.10 3 169 ms 173 ms 169 ms war-b1-link.telia.net [213.248.92.117] 4 196 ms 196 ms 198 ms ffm-bb2-link.telia.net [80.91.250.107] 5 196 ms 196 ms 194 ms ffm-b2-link.telia.net [80.91.246.219] 6 * 196 ms 196 ms cogent-ic-135155-ffm-b2.c.telia.net [213.248.93.174] 7 206 ms 198 ms 200 ms te2-1.ccr01.muc01.atlas.cogentco.com [130.117.0.166] 8 208 ms 218 ms 212 ms te3-1.ccr01.bts01.atlas.cogentco.com [154.54.36.13] 9 * 228 ms 229 ms te1-1.ccr01.kbp01.atlas.cogentco.com [130.117.49.42] 10 * 104 ms 105 ms 149.6.190.198 11 105 ms 105 ms 103 ms 94.244.0.154 12 106 ms 107 ms 106 ms slots6.playground.org.ua [91.211.116.21]
#20 Guest_LoLLneSS
Отправлено 18 August 2010 - 07:04 PM
Submit server 94.244.3.141:27022 14/14 cs_italy 37 / 0 cstrike www.nstyle-tm.at.ua | Zombie PlagueI don't know what you have done. But I love you man!!! Thx you hundred times, you are the best
0 пользователей читают эту тему
0 пользователей, 0 гостей, 0 скрытых