[SOLVED] csprog.dat hangs up

Hello,
I encounter an issue with xonotic 0.6 in multiplayer.
When I join a server, no problem, maps are downloaded very fast. But when it comes the turn to download csprog.dat, it simply hangs up.
Download rate is at this moment of 0bytes/s , and sometimes for a very short moment at 311bytes/s. But event when csprog.dat is downloaded at 100%, nothing happens, I still have the black screen of downloads with the grey bar.

I'm running xonotic 0.6 on a debian wheezy 64 bits.

Do I have to open UDP port? or is it totally unrelated?

You don't have to open any ports, but if you have a firewall, do check its logs.

On which server does this happen? Have you tried other servers?

Yes I tried different servers, but the problem is recurrent.
What is weird is that I have no problem for maps downloads.
My firewall isn't blocking anything. To be sure, I tried to remove every iptables rules and restarted xonotic : csprog.dat still refuses to be downloaded.

This is probably irrelevant, but where did you download Xonotic?

Anyway, csprogs.dat is sent by the server to the client through an udp link, unlike maps which are most of the time served from an http or ftp server. I really don't know why that transfer would fail though...

Before trying some in-depth troubleshooting (which I'm not sure I'm capable of assisting), perhaps you should consider giving autobuilds a try. Those are snapshots of the development version, maybe they don't suffer from the issue you're experiencing.

Well, I downloaded it here : http://dl.xonotic.org/xonotic-0.6.0.zip

I should have told it before : I tried with a git build, but the problem is the same.

Do I need any program to handle these udp links?

Thank you for taking time to solve this.

No, you don't need anything, it works out of the box. Something's preventing the file transfer but I really don't know what that could be...

Can you try with a fresh profile? To do that, you can simply rename your $HOME/.xonotic/data/ directory to something else and start the game. It will create a new personal data directory with default configs, try it then. When you're done you can remove the new data directory and rename the backup back to $HOME/.xonotic/data/.

Already tried, but the problem was still here.

Not sure if it was you but a couple of people mentioned this on my FT server yesterday. They had issues with downloading cprogs.

Is there something I can look for in my server logs?

It possible, I was connected with the "NULL" pseudo. You have something in logs?

On my own, what kind of information can I give to fix this issue (or report a bug)?

A packet dump could be useful. Do you know about Wireshark? If not, this might get too tricky, which is why I avoided mentioning it until now...

You would have to filter the relevant packets, otherwise you might leak personal information and have a much bigger file than is needed.

I heard about it, but never actually used it... However I can read any tutorial under your advice

I don't really have any resource to suggest, I just kind of picked it up. It's not that hard to use actually, so any tutorial should do.

The point is to start capturing packets on your network interface before you join the server, and then to isolate the packets between you and the server. One way to do that is to find one of the many UDP packets that *follow* the connection to the server and right click on it and set a "Conversation Filter" to IP. I guess you could then export the displayed packets (make sure "displayed" is checked, instead of "captured", otherwise you might be exporting sensitive data).

I tried to get some info with tcpdump (which seems to be quite equivalent to wireshark from tutorials).
Here is the log from the moment csprog.dat should be downloaded :

http://paste.debian.net/9022/

The thing I understand is there is an udp problem. But how can I fix it?

Yep, seems you're hitting a barrier somewhere. Are you sure you're not behind any firewall? Be it in your PC, or in your router or modem even (try to enable logging on the router if there is such a thing?)

I think your log there will be useful. I don't really know how to troubleshoot further though... Double check your network!

I'll check again, but I promise I tried after opening router and computer firewalls.

This problem happens in some others multiplayers games (openarena, quake live), and it's really surprising the number of unresolved topic you can find on the web when you type "awaiting gamestate" in a search engine!

Well, the problem is still here when averything is open.
As I said, it's a recurrent problem on several multiplayer games : https://www.google.fr/search?q=awaiting+...cher&hl=fr

Have you checked the logs of the firewalls? That can still help.

Are you aware of your ISP blocking some ports or kinds of traffic?

Do you have any other OS that you could test this on? Other hardware (computer AND networking hardware)? You should try as many alternatives as you can, to try to single out the source of the problem. If nothing works, perhaps the problem is with your ISP.

Yes I checked firewall logs. Only blocked packets are unrelated to xonotic (port 80 for most)

I'm connected to internet with OVH, and I never heard about ports blocking. But I'll look after more informations.

No, I don't have other OSes, and I don't think it could help, because I was able to play xonotic correctly last week, this problem is very recent.

Here some more logs

- from router firewall :


