Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's up with Arma3 ports? #1240

Closed
UltimateByte opened this issue Jan 12, 2017 · 6 comments · Fixed by #1247
Closed

What's up with Arma3 ports? #1240

UltimateByte opened this issue Jan 12, 2017 · 6 comments · Fixed by #1247
Assignees
Labels
type: feature request New feature or request

Comments

@UltimateByte
Copy link
Contributor

Since only one is required and is set with start parms, then why are they into the cfg file?
And especially, why ERROR! Missing/commented ports in arma3-server.server.cfg error message even exists, since this is absolutely normal for them to be commented?

First time I'm looking into it, and I feel confused, maybe I'm missing something.
So does this guy with this error message http://steamcommunity.com/groups/linuxgsm/discussions/0/144513128846028225/

https://github.com/GameServerManagers/Game-Server-Configs/blob/master/Arma3/server.cfg#L14
https://github.com/GameServerManagers/LinuxGSM/blob/master/Arma3/arma3server#L31
https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/command_details.sh#L521

At first glanc,e I guess port info should come from the main port and some additions set here
https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/info_config.sh#L335

@dgibbs64
Copy link
Member

Ideally parms should not be used and instead the config should be used. I recommend testing arma 3 with the port being using from the config and remove the parms port="2302"

We should only use parms if we have no choice. Make things less complicated

@UltimateByte
Copy link
Contributor Author

OK, thx, will test it right now.

@UltimateByte
Copy link
Contributor Author

UltimateByte commented Jan 12, 2017

So test 1) Remove port start parameter, and start with default commented config

23:44:55 Game Port: 2302, Steam Query Port: 2303
23:44:55 Initializing Steam server - Game Port: 2302, Steam Query Port: 2303
Arma 3 Console version1.66.139586  : port 2302

Test 2) Try altering config file:

// Server Port
serverport=2310;

// Steam Master Port
steamport=2320;

steamqueryport=2330;

Result:

23:47:18 Game Port: 2302, Steam Query Port: 2303
23:47:18 Initializing Steam server - Game Port: 2302, Steam Query Port: 2303
Arma 3 Console version1.66.139586  : port 2302

Arma3 don't care about ports set within config files.

Test 3) Remove anything about ports in cfg file, and try with port start parms

23:49:13 Game Port: 2330, Steam Query Port: 2331
23:49:13 Initializing Steam server - Game Port: 2330, Steam Query Port: 2331
Arma 3 Console version1.66.139586  : port 2330

Conclusion: Sadly, we have to remove port config from config file and use start parameters only.

@UltimateByte
Copy link
Contributor Author

Also, port info is broken atm.

ERROR! Missing/commented ports in arma3-server.server.cfg.

DESCRIPTION              DIRECTION  PORT  PROTOCOL
> Game                   INBOUND    2302  udp
> Steam: Query           INBOUND    udp
> Steam: Master traffic  INBOUND    udp

Will be a hotfix, since it's quite critical for ARMA IMO, and also, because we need to make sure to alter cfg file at the same time as the master commit.

@UltimateByte
Copy link
Contributor Author

UltimateByte commented Jan 14, 2017

Proper output:

Ports
==================================================================================================
Change ports by editing the parameters in:
arma3server

Useful port diagnostic command:
netstat -atunp | grep arma3server

DESCRIPTION              DIRECTION  PORT  PROTOCOL
> Game                   INBOUND    2302  udp
> Steam: Query           INBOUND    2303  udp
> Steam: Master traffic  INBOUND    2304  udp
> Undocumented Port      INBOUND    2305  udp

Awaiting merge.

@lock
Copy link

lock bot commented Jul 19, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature request New feature or request
Projects
None yet
2 participants