Hello,
I have a box running a CS 1.6 server (listening on port 27015), and I am
trying to run the L4D server on the same box using a second IP assigned
to the virtual interface eth0:1. I am specifying the eth0:1 IP address
and port 27015 when I start the L4D server, but it consistently binds to
port 27016 instead. The only way I can get it to listen on 27015 is if
I shut down the CS 1.6 server.
Here is the command line I'm using:
./srcds_run -game left4dead +map l4d_dem_hospital01_apartment
+maxplayers 8 +ip x.x.x.x -port 27015 +sv_lan 1 +sv_public 0
+sv_allow_lobby_connect_only 0 +exec server.cfg -nomaster
The server starts up correctly and doesn't say anything about any port
problems or the port change, but starts listening on 27016:
Network: IP x.x.x.x, mode MP, dedicated Yes, ports 27016 SV / 27005 CL
This exact same setup is working fine on another box running a TF2
server and a CS:S server on separate IPs using a virtual interface, both
listening on port 27015.
I have verified that I can run simultaneous instances of other programs
listening on the same TCP or UDP port using the two different IPs, so it
doesn't appear to be an OS problem.
Getting L4D to run on this box and listen on port 27015 would be ideal
because that port is already open in our firewall to these IPs. Any
help or ideas would be greatly appreciated.
Thanks,
Dave
--
Dave Parker
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
