linkdead - tcpdump (slim chance that this might be of use to devs)

[Guinness2702]

In case it is of any use, the following is a tcpdump of what happens, in one of my repeated, random linkdead occurances.

My network is as follows

192...3   <-cable->   192...1(linux firewall) 10...1    <-cable->  10...2 (adslmodem) x.x.x.x <-adsl.line-> internet

192...3 - WinXP box, running the game
192...1 - Internal network side of my linux box (eth0)
10...1 - External network side of my linux box (eth1)
10...2 - Linux box facing side of ADSL modem
x.x.x.x - my public IP address

The linux box has a firewall/router with NAT/IP_MASQ inbetween 192...1 & 10...1, which includes port forwarding of traffic from the external interface of UDP/13331 to 192...3

Note that in the following dump, eth1 is an alias for 10...1
Also note that the dump is restricted to traffic in/out on eth1, and was obtained on the linux box


03:17:11.773247 203.81.47.91.7354 > eth1.4399: udp 195 (DF)
03:17:11.822804 eth1.4399 > 203.81.47.91.7354: udp 15
03:17:11.823029 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:11.881177 203.81.47.91.7354 > eth1.4399: udp 60 (DF)
03:17:11.977756 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:11.991077 203.81.47.91.7354 > eth1.4399: udp 135 (DF)
03:17:12.097028 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:12.108927 203.81.47.91.7354 > eth1.4399: udp 195 (DF)
03:17:12.147749 eth1.4399 > 203.81.47.91.7354: udp 15
03:17:12.249490 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:12.350891 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:12.554191 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:12.655570 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:12.850220 203.81.47.91 > 192.168.0.3: icmp: 203.81.47.91 udp port 7354 unreachable
03:17:12.861256 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:12.952063 203.81.47.91 > 192.168.0.3: icmp: 203.81.47.91 udp port 7354 unreachable
03:17:12.964587 eth1.4399 > 203.81.47.91.7354: udp 135
03:17:13.159776 203.81.47.91 > 192.168.0.3: icmp: 203.81.47.91 udp port 7354 unreachable
03:17:13.160346 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:13.263927 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:13.265710 203.81.47.91 > 192.168.0.3: icmp: 203.81.47.91 udp port 7354 unreachable
03:17:13.438788 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:13.455510 203.81.47.91 > 192.168.0.3: icmp: 203.81.47.91 udp port 7354 unreachable
03:17:13.542312 eth1.4399 > 203.81.47.91.7354: udp 60
03:17:13.559394 203.81.47.91 > 192.168.0.3: icmp: 203.81.47.91 udp port 7354 unreachable

[ronxena]

203.81.47.91 (laanx.fragnetics.com), udp port 7354 is the address of the server (the server is using udp protocol to communicate with your client).

I think link-dead has nothing to do with the network connection. This currently occurs when the server crashes - so the client gets no answer from server and assumes a \"link-dead\"... in case of server crash no application has opened a port udp 7354, and these are the messages you get.

About 30-45 secs after the crash the server is automatically restarted and you can relogin.

Currently the server stability is not \"optimal\" - server crashes about each 5-10 minutes, but I think developers are already working on this. At least I hope so ;-)