GPZ pings and packet loss
-
Grimmwolf_GB
- Posts: 3711
- Joined: Wed Jul 02, 2003 7:00 am
- Location: Germany
- Contact:
Grimmwolf_GB wrote:QUOTE (Grimmwolf_GB @ Feb 2 2010, 01:24 PM) Has it changed since the server was moved?
GPZ is in the same camp as the rest of the servers now for me since the move. I get good to decent pings most of the time, the rest I am sure it's a local ISP or cloud issue (and possibly a NIC issue). I general get 50ms-150ms when things are *good* and when things are bad it's across all servers (been testing that the last few nights).
Questions: how many people that have lag issues are using on-board nics? I think I have an intel nic around here that I will try installing.
Th
Hyro wrote:QUOTE (Hyro @ Feb 22 2010, 01:08 PM) You grasp subtlety like a quadriplegic grasps his dick. Never or with grudging help.
Can someone please explain this to me?
Right now GPZ is unplayable for me, mostly due to packet losses.
Code: Select all
C:\>tracert server.german-borg.de
Tracing route to server.german-borg.de [217.23.13.160]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 32 ms 32 ms 32 ms bbras-llu-kln-06L0.forthnet.gr [194.219.231.61]
3 34 ms 33 ms 32 ms core-kln-01-Gi6-0-0.forthnet.gr [62.1.37.129]
4 * * * Request timed out.
5 164 ms 163 ms 161 ms so-0-2-2.fra22.ip4.tinet.net [77.67.74.225]
6 118 ms 118 ms 119 ms xe-2-2-0.ams10.ip4.tinet.net [89.149.186.201]
7 119 ms 119 ms 120 ms caiw-diensten-gw.ip4.tinet.net [77.67.72.134]
8 117 ms 118 ms 118 ms cn-nawij-is-cr40-ten1-1.caiw.net [62.45.254.22]
9 119 ms 119 ms 118 ms cn-nawij-is-cr40-wrldstrm.kabelfoon.nl [62.45.63
.222]
10 118 ms 120 ms 118 ms 217.23.13.160
Trace complete.
C:\>ping server.german-borg.de
Pinging server.german-borg.de [217.23.13.160] with 32 bytes of data:
Reply from 217.23.13.160: bytes=32 time=121ms TTL=113
Reply from 217.23.13.160: bytes=32 time=118ms TTL=113
Reply from 217.23.13.160: bytes=32 time=119ms TTL=113
Reply from 217.23.13.160: bytes=32 time=120ms TTL=113
Ping statistics for 217.23.13.160:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 118ms, Maximum = 121ms, Average = 119ms
C:\>





" There is good in everyone. You just need the eyes for it. "
your pings and tracert is fine. No indication that there's any loss from the data presented. Perhaps it's just a random peak-traffic thing? (Playing at a different time of the day than when you took those samples?)
If you're behind a router, have a look at your settings to make sure that you're not giving anything else a higher priority over Allegiance. (QoS or Quality of Service can sometimes muck up an otherwise perfectly good connection.)
If you're behind a router, have a look at your settings to make sure that you're not giving anything else a higher priority over Allegiance. (QoS or Quality of Service can sometimes muck up an otherwise perfectly good connection.)
-
Grimmwolf_GB
- Posts: 3711
- Joined: Wed Jul 02, 2003 7:00 am
- Location: Germany
- Contact:
It looks like a problem between the networks of your ISP and Tiscali carrier:
The route back to your PC looks fine.
Code: Select all
Tracing route to 77.49.xxx.xxx.dsl.dyn.forthnet.gr [77.49.xxx.xxx]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 217.23.13.1
2 <1 ms <1 ms <1 ms cn-nawij-is-cr40-te43.kabelfoon.nl [62.45.63.221
]
3 1 ms 1 ms 1 ms cn-asd-kbw-cr10-ten1-3.caiw.net [62.45.254.21]
4 1 ms 1 ms 1 ms cn-asd-kbw-cr11-ten1-1.caiw.net [62.45.254.26]
5 1 ms 1 ms 2 ms xe-7-1-0-0.ams10.ip4.tinet.net [77.67.72.133]
6 8 ms 43 ms 8 ms xe-5-3-0.fra23.ip4.tinet.net [89.149.187.6]
7 54 ms 54 ms 54 ms forthnet-gw.ip4.tinet.net [77.67.74.174]
8 61 ms 61 ms 61 ms core-kln-01G5-0-0.forthnet.gr [212.251.94.17]
9 61 ms 61 ms 61 ms bbras-llu-kln-06.forthnet.gr [62.1.37.141]
10 * * * Request timed out.The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
This is an intermittent thing across all servers.Yes,the internet is broken,and I believe it has to do with the conficker attacks of 08.I may be wrong,but the internets servers (all of themrandomly) are having these issues.Google and YouTube are getting around it by using honey pot front end gatway machines that switch out on a regular basis.

-
Grimmwolf_GB
- Posts: 3711
- Joined: Wed Jul 02, 2003 7:00 am
- Location: Germany
- Contact:
I don't know how to reply to this... It is wrong on so many levels...raumvogel wrote:QUOTE (raumvogel @ Mar 2 2010, 08:36 PM) This is an intermittent thing across all servers.Yes,the internet is broken,and I believe it has to do with the conficker attacks of 08.I may be wrong,but the internets servers (all of themrandomly) are having these issues.Google and YouTube are getting around it by using honey pot front end gatway machines that switch out on a regular basis.
I talked to my ISPs helpline and they were aware of the problem. They said that there is a general problem with out-of-the-country traffic.
Since most of us that experience the packet loss issue are from the south east part of Europe (Greece, Turkey, etc) I believe that all these incidents are related to some line somewhere that is broken affecting all of us. So, GPZ administrators can't do something about it. Neither can we. We just have to wait and see.
Since most of us that experience the packet loss issue are from the south east part of Europe (Greece, Turkey, etc) I believe that all these incidents are related to some line somewhere that is broken affecting all of us. So, GPZ administrators can't do something about it. Neither can we. We just have to wait and see.
Last edited by parcival on Fri Mar 05, 2010 2:17 pm, edited 1 time in total.






" There is good in everyone. You just need the eyes for it. "