- From tcpdump (huge file!)
http://pastebin.yeuxdelibad.net/?699c407...jk7J4nmrrA=

There is something in these logs I don't understand :

Code:

10:53:07.409434 IP 192.168.1.68 > srv02.xonotic.org: ICMP 192.168.1.68 udp port 56992 unreachable, length 61
10:53:07.412132 IP srv02.xonotic.org.27000 > 192.168.1.68.56992: UDP, length 25
10:53:07.412188 IP 192.168.1.68 > srv02.xonotic.org: ICMP 192.168.1.68 udp port 56992 unreachable, length 61
10:53:07.413248 IP srv02.xonotic.org.27000 > 192.168.1.68.56992: UDP, length 25
10:53:07.413303 IP 192.168.1.68 > srv02.xonotic.org: ICMP 192.168.1.68 udp port 56992 unreachable, length 61

The few I understand is that the server isn't listening on the ports used via UDP.

Why every servers would stop listening one day?

There is something in these logs I don't understand :

Code:

10:53:07.409434 IP 192.168.1.68 > srv02.xonotic.org: ICMP 192.168.1.68 udp port 56992 unreachable, length 61
10:53:07.412132 IP srv02.xonotic.org.27000 > 192.168.1.68.56992: UDP, length 25
10:53:07.412188 IP 192.168.1.68 > srv02.xonotic.org: ICMP 192.168.1.68 udp port 56992 unreachable, length 61
10:53:07.413248 IP srv02.xonotic.org.27000 > 192.168.1.68.56992: UDP, length 25
10:53:07.413303 IP 192.168.1.68 > srv02.xonotic.org: ICMP 192.168.1.68 udp port 56992 unreachable, length 61

The few I understand is that the server isn't listening on the ports used via UDP.

Why every servers would stop listening one day?

No, what it means is that your client can't reach that UDP port. It could be a problem with the server, but it could also be a problem on your LAN or anywhere inbetween.

What kind of router / box do you have? Can you search the internet if others are having trouble with online gaming with the same equipment?

I searched this way, but I didn't find anything interesting yet...

My router is a Thomson Gateway TG784n , software release : 10.2.1.4

Oh wait, I had misread this all. I blame my bad knowledge of networking.

What's happening here is that your system is indeed getting UDP packets to a certain port, but it sends back an ICMP packet to the server telling it that that port can't be reached.

Do you think you could focus on these specific packets and make tcpdump dump the entire packet sequence instead of just a summary of it?

Something's wrong with networking on your PC I think. Can you post a full log of Xonotic from startup to trying to download csprogs.dat? Perhaps DP can't bind that port and it ends up being unreachable? Can you try this while it's trying to download?

Code:

netstat -4lp

and post the results?

Here is the log of Xonotic :
http://pastebin.fr/27677

Here is the result of tcpdump (I used this command, please correct me if necessary : tcpdump -i wlan0 -vv -X udp or icmp )
http://pastebin.fr/27678

And last, the result of netstat :

Code:

Connexions Internet actives (seulement serveurs)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        PID/Program name
tcp        0      0 localhost:domain        *:*                     LISTEN      4867/unbound    
tcp        0      0 localhost:8118          *:*                     LISTEN      5026/privoxy    
tcp        0      0 localhost:ipp           *:*                     LISTEN      4734/cupsd      
tcp        0      0 *:smtp                  *:*                     LISTEN      5159/master    
tcp        0      0 *:9977                  *:*                     LISTEN      5095/python    
tcp        0      0 localhost:8953          *:*                     LISTEN      4867/unbound    
tcp        0      0 localhost:8123          *:*                     LISTEN      4515/polipo    
tcp        0      0 localhost:6600          *:*                     LISTEN      4985/mpd        
udp        0      0 *:39399                 *:*                                 7590/dhclient  
udp        0      0 *:19743                 *:*                                 7404/dhclient  
udp        0      0 localhost:domain        *:*                                 4867/unbound    
udp        0      0 *:bootpc                *:*                                 7404/dhclient  
udp        0      0 *:bootpc                *:*                                 7590/dhclient  
udp        0      0 *:ipp                   *:*                                 4734/cupsd      
udp        0      0 *:9977                  *:*                                 5095/python    
udp        0      0 *:51033                 *:*                                 6511/xonotic-linux6

Thanks a lot for your help!

Okay, first of all you should update to Xonotic 0.7 and see if the problem still occurs. You can use the rsync updater as described on the download page to save bandwidth: http://www.xonotic.org/download/

If the problem still happens, I'll try to forward your information to someone who's more knowledgeable than me about this. I think what you provided here will be very helpful.