starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #1593] Give an option to omit -ip start param #1243

New issue

Closed

opened 2026-02-27 02:56:05 +03:00 by kerem · 8 comments

kerem commented

2026-02-27 02:56:05 +03:00

Owner

Originally created by @marlonrichert on GitHub (Aug 25, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1593

Because if you run a Steam Source server (for example, TF2) with the -ip (or +ip) param, it will not show up in the LAN browser on the client: http://www.fusionnetwork.us/index.php/articles/general-tutorials/steam-fix-lan-server-not-showing-up-in-lan-server-browser/

Originally created by @marlonrichert on GitHub (Aug 25, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1593 Because if you run a Steam Source server (for example, TF2) with the -ip (or +ip) param, it will not show up in the LAN browser on the client: http://www.fusionnetwork.us/index.php/articles/general-tutorials/steam-fix-lan-server-not-showing-up-in-lan-server-browser/

kerem closed this issue

2026-02-27 02:56:05 +03:00

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@UltimateByte commented on GitHub (Aug 27, 2017):

You can remove the start parameter manually into your lgsm config file. (as easy as a setting)

@UltimateByte commented on GitHub (Aug 27, 2017): You can remove the start parameter manually into your lgsm config file. (as easy as a setting)

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@marlonrichert commented on GitHub (Aug 27, 2017):

@UltimateByte

In _default.cfg, there is ip="0.0.0.0", which is passed to Source's -ip param (where LGSM automagically replaces 0.0.0.0 with you actual IP address). The only way I see to remove the -ip param is override the entirety of this:

fn_parms(){
parms="-game tf -strictportbind -ip ${ip} -port ${port} +clientport ${clientport} +tv_port ${sourcetvport} +map ${defaultmap} +sv_setsteamaccount ${gslt} +servercfgfile ${servercfg} -maxplayers ${maxplayers}"
}

Yes, that works, but if I override that entire thing there, I will also automatically be overriding any future updates to that construct. I would like there to be an easier way that is more forward compatible.

@marlonrichert commented on GitHub (Aug 27, 2017): @UltimateByte In `_default.cfg`, there is `ip="0.0.0.0"`, which is passed to Source's `-ip` param (where LGSM automagically replaces `0.0.0.0` with you actual IP address). The only way I see to remove the `-ip` param is override the entirety of this: ``` fn_parms(){ parms="-game tf -strictportbind -ip ${ip} -port ${port} +clientport ${clientport} +tv_port ${sourcetvport} +map ${defaultmap} +sv_setsteamaccount ${gslt} +servercfgfile ${servercfg} -maxplayers ${maxplayers}" } ``` Yes, that works, but if I override that entire thing there, I will also automatically be overriding any future updates to that construct. I would like there to be an easier way that is more forward compatible.

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@UltimateByte commented on GitHub (Aug 27, 2017):

This is because _default.cfg is default, therefore you cannot edit it directly. You need to pass parameters from this file to your instance config file, as per documentation.
https://github.com/GameServerManagers/LinuxGSM/wiki/LinuxGSM-Config-Files#how-to-get-started-with-the-new-config-files-system

@UltimateByte commented on GitHub (Aug 27, 2017): This is because _default.cfg is default, therefore you cannot edit it directly. You need to pass parameters from this file to your instance config file, as per documentation. https://github.com/GameServerManagers/LinuxGSM/wiki/LinuxGSM-Config-Files#how-to-get-started-with-the-new-config-files-system

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@marlonrichert commented on GitHub (Aug 27, 2017):

Yes, in tf2server.cfg, I am overriding fn_parms(){ parms="…" }. That means, however, that if fn_parms(){ parms="…" } gets updated somehow in defaults.cfg, I will not get any of those changes on my server. I mean, I am this way overriding all start params, when I only want to remove the -ip param specifically. If later any start params in _default.cfg are added or removed, those changes will no longer cascade to me.

Or am I missing something here? Is there some way in which I can remove the -ip param in tf2server.cfg without overriding that fn_parms(){ parms="…" } construct?

@marlonrichert commented on GitHub (Aug 27, 2017): Yes, in `tf2server.cfg`, I am overriding `fn_parms(){ parms="…" }`. That means, however, that if `fn_parms(){ parms="…" }` gets updated somehow in `defaults.cfg`, I will not get any of those changes on my server. I mean, I am this way overriding _all_ start params, when I only want to remove the `-ip` param specifically. If later any start params in `_default.cfg` are added or removed, those changes will no longer cascade to me. Or am I missing something here? Is there some way in which I can remove the `-ip` param in `tf2server.cfg` without overriding that `fn_parms(){ parms="…" }` construct?

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@ghost commented on GitHub (Aug 27, 2017):

There isn't a logical way since the scripts pull from the custom configuration then from the default. If the flags exist in the custom config then they are ignored in the _default.cfg in their entirety.

IMO, you probably shouldn't rely on the default string to run things if you want it to be consistent anyway. If you want to research the flags of it, you should check out the other command line options from the wiki.

@ghost commented on GitHub (Aug 27, 2017): There isn't a logical way since the scripts pull from the custom configuration then from the default. If the flags exist in the custom config then they are ignored in the `_default.cfg` in their entirety. IMO, you probably shouldn't rely on the default string to run things if you want it to be consistent anyway. If you want to research the flags of it, you should check out the [other command line options](https://wiki.teamfortress.com/wiki/Linux_dedicated_server#Create_a_shell_script_to_run_the_server) from the wiki.

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@ghost commented on GitHub (Aug 27, 2017):

I also wonder if your server is meant to be internet facing? If so, clients should be able to use whatever external IP or dynamic DNS name given to find and connect as well as use the local IP of the host machine and add the server to their favorites if it's LAN only.

@ghost commented on GitHub (Aug 27, 2017): I also wonder if your server is meant to be internet facing? If so, clients should be able to use whatever external IP or dynamic DNS name given to find and connect as well as use the local IP of the host machine and add the server to their favorites if it's LAN only.

kerem commented

2026-02-27 02:56:05 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Sep 20, 2017):

Removing the -ip from the parms is the best way. parms rarely get updated so I wouldnt worry at all.

@dgibbs64 commented on GitHub (Sep 20, 2017): Removing the -ip from the parms is the best way. parms rarely get updated so I wouldnt worry at all.

kerem commented

2026-02-27 02:56:06 +03:00

Author

Owner

@lock[bot] commented on GitHub (Sep 20, 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[bot] commented on GitHub (Sep 20, 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.

kerem referenced this issue

2026-02-27 03:54:00 +03:00

[PR #1243] [MERGED] Fix for config issues (ark & global) #3297