Official forums for BZFlag.org

Players from NZ and Australia are used to being very laggy on most servers ...

Well, no more! bz.gonzul.net is located in Dunedin, NZ on a 1MB (burst to 2MB) connection, running on a low-spec desktop.

Currently it hosts my new map, Yojimbo's Barrier, and a copy of ahs3's Dodge Trainer 2v2.

/report any problems, or PM me here.

Your server seems to have unstable lag. Sometimes I am even worse off there than at a US server.

The Traitor wrote:Your server seems to have unstable lag. Sometimes I am even worse off there than at a US server.

I've seen a couple of /reports about that. My link into FXnet seems to be pretty stable, so the problems are either related to server performance itself, or perhaps to the lack of decent peering between NZ ISPs.

For example, I'm currently on an Xtra connection in Christchurch, 14 hops away from my server, routed via the Auckland Peering Exchange. This pings at around 100ms with occasional spikes up to +200ms, which is quite frankly terrible.

Ping: min/avg/max/med = 84/102/252/94

If you could post or send a traceroute and ping sample, it would help me to figure out where the issue lies, and whether I can fix it or not.

The players have voted with their feet ... seems like no-one can get to the server without suffering lag, so I suspect that my upstream ISP isn't quite up to the job.

I'll try to get another server lined up one day, either directly connected to a peering exchange or on one of the "major" (=non-peering) ISPs.

But in the meantime, I'll be shutting down. It was fun

If you could post or send a traceroute and ping sample, it would help me to figure out where the issue lies, and whether I can fix it or not.

From my server in Stratford, CT:

40 packets transmitted, 40 received, 0% packet loss, time 39000ms
rtt min/avg/max/mdev = 250.350/256.292/261.723/2.327 ms

From my desktop computer in southern NY:

Minimum = 265ms, Maximum = 319ms, Average = 269ms

Traceroute from my server:

traceroute to wic.gonzul.net (120.89.80.94), 30 hops max, 40 byte packets
1 heekinlaw.com (65.18.172.2) 0.709 ms 0.464 ms 0.429 ms
2 69.94.3.5 (69.94.3.5) 0.323 ms 0.411 ms 0.355 ms
3 69.182.114.205 (69.182.114.205) 2.713 ms 2.738 ms 2.225 ms
4 bb2-g8-0-1.mrdnct.sbcglobal.net (151.164.42.56) 124.281 ms 3.365 ms 3.008 ms
5 151.164.95.244 (151.164.95.244) 78.958 ms 79.371 ms 78.980 ms
6 Gi5-2.gw1.sjc1.asianetcom.net (206.223.116.143) 75.811 ms 76.102 ms 75.987 ms
7 gi15-1.gw1.akl1.asianetcom.net (202.147.55.225) 227.846 ms 226.527 ms 226.189 ms
8 FXN-0001.GW1.AKL1.asianetcom.net (203.192.167.162) 224.807 ms 225.028 ms 225.082 ms
9 GigabitEthernet0-2-210.fxak1-rt2.fx.net.nz (202.53.187.14) 226.647 ms 226.809 ms 226.790 ms
10 GigabitEthernet0-0-357.fxwn3-rt1.fx.net.nz (202.53.187.9) 234.793 ms 234.826 ms 235.504 ms
11 fxdn1-rt1.fa0-0-60.fx.net.nz (131.203.252.133) 245.765 ms 246.876 ms 245.231 ms
12 131.203.252.138 (131.203.252.138) 247.998 ms 248.397 ms 250.067 ms
13 202.20.97.1 (202.20.97.1) 249.919 ms 248.506 ms 249.738 ms
14 202.49.106.174 (202.49.106.174) 250.061 ms 249.704 ms 254.716 ms
15 120.89.80.94 (120.89.80.94) 253.966 ms 254.366 ms 253.117 ms

