starred/LinuxGSM

Fork 0

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

[GH-ISSUE #204] [CS]Debian server hosting #168

New issue

Closed

opened 2026-02-27 01:59:54 +03:00 by kerem · 8 comments

kerem commented

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

Owner

Originally created by @Roedy86 on GitHub (Oct 24, 2014).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/204

Hi,

I am trying to host some lan server and have run into a problem.

When i run the servers with this command:
./hlds_run -game cstrike -strictportbind +ip 192.168.100.63 -port 27015 +clientport 27005 +map de_dust2 +servercfgfile cs.cfg

The server i bound to the one network interface and it is vac secure. But it doesn't show up in the lan tab. I can connect to the server from the console though.

If i run the server with this command:
./hlds_run -game cstrike -strictportbind -ip 192.168.100.63 -port 27015 +clientport 27005 +map de_dust2 +servercfgfile cs.cfg

The server is now on all interfaces, its not vac secure, but it does show up on the lan tab.

Is there a way to make the server visible in the lan tab and still only bound to one interface? This is possible with the same command under windows and hlds update tool (On the debian i am using steamcmd)

Thanks
/Roedy86

Originally created by @Roedy86 on GitHub (Oct 24, 2014). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/204 Hi, I am trying to host some lan server and have run into a problem. When i run the servers with this command: ./hlds_run -game cstrike -strictportbind +ip 192.168.100.63 -port 27015 +clientport 27005 +map de_dust2 +servercfgfile cs.cfg The server i bound to the one network interface and it is vac secure. But it doesn't show up in the lan tab. I can connect to the server from the console though. If i run the server with this command: ./hlds_run -game cstrike -strictportbind -ip 192.168.100.63 -port 27015 +clientport 27005 +map de_dust2 +servercfgfile cs.cfg The server is now on all interfaces, its not vac secure, but it does show up on the lan tab. Is there a way to make the server visible in the lan tab and still only bound to one interface? This is possible with the same command under windows and hlds update tool (On the debian i am using steamcmd) Thanks /Roedy86

kerem closed this issue

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

kerem commented

2026-02-27 01:59:55 +03:00

Author

Owner

@Scarsz commented on GitHub (Oct 25, 2014):

+sv_lan 1

@Scarsz commented on GitHub (Oct 25, 2014): `+sv_lan 1`

kerem commented

2026-02-27 01:59:55 +03:00

Author

Owner

@Roedy86 commented on GitHub (Oct 26, 2014):

Sadly i already tried that. Its the same result.

@Roedy86 commented on GitHub (Oct 26, 2014): Sadly i already tried that. Its the same result.

kerem commented

2026-02-27 01:59:55 +03:00

Author

Owner

@Scarsz commented on GitHub (Oct 26, 2014):

Only other thing I can think of is to remove strictbindport but unfortunately this is a problem with the server or your machine, not the script.

@Scarsz commented on GitHub (Oct 26, 2014): Only other thing I can think of is to remove strictbindport but unfortunately this is a problem with the server or your machine, not the script.

kerem commented

2026-02-27 01:59:55 +03:00

Author

Owner

@Roedy86 commented on GitHub (Oct 26, 2014):

I actually did some tcpdumps to have a look at the traffic.
The client sends a broadcast to all the ports (27015-27020)m Then normally the servers on these ports will answer.
But when i have the +ip configured, it simply doesn't answer. I think it looks like a bug

@Roedy86 commented on GitHub (Oct 26, 2014): I actually did some tcpdumps to have a look at the traffic. The client sends a broadcast to all the ports (27015-27020)m Then normally the servers on these ports will answer. But when i have the +ip configured, it simply doesn't answer. I think it looks like a bug

kerem commented

2026-02-27 01:59:55 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Nov 2, 2014):

This is an issue with the server rather than the script itself. If there is a bug it would need to be reported to Valve. However I recommend seeing if other Admins have had this issue.

@dgibbs64 commented on GitHub (Nov 2, 2014): This is an issue with the server rather than the script itself. If there is a bug it would need to be reported to Valve. However I recommend seeing if other Admins have had this issue.

kerem commented

2026-02-27 01:59:55 +03:00

Author

Owner

@Roedy86 commented on GitHub (Nov 3, 2014):

I have reported this to valve a week ago, but I am still waiting for a reply.
Does +ip work for you guys? If it does i would like to see the parameters you use.

I am also wondering why the script you developed is by default using -ip, which is not binding it to any interface. testing on my debian installation i have to use +ip to make it bind to an interface.

@Roedy86 commented on GitHub (Nov 3, 2014): I have reported this to valve a week ago, but I am still waiting for a reply. Does +ip work for you guys? If it does i would like to see the parameters you use. I am also wondering why the script you developed is by default using -ip, which is not binding it to any interface. testing on my debian installation i have to use +ip to make it bind to an interface.

kerem commented

2026-02-27 01:59:55 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Nov 24, 2014):

-ip is a command line parameter whereas +ip is more for console. Both should work
https://developer.valvesoftware.com/wiki/Command_Line_Options

I am closing this issue now

@dgibbs64 commented on GitHub (Nov 24, 2014): -ip is a command line parameter whereas +ip is more for console. Both should work https://developer.valvesoftware.com/wiki/Command_Line_Options I am closing this issue now

kerem commented

2026-02-27 01:59:55 +03:00

Author

Owner

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