Jump to content
Bohemia Interactive Forums

Imhoteph

Member
 View Profile  See their activity

  • Content Count

    2

  • Joined

  • Last visited

  • Medals

Posts posted by Imhoteph

  1. Posted

    Hi folks,

    I have been working on a wasteland server concept for a while now, and we have now been running the main server for a couple of weeks.

    Main attributes:

    - Saves bases/location/gear/vehicles/radars/town ownership across server restart

    - Server restart about 2-3 time / week

    - PvE aspect and city domination system (Capture towns and make them controlled by NPCs on your side)

    - Unique spawn in system (Plane insertion / HALO jump depending on class)

    It was originally based on the v2.7 404Wasteland mod, but has been extensively bugfixed and improved since then.

    Server info:

    Wasteland - Saving/Persistent world - Battlegrounds - US#1 [using Beta]

    IP: 54.235.144.61 PORT: 2532

  2. Posted · Edited by Imhoteph
    Updated with more findings

    Hi,

    I have been spending significant amounts of time this weekend debugging and troubleshooting this issue.

    Server has been rock stable for about 3-4 weeks now, with only intermittent issues for individuals.

    The server runs in Amazon EC2 cloud, and runs on Ubuntu Linux.

    Then, suddenly yesterday morning (Sunday), it stopped working, and I kept getting "NAT Negotiation Failed - Unable to communicate with the server" in the arma2 server log.

    Clients would get the NNThink Error 2, and simply connection failed.

    -----

    Also note that Amazon AWS EC2 servers are equipped with two IP addresses. One internal (That is always the one you have on eth0), and one external (That is a 1:1 NAT relation to the outside world)

    I have all the necessary ports open, (And I control the firewall rules myself) - Just to be clear, I changed nothing on this from Saturday night until Sunday morning.

    -----

    In order to really see what was going wrong, I eventually did a tcpdump on the serverside on the listening port, to see what the server is sending to Gamespy

    
..	.l.._./.....localip0.[b]10.220.85.225[/b].localport.2532.natneg.1.gamename.arma2oapc.publicip.[b]1032907574[/b].publicport.2532.gamever.1.62.102451.hostname.Wasteland - Persistent - Battlegrounds [use remote: 54.235.144.61:2532].mapname..gametype..numplayers.0.numteams.0.maxplayers.60.gamemode.openwaiting.timelimit.0.password.0.param1.0.param2.0.currentVersion.162.requiredVersion.162.mod.Arma 2;Arma 2: Operation Arrowhead;Arma 2: British Armed Forces (Lite);Arma 2: Private Military Company (Lite).equalModRequired.0.gameState.1.dedicated.1.platform.linux.language.65545.difficulty.0.mission..gamename.arma2oapc.sv_battleye.1.verifySignatures.2.signatures.bi;bi2.modhash.PMC v. 1.02;BAF v. 1.03;01a7de012d75ad0f4adb45c885cb9c8ab2636963;.hash.CC15E928BA1CA9CA2CC5658BE67FE4AA642AE47F.reqBuild.0.reqSecureId.1.lat.427391728.lng.427391824....player_.team_.score_.deaths_.....

    Note how the localip is being reported back - This is the internal IP Amazon has given to the machine, which is not reachable from the outside world. The IP on publicIP looks encrypted/hashed in some way to me, as that is not the actual external IP I'm on (That is: 54.235.144.61) I will try to connect to the server with IP/port on my client cmdline now, to see if that will help. *crosses fingers*

    *EDIT*: Direct IP/Port did not really help. I was able to connect using the ARMA2 Beta client however. (Without changing anything on the server)

    I also see incoming packets whenever a player tries to join (Before getting NAT Negotiation Failed)

    I also patched the server to the latest Linux distro that came out about a week ago, with no luck.

    Hopefully this will help some of you out there that are also pulling your hair out.

×