Yeah, could the server stop binding to 27005? I was under the impression (At
least in HL1 mods), that 27005 is used by clients only. Correct me if wrong.

----- Original Message -----
From: "Mario Benito Ríos" <[EMAIL PROTECTED]>
To: <hlds_linux@list.valvesoftware.com>
Sent: Wednesday, April 06, 2005 5:09 PM
Subject: Re: [hlds_linux] Counter-Strike: Source and Source Engine update


This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Since last update, servers are binding at ip 0.0.0.0, port 27030 and up:

tcp        0      0 82.194.78.165:27012     0.0.0.0:*
LISTEN      10960/srcds_i686
tcp        0      0 82.194.78.165:27013     0.0.0.0:*
LISTEN      10994/srcds_i686
tcp        0      0 82.194.78.165:27016     0.0.0.0:*
LISTEN      18757/srcds_i686
tcp        0      0 82.194.78.165:27017     0.0.0.0:*
LISTEN      10990/srcds_i686
tcp        0      0 82.194.78.165:27019     0.0.0.0:*
LISTEN      10989/srcds_i686
tcp        0      0 82.194.78.165:27025     0.0.0.0:*
LISTEN      10980/srcds_i686
tcp        0      0 82.194.78.165:27026     0.0.0.0:*
LISTEN      10988/srcds_i686
udp        0      0 82.194.78.165:27008
0.0.0.0:*                           10990/srcds_i686
udp        0      0 82.194.78.165:27009
0.0.0.0:*                           10989/srcds_i686
udp        0      0 82.194.78.165:27010
0.0.0.0:*                           10960/srcds_i686
udp    21984      0 82.194.78.165:27011
0.0.0.0:*                           10980/srcds_i686
udp     1832      0 82.194.78.165:27012
0.0.0.0:*                           10960/srcds_i686
udp        0      0 82.194.78.165:27013
0.0.0.0:*                           10994/srcds_i686
udp        0      0 82.194.78.165:27016
0.0.0.0:*                           18757/srcds_i686
udp        0      0 82.194.78.165:27017
0.0.0.0:*                           10990/srcds_i686
udp        0      0 82.194.78.165:27019
0.0.0.0:*                           10989/srcds_i686
udp        0      0 0.0.0.0:27023
0.0.0.0:*                           14900/hlds_i686
udp        0      0 82.194.78.165:27025
0.0.0.0:*                           10980/srcds_i686
udp        0      0 82.194.78.165:27026
0.0.0.0:*                           10988/srcds_i686
udp        0      0 0.0.0.0:27030
0.0.0.0:*                           18757/srcds_i686
udp        0      0 0.0.0.0:27031
0.0.0.0:*                           10994/srcds_i686
udp        0      0 0.0.0.0:27032
0.0.0.0:*                           10990/srcds_i686
udp        0      0 0.0.0.0:27033
0.0.0.0:*                           10989/srcds_i686
udp        0      0 0.0.0.0:27034
0.0.0.0:*                           10988/srcds_i686
udp        0      0 0.0.0.0:27035
0.0.0.0:*                           10980/srcds_i686
udp        0      0 0.0.0.0:27036
0.0.0.0:*                           10960/srcds_i686
udp        0      0 82.194.78.165:27005
0.0.0.0:*                           18757/srcds_i686
udp        0      0 82.194.78.165:27006
0.0.0.0:*                           10988/srcds_i686
udp        0      0 82.194.78.165:27007
0.0.0.0:*                           10994/srcds_i686

There are also unwanted bindings starting at 27005, as you can see. My
servers are started with -nohltv option.

Alfred Reynolds wrote:

I cannot reproduce this exact problem. I start two servers with the
following command lines:
./srcds_run -game hl2mp +map dm_lockdown -dev +rcon_password bottest
-port 27020
./srcds_run -game hl2mp +map dm_lockdown -dev +rcon_password bottest
-port 27030


And the first server binds to 27020 and the second to 27031 (that is a bug, it is one higher than it should be, we will look into that). I cannpt get the first server to bind to 27030.

- Alfred

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thiesson
Johann
Sent: Wednesday, April 06, 2005 6:49 AM
To: hlds_linux@list.valvesoftware.com
Subject: Re: [hlds_linux] Counter-Strike: Source and Source Engine
update

--
On Apr 06, 10:55, Stephen Nicholson wrote:


Christoph Franke wrote:


Since the update there is a problem with the ip/port bindings.
Currently there are 2 srcds instances on my multihome system: cs:s
server on ip A with port 27015 and hl2mp on ip B with port 27030. But





starting with the update the cs:s server globally catches the port


27030 on start.


I've got the same thing on a server running two instances of CSS (Same





ip). The first server grabs 27030 which I used for the second server.



Same here. This is not the first time you make an update which broke the ip/port binding system :/

A very fast update for a fix is really needed.

--
DjoDjo
--
Content-Description: Digital signature

[ signature.asc of type application/pgp-signature deleted ]
--

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux



--

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux



_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to