kptkonrad 0 Posted May 26, 2020 Hi everyone, I've been attempting to install and run an Arma 3 server off of my Linux server for about a week now and I seem to be running into a wall with my configuration. I have the server installed through LinuxGSM and that seems to be working correctly, the server launches and I can see/connect to it, albeit only via the LAN IP, not the WAN IP (also the password param in the config file doesn't seem to be working correctly but thats another issue for another day), and as such anyone trying to connect from outside my LAN can't. This seems to be a port forwarding issue because when I check what ports are active and listening on my linux machine, ports 2302-2306 are being used by the Arma 3 Server, but they are not listening and nothing I do makes them listen whether I try to open the ports from my router diagnostics or through commandline on the server itself (through iptables). I can't seem to find any tutorials that solve the issue either so I figured I'd ask myself. Thanks for any help! Share this post Link to post Share on other sites
Dedmen 2588 Posted May 27, 2020 Need more details. What are your server start parameters. If you are connecting via LAN, doesn't that mean the Arma ports are actually listening? But you say they are not listening, how can you connect via LAN if they aren't? Do you have a router with NAT infront of your server? Did you forward the ports there too? Share this post Link to post Share on other sites
kptkonrad 0 Posted May 27, 2020 1 hour ago, Dedmen said: Need more details. What are your server start parameters. If you are connecting via LAN, doesn't that mean the Arma ports are actually listening? But you say they are not listening, how can you connect via LAN if they aren't? Do you have a router with NAT infront of your server? Did you forward the ports there too? Start params: ./arma3server -ip=10.0.0.120 -port=2302 -cfg=/home/mac/serverfiles/cfg/arma3server.network.cfg -config=/home/mac/serverfiles/cfg/arma3server.server.cfg -mod= -servermod= -bepath= -autoinit -loadmissiontomemory After starting the Arma 3 server and connecting via LAN and running sudo lsof -i -P -n : COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME arma3serv 5108 mac 933u IPv4 50886 0t0 UDP 10.0.0.120:2304 arma3serv 5108 mac 934u IPv4 50887 0t0 UDP 10.0.0.120:2302 arma3serv 5108 mac 935u IPv4 50888 0t0 UDP 10.0.0.120:2306 arma3serv 5108 mac 936u IPv4 50889 0t0 UDP *:49832 arma3serv 5108 mac 948u IPv4 50039 0t0 UDP 10.0.0.120:2303 arma3serv 5108 mac 950u IPv4 50040 0t0 UDP 10.0.0.120:2305 arma3serv 5108 mac 951u IPv4 50897 0t0 TCP 10.0.0.120:32886->217.147.95.135:443 (CLOSE_WAIT) arma3serv 5108 mac 952u IPv4 50902 0t0 TCP 10.0.0.120:47944->34.200.186.152:443 (CLOSE_WAIT) arma3serv 5108 mac 953u IPv4 51840 0t0 TCP 10.0.0.120:57512->145.239.8.133:2344 (ESTABLISHED) So lsof says they aren't listening, but I am connected via LAN (I can only connect if I type the local IP into the direct connect box, I can't seem to find it through server browser). I do have a router with NAT infront, but I have set ports 2302-2306 to be forwarded. Also, this seems important, specifically the discrepancy between Server IP and Internet IP (also the Server password should be TemporaryPassword but I'm really not sure why it isn't reading the config correctly but as it is I can connect to the server without entering a password): ARMA 3 Server Details ================================= Server name: Konrad's Arma Server Server IP: 10.0.0.120:2302 Internet IP: 172.219.200.105:2302 Server password: Admin TemporaryAdminPassword Admin password: TemporaryAdminPassword Maxplayers: 32 Status: ONLINE Share this post Link to post Share on other sites
Dedmen 2588 Posted May 27, 2020 2 hours ago, kptkonrad said: -ip=10.0.0.120 That looks like a lan IP.. I'd recommend just leaving that out, you only need to specify IP if you have multiple network interfaces. 2 hours ago, kptkonrad said: sudo lsof -i -P -n : I always do netstat -anp Share this post Link to post Share on other sites
kptkonrad 0 Posted May 27, 2020 8 hours ago, Dedmen said: That looks like a lan IP.. I'd recommend just leaving that out, you only need to specify IP if you have multiple network interfaces. I always do netstat -anp Okay, so I went into the config file and changed the start params so they look like this now: ./arma3server -port=2302 -cfg=/home/mac/serverfiles/cfg/arma3server.network.cfg -config=/home/mac/serverfiles/cfg/arma3server.server.cfg -mod= -servermod= -bepath= -autoinit -loadmissiontomemory Yet my issue persists. I can still connect to the server locally through direct connect but if I try to connect using the external IP, nothing happens. I also tried netstat as you suggested and here are my results (after start params were changed and server is running): tcp 32 0 10.0.0.120:33134 217.147.95.135:443 CLOSE_WAIT 9582/./arma3server tcp 32 0 10.0.0.120:56208 35.173.112.19:443 CLOSE_WAIT 9582/./arma3server udp 0 0 0.0.0.0:2302 0.0.0.0:* 9582/./arma3server udp 0 0 0.0.0.0:2303 0.0.0.0:* 9582/./arma3server udp 0 0 0.0.0.0:2304 0.0.0.0:* 9582/./arma3server udp 0 0 0.0.0.0:2305 0.0.0.0:* 9582/./arma3server udp 0 0 0.0.0.0:2306 0.0.0.0:* 9582/./arma3server Notice again there is no LISTEN state on any of the ports. Share this post Link to post Share on other sites
Dedmen 2588 Posted May 28, 2020 If lan works, that means the server is listening correctly. If exernal IP doesn't work, your port forwarding on your external router is probably not correct. Don't have any further ideas. Share this post Link to post Share on other sites
