I recently changed my network configuration and now Quakespasm is unable to join netquake servers. It shows "connection accepted", then "3 demos in loop", occasionally printing "server to client keepalive".
I read up about this and it seems to be quite a well known problem.
http://quakeone.com/forums/quake-help/general-help/180-cant-connect-server.html
It seems that quakespasm has one part of the "NAT fix" that originated in Proquake, but certain NAT configurations cause that one line fix to not be enough for certain (probably bizarre) network configurations. I can connect to the same server (quake.shmack.net:26002) with both Darkplaces and Quore. I can't get Qrack to compile at the moment so couldn't test with that.
I have no idea of the specific NAT configuration that causes this issue. I can tell you that my router is a Zyxel P-660HW-T1. It doesn't have any special configuration besides a few unrelated ports forwarded.
I believe that my issue with Quakespasm is likely the same as the one this poster experiences with DirectQ: http://quakeone.com/forums/quake-help/general-help/5607-directq-mp-problems.html
Running SVN trunk r637 on Linux amd64.
Does the attached patch help?
(I extracted the bits from old darkplaces revs. 2870 & 2872:
http://svn.icculus.org/twilight?view=rev&revision=2870
http://svn.icculus.org/twilight?view=rev&revision=2872 )
No, I still get the same behaviour when building with that patch.
Back to drawing board then. This might not be fixed truly+compatibly without some major work.