From my desktop computer:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 6 ms 5 ms 7 ms 10.132.64.1
3 6 ms 8 ms 6 ms dstswr1-vlan2.rh.whplny.cv.net [67.83.224.33]
4 * * * Request timed out.
5 8 ms 7 ms 7 ms 64.15.8.113
6 10 ms 9 ms 9 ms 64.15.0.193
7 * * * Request timed out.
8 9 ms 9 ms 9 ms 10gigabitethernet1-1.core1.nyc4.he.net [72.52.92.45]
9 18 ms 21 ms 16 ms 10gigabitethernet2-3.core1.ash1.he.net [72.52.92.86]
10 52 ms 49 ms 51 ms 10gigabitethernet1-1.core1.dal1.he.net [72.52.92.61]
11 91 ms 89 ms 90 ms 10gigabitethernet1-2.core1.lax1.he.net [72.52.92.57]
12 79 ms 76 ms 75 ms 216.218.224.126
13 79 ms 77 ms 79 ms po0-1.gw1.lax1.asianetcom.net [202.147.61.157]
14 242 ms 236 ms 237 ms po6-0.gw1.akl1.asianetcom.net [202.147.61.190]
15 620 ms 382 ms 309 ms FXN-0001.GW1.AKL1.asianetcom.net [203.192.167.162]
16 237 ms 240 ms 236 ms GigabitEthernet0-2-210.fxak1-rt2.fx.net.nz [202.53.187.14]
17 245 ms 244 ms 245 ms GigabitEthernet0-0-357.fxwn3-rt1.fx.net.nz [202.53.187.9]
18 252 ms 258 ms 253 ms fxdn1-rt1.fa0-0-60.fx.net.nz [131.203.252.133]
19 252 ms 254 ms 252 ms 131.203.252.138
20 256 ms 255 ms 262 ms 202.20.97.1
21 255 ms 255 ms 257 ms 202.49.106.174
22 299 ms 266 ms 260 ms 120.89.80.94

traceroute to wic.gonzul.net (120.89.80.94), 30 hops max, 40 byte packets
1 heekinlaw.com (65.18.172.2) 0.709 ms 0.464 ms 0.429 ms
2 69.94.3.5 (69.94.3.5) 0.323 ms 0.411 ms 0.355 ms
3 69.182.114.205 (69.182.114.205) 2.713 ms 2.738 ms 2.225 ms
4 bb2-g8-0-1.mrdnct.sbcglobal.net (151.164.42.56) 124.281 ms 3.365 ms 3.008 ms
5 151.164.95.244 (151.164.95.244) 78.958 ms 79.371 ms 78.980 ms
6 Gi5-2.gw1.sjc1.asianetcom.net (206.223.116.143) 75.811 ms 76.102 ms 75.987 ms
7 gi15-1.gw1.akl1.asianetcom.net (202.147.55.225) 227.846 ms 226.527 ms 226.189 ms
8 FXN-0001.GW1.AKL1.asianetcom.net (203.192.167.162) 224.807 ms 225.028 ms 225.082 ms
9 GigabitEthernet0-2-210.fxak1-rt2.fx.net.nz (202.53.187.14) 226.647 ms 226.809 ms 226.790 ms
10 GigabitEthernet0-0-357.fxwn3-rt1.fx.net.nz (202.53.187.9) 234.793 ms 234.826 ms 235.504 ms
11 fxdn1-rt1.fa0-0-60.fx.net.nz (131.203.252.133) 245.765 ms 246.876 ms 245.231 ms
12 131.203.252.138 (131.203.252.138) 247.998 ms 248.397 ms 250.067 ms
13 202.20.97.1 (202.20.97.1) 249.919 ms 248.506 ms 249.738 ms
14 202.49.106.174 (202.49.106.174) 250.061 ms 249.704 ms 254.716 ms
15 120.89.80.94 (120.89.80.94) 253.966 ms 254.366 ms 253.117 ms

That's fine; you have around 80ms to the edge of asianetcom, which is good; then 150ms added to get into NZ, which is expected due to sheer physical distance, and finally 30ms to transit.

I'm more interested in how the average NZ player gets routed into me, as the two biggest ISPs do not peer properly, due to a combination of ignorance and arrogance ...

Hey Yojimbo,

