This is regarding LAN-only dedicated servers. Copied from my post in the HLDS mailing list. I believe this to be a bug induced by a game update, based that I've tested this recently in several scenarios and have received the same results each time. It worked fine about a year ago on the same install, when I last utilized -nomaster.
I was tasked to set up some servers for an upcoming annual LAN party where there will be no internet connection readily available. I have done this is previous years with no issues whatsoever. However, when testing this time around I have ran into several buggers. I'm guessing an update was released since then that broke something...
Here's what I've been able to trouble-shoot and confirm:
TF2 servers do not show up under the "LAN" servers master list when the -nomaster switch is used. The console starts up fine. I can connect to it manually with the client (connect 192.168...). sv_lan 1 is set. If -nomaster isn't present in the startup line they show up fine. However, this switch is (obviously) necessary when no internet connection is present so that the servers don't go into an infinite loop searching for a master server they can't possibly find. L4D servers show up fine when using the -nomaster switch, and similar startup parameters. This is most likely a server-side issue.
TF2 server startup line (does NOT show up in LAN list):
L4D server startup line (shows up perfectly fine on the LAN list):
Both are running on same Arch Linux machine. And, again, everything works fine when -nomaster isn't used. I decided to see if a -nomaster sv_lan 1 server would show up in the "LAN" list if it was ran on Windows. I did a base install of SRCDS for TF2 under Windows XP on the same machine (dual-boot setup). It had the same results. It also does not show up under the "LAN" server list on the client end, but can be manually connected to and otherwise runs fine. So, this rules out it being a Linux specific issue at least.
Are there any workarounds for this that anybody knows of? I think telling everyone at the LAN Party to manually connect might be too much for some people (developer console not enabled by default, people being unable to remember the IP, etc.) I suppose a possible solution might be to hand out a game menu modification that list's any dedicated servers at the event (easy to make I know). The only tricky part is getting is distributed. Hrm...
I was tasked to set up some servers for an upcoming annual LAN party where there will be no internet connection readily available. I have done this is previous years with no issues whatsoever. However, when testing this time around I have ran into several buggers. I'm guessing an update was released since then that broke something...
Here's what I've been able to trouble-shoot and confirm:
TF2 servers do not show up under the "LAN" servers master list when the -nomaster switch is used. The console starts up fine. I can connect to it manually with the client (connect 192.168...). sv_lan 1 is set. If -nomaster isn't present in the startup line they show up fine. However, this switch is (obviously) necessary when no internet connection is present so that the servers don't go into an infinite loop searching for a master server they can't possibly find. L4D servers show up fine when using the -nomaster switch, and similar startup parameters. This is most likely a server-side issue.
TF2 server startup line (does NOT show up in LAN list):
Code:
#!/bin/sh
echo "Starting Server #1 as TF2 (server-1)"
sleep 1
screen -A -m -d -S server-1 ./srcds_run -nomaster -game tf -ip 0.0.0.0 +fps_max 375 +map ctf_2fort +maxplayers 32
L4D server startup line (shows up perfectly fine on the LAN list):
Code:
#!/bin/sh
echo "Starting Server #2 as L4D (server-2)"
sleep 1
screen -A -m -d -S server-2 ./srcds_run -nomaster -game left4dead -ip 0.0.0.0 -port 27019 +map l4d_hospital01_apartment
Both are running on same Arch Linux machine. And, again, everything works fine when -nomaster isn't used. I decided to see if a -nomaster sv_lan 1 server would show up in the "LAN" list if it was ran on Windows. I did a base install of SRCDS for TF2 under Windows XP on the same machine (dual-boot setup). It had the same results. It also does not show up under the "LAN" server list on the client end, but can be manually connected to and otherwise runs fine. So, this rules out it being a Linux specific issue at least.
Are there any workarounds for this that anybody knows of? I think telling everyone at the LAN Party to manually connect might be too much for some people (developer console not enabled by default, people being unable to remember the IP, etc.) I suppose a possible solution might be to hand out a game menu modification that list's any dedicated servers at the event (easy to make I know). The only tricky part is getting is distributed. Hrm...