Hmmm ... am I reading this correctly? > *./srcds_run -console -game cstrike +map de_dust +maxplayers 10 +ip > 10.0.0.21 -port 27015 +exec server.cfg* > *./srcds_run -console -game cstrike +map de_dust +maxplayers 10 +ip > 10.0.0.22 -port 27015 +exec server.cfg* > *./srcds_run -console -game cstrike +map de_dust +maxplayers 10 +ip > 10.0.0.23 -port 27015 +exec server.cfg*
Is that running three instances on the same server, but binding to the same port number - but on different IP addresses? I notice that those are all RFC-1918 (private address space) IP addresses. I presume these are all behind the same firewall / Interoutrnet-er devices that is than using port/address translation to public IP addresses? If so, they may each need to be individually mapped at your firewall / Internet-router to different public IP address (i.e. multiple public IP addresses instead of sharing the same public IP address), OR port-forwarded at your firewall / Internet-router to different public ports on the same IP address - in which case it would be easier to use one private IP address and different ports instead of all on 27015. On Wed, Aug 27, 2014 at 1:22 PM, Jeff Nelson <[email protected]> wrote: > I've been out of pocket for a while and I was able to finally test. > > The problem has been narrowed down to specifying the IP in the srcds > startup command. > If I use: "./srcds_run -console -game tf +map ctf_well +maxplayers 24 +ip > 10.10.0.50" > > The game server is running, live and available to connect, but it doesn't > appear in the server browser for LAN games. > If I paste this exact command into a windows box, it does work. > > Performing a test on the linux servers using: "lsof -i -n -a -p > $GAMESERVPID", > shows me the following: > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > srcds_lin 7645 root 22u IPv4 266289 0t0 UDP 10.10.0.50:27015 > srcds_lin 7645 root 23u IPv4 266290 0t0 UDP 10.10.0.50:27005 > srcds_lin 7645 root 24u IPv4 266291 0t0 UDP 10.10.0.50:27020 > srcds_lin 7645 root 25u IPv4 266292 0t0 TCP 10.10.0.50:27015 > (LISTEN) > srcds_lin 7645 root 35u IPv4 266092 0t0 UDP 10.10.0.50:26901 > > This indicates to me that the srcds program is properly bonding to the > specified IP in the startup command. But for some reason isn't broadcasting > itself to the server browser. > > If I run the following srcds command: > ./srcds_run -console -game tf +map ctf_well +maxplayers 24 > *Note that no IP is specified for srcds to bond to... > > The server does appear in the browser. Performing a similar port look-up I > receive: > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > srcds_lin 7689 root 22u IPv4 273770 0t0 UDP *:27015 > srcds_lin 7689 root 23u IPv4 273771 0t0 UDP *:27005 > srcds_lin 7689 root 24u IPv4 273772 0t0 UDP *:27020 > srcds_lin 7689 root 25u IPv4 273776 0t0 TCP *:27015 (LISTEN) > srcds_lin 7689 root 35u IPv4 274580 0t0 UDP *:26901 > > In this case, the srcds instance is bonding to the available IP on the > server, but when this happens, broadcast traffic is allowed. > > Is there anything else I can try or suggestions anyone else has? > Thanks for the help! > > > > > > > On Wed, Feb 19, 2014 at 5:41 PM, Jesse Molina <[email protected]> > wrote: > > > > > Do all three servers stop appearing in the server browser, or only one or > > two of them? > > > > Verify that your servers are not actually tripping all over themselves > > without your knowledge, and that they are binding to the sockets which > you > > think they should be: > > > > lsof -i -n -a -p $GAMESERVPID > > > > Do this for each server and find out what network resources it is using. > > > > It should be noted that CSGO currently has a problem where it globs onto > * > > for certain sockets EVEN when you specifically assign it to a particular > > IP. This bug has been noted many times on this mailing list now. > > > > I can't think of anything with SELinux that might be causing you a > > problem, and I don't know if it is enabled by default on Suse, but you > > might want to disable it and see if that has any effect. > > > > Good luck > > > > > > > > > > On 2/18/14, 23:46, Jeff Nelson wrote: > > > >> We are experiencing an issue where if we run multiple SRCDS instances on > >> the same linux server, on the same subnet, bounded to specific IP > >> addresses, they will not appear in the server browser. (This bug doesn't > >> appear when using a Windows server, Linux only.) > >> > >> Environment: > >> OpenSuse 13.1 x64 (Kernal: 3.11.6-4-default) > >> We have also tried this on CentOS and RedHat, still no dice. > >> We have 3 IP addresses assigned to one server using the same broadcast > >> address: 10.0.0.255 > >> > >> Startup Scripting: > >> > >> *./srcds_run -console -game cstrike +map de_dust +maxplayers 10 +ip > >> 10.0.0.21 -port 27015 +exec server.cfg* > >> *./srcds_run -console -game cstrike +map de_dust +maxplayers 10 +ip > >> 10.0.0.22 -port 27015 +exec server.cfg* > >> *./srcds_run -console -game cstrike +map de_dust +maxplayers 10 +ip > >> 10.0.0.23 -port 27015 +exec server.cfg* > >> > >> The servers run and startup correctly - no errors. I am able to connect > to > >> all of them using the in-game console; however, they are not present > when > >> using the Steam server browser under the LAN tab. > >> I have contacted Steam support with a possible Steam client issue but > they > >> replied stating that it wasn't a client issue. > >> > >> If I run these servers inside a virtual machine, like XEN or VMWARE, > where > >> each guest VM has a single IP address assigned to it, running one SRCDS > >> instance per guest, this problem goes away. > >> I am able to run each server on the same subnet and broadcast networks > and > >> they will appear in the server browser. This only occurs when multiple > >> SRCDS instances run on the same server where specific IP addresses are > >> assigned. > >> > >> Additional Notes: > >> This problem doesn't occur on Windows servers. Changing the ./srcds_run > to > >> srcds.exe (leaving the rest of the commands as is), I am able to view > all > >> those servers above from the server browser. > >> In the same scenario, we have 3 LAN IP addresses assigned to the Windows > >> server, and the srcds instances are assigned IP addresses. > >> > >> Why don't you just change the ports? > >> Changing the port is what we've been doing for sometime; however, we are > >> limited to only 5 SRCDS per server as the broadcast port cannot be used > or > >> passed (port 27020). We then run into additional issues as use use HLTV > >> and > >> GoTV on several servers and they operate on 27020+ ports. I would like > to > >> know if this is a bug and can be fixed since it works for one platform > but > >> not another. > >> > >> Final Note: > >> I'm working with LAN IP addresses only for local LAN events. I am not > >> trying to accomplish this task for public play. > >> > >> Thanks for everyone's assistance. > >> _______________________________________________ > >> To unsubscribe, edit your list preferences, or view the list archives, > >> please visit: > >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > >> > > > > > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