here's my traceroute to your server (I'm in Palmerston North):
linux-bnpo:/ # traceroute bz.gonzul.net
traceroute to bz.gonzul.net (120.89.80.94), 30 hops max, 40 byte packets
1 * * *
2 lns1.inspire.net.nz (203.114.128.240) 100.150 ms 99.516 ms 101.784 ms
3 br1.wix.inspire.net.nz (203.114.147.242) 118.389 ms * 132.324 ms
4 fx3.wix.net.nz (202.7.1.175) 104.650 ms 105.774 ms 105.525 ms
5 fxdn1-rt1.fa0-0-60.fx.net.nz (131.203.252.133) 113.643 ms 113.274 ms 112.216 ms
6 131.203.252.138 (131.203.252.138) 110.547 ms 111.589 ms 109.137 ms
7 202.20.97.1 (202.20.97.1) 110.070 ms 113.852 ms 117.934 ms
8 202.49.106.174 (202.49.106.174) 120.682 ms 115.686 ms 123.966 ms
9 120.89.80.94 (120.89.80.94) 131.878 ms 123.949 ms 120.065 ms
linux-bnpo:/ #

So not that great. But by comparison, here is the trace to my server which is in Auckland:
linux-bnpo:/ # traceroute enuffsaid.co.nz
traceroute to enuffsaid.co.nz (119.47.112.102), 30 hops max, 40 byte packets
1 * * *
2 lns1.inspire.net.nz (203.114.128.240) 103.049 ms 102.351 ms 102.025 ms
3 akl-kingston-br-1 (203.114.147.233) 123.317 ms 111.206 ms 132.077 ms
4 maxnet1.ape.net.nz (192.203.154.86) 110.743 ms 109.478 ms 108.331 ms
5 gi5-1.hsa1.alb.maxnet.net.nz (123.100.64.131) 110.359 ms 109.694 ms 110.762 ms
6 bo0-966.akmn1-br1.webhost.co.nz (202.89.49.117) 110.431 ms 110.139 ms 109.356 ms
7 ln-32-1.openhost.net.nz (119.47.118.15) 118.018 ms 116.605 ms 118.377 ms
8 119.47.112.102 (119.47.112.102) 117.607 ms 117.399 ms 117.080 ms

Not really anything in it.

The annoying thing is that I used to get ping times of around 50ms in game. Oh, and I've seen players recently from Australia with lag times of around 60ms on it! Makes me mad that I'm a hellova lot closer than them to the server and yet have way more lag.

Grans

Grans Remedy wrote:
traceroute to bz.gonzul.net (120.89.80.94), 30 hops max, 40 byte packets
1 * * *
2 lns1.inspire.net.nz (203.114.128.240) 100.150 ms 99.516 ms 101.784 ms

Wow. 100ms just to get through to your ISP ... what are you connecting with? A cheap richard Smith ADSL modem that's overheating?

Grans Remedy wrote: The annoying thing is that I used to get ping times of around 50ms in game.

Well ... if there is some real demand for the machine, I could put it back again I guess. Perhaps with a different map ... ?

Yojimbo wrote: Wow. 100ms just to get through to your ISP ... what are you connecting with? A cheap richard Smith ADSL modem that's overheating?

Lol. No an Allied Telesyn router/firewall. My lag went up when I changed to KDE4/4.1 - it was fine on KDE3.5

Yojimbo wrote: Well ... if there is some real demand for the machine, I could put it back again I guess. Perhaps with a different map ... ?

Well, I really think we need at least one server in NZ - getting constantly lag-kicked is a real pain in the rear. Though sometimes its seems like I'm the only NZ player around...we must be few and far between!

A GU match server in New Zealand or Australia would not be amiss.

Constitution wrote:A GU match server in New Zealand or Australia would not be amiss.

What's involved? I mean, how many players (bandwidth considerations), does anyone need server-level access?

I've never tried playing GU ... always had too much lag. A local server ... hmmm ... I might stand a chance ...

are there any servers in australia at all, im in tasmania and suffer 200 to 300 ping to heaps of servers, only servers with a couple of people on it im able to stay on and not get kicked for lagging.

Constitution wrote:A GU match server in New Zealand or Australia would not be amiss.

There is but it isn't permenant.
Nor is it official, nor does it play anything like the real GU Match Maps, heck, it allows Rogues to play

Yojimbo wrote:

Constitution wrote:A GU match server in New Zealand or Australia would not be amiss.

What's involved? I mean, how many players (bandwidth considerations), does anyone need server-level access?

Bandwidth wise, if your server becomes very popular, I would say you would run through about 200GB/mo. No one else would need access to the server besides you.