wingthor

Hey all, I am struggelig with a Arma 2 server, I now there has been a lot of issues with Arma and Gamespy, but after two day by tweaking and googling I now think its time to address the issue. I have tried several server config files on the net, and some of the makes my server appear in the Gamespy list, when they have something between the brackets in the mission class. However I have a clean server with only the default missions innstalled, so when try to connect, I get an error "Can't join". But when cleaning up between the brackets the server won't come up, but I can connect by choosing "Remote connect". I have noticed when connecting remotely it show nothing in the games status, in those that are listed on Gamespy it normally shows either "Playing" or "Creating. When I connect, I get in to the game as I have configured "By a voting". And I can play perfectly. The server also comes up in http://arma2.swec.se/server/data/151362. By runing tcpdump (ip packets sniffer) I can se that the trafic between the Gamespy seems to ok, at least if the communication goes on the ports stated as default. So what is wrong, is this a bug? Does anyone else manage to reproduce this error or it is just mine server? I see in the common server configs, both the address "reportingIP = "armedass.master.gamespy.com";" and "reportingIP = arma2pc.master.gamespy.com";" is used. Which of them is right? Two question then, bug and what is the right reportingIP for an Arma 2 server. Hope someone can help... :) Regards Wingthor

I solved this my self. Regarding the the issues with the config it was I was lazy and used others server.cgf file which was not accurate. Second is that it seems like the server didn't restarted properly. To be precise, the ./arma2server restart, just started up a new instance of the server. Caused me confusion. Aways check that there is only one instance of the server by the ps (linux) command. However, the reason why my server didn't show up in the gamespy server list is that I had configureated the NAT module in iptables, to Destination NAT SPORT only. Evidently the Arma 2 server is a client to the gamespy serverlist. So the arma 2 server sent messages on port 2304 and 2302. Iptables then DNAT-ed it back to the arma2 servers IP adress, causing it to go into an endless lopp. Tell iptables to ignore packets coming from the arma2 servers IP adress. However there was some issues regarding iptables and gamespy which is worthwhile take a closer look into. Among others, gamespy didn't reportet ping, or it was noted "?" or "2500" So I will write a guide thorough guide later, which will show all the ports you need to open in case you have problems with servers behind without a public IP. Regards