Hi,

Adding the +ip parameter fixed it.

I can now send query's to the servers and get a response.

Cheers,

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jt
Sent: Sunday, November 09, 2008 7:20 PM
To: Half-Life dedicated Linux server mailing list
Subject: Re: [hlds_linux] -fork query issue s

Why is it binding to all the interfaces? Are you specifying -ip?

Sent from my iPhone

On 9-Nov-08, at 9:42 AM, "Saint K." <[EMAIL PROTECTED]> wrote:

> Hi,
>
> On the command it returns no results. Only on a netstat -a I get  
> results on
> port 27016.
>
> udp      664      0 *:27016                 *:*
>
> May I ask what the command line looks like you boot your servers with?
>
> Cheers,
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of  
> localhost
> Sent: Sunday, November 09, 2008 5:14 PM
> To: Half-Life dedicated Linux server mailing list
> Subject: Re: [hlds_linux] -fork query issue s
>
>
> Hmm, on my setup I get a tcp port per game instance.  I think the  
> port 9000
> thing is related to netconport - even though you don't have that  
> enabled,
> the "master" server still seems to be listening (you can't do  
> anything with
> the master server yet, though; apparently you may be able to in  
> future)
>
> only other thing I can think of is doing, say, "netstat -napt | grep  
> 27016"
> (numeric, all, show program, tcp) and seeing if something else is  
> nicking
> the port.  I'd expect the server to die in that case, though.
>
> There's 3 issues here:
>
> - The linux l4d demo server grabs more udp ports than it needs to
> - When using -fork, you lose the little control over port  
> assignments you
> had (Control over this is something Chris has said he's looking at)
> - In your setup, most of the servers don't seem to be listening on  
> the rcon
> ports at all (I'm surprised they work)
>
> Sorry I can't help further
>
> On Sun, 9 Nov 2008 17:03:14 +0100, "Saint K." <[EMAIL PROTECTED] 
> >
> wrote:
>> Hi,
>>
>> There are only 2 TCP ports listening.
>>
>> tcp        0      0 0.0.0.0:27015           0.0.0.0:*
> LISTEN
>> 6107/srcds_i486
>> tcp        0      0 0.0.0.0:9000            0.0.0.0:*
> LISTEN
>> 463/srcds_i486
>>
>> So now the big question rises, how to external query the other  
>> servers in
>> the fork, trough 27015?
>>
>> I'm not quite sure btw on what is port 9000 doing.
>>
>> Cheers,
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of  
>> localhost
>> Sent: Sunday, November 09, 2008 4:56 PM
>> To: Half-Life dedicated Linux server mailing list
>> Subject: Re: [hlds_linux] -fork query issue s
>>
>>
>> try "netstat -nlpt | grep srcds" as rcon is tcp not udp
>>
>> if you aren't using the -netconport option, the only ports which  
>> should
> be
>> found are the rcon listening ports.  I wonder if it's possible for  
>> the
> udp
>> and tcp ports to end up different, somehow?
>>
>> On Sun, 9 Nov 2008 16:51:36 +0100, "Saint K." <[EMAIL PROTECTED] 
>> >
>> wrote:
>>> Well, I can see them online in HLSW, but I can't communicate with it
>> terms
>>> of sending commands / receiving output.
>>>
>>> If you try and setup a connection with HLSW, or our query's from the
>>> website, the error reads; Connection failed (No connection could  
>>> be made
>>> because the target machine actively refused it. ) It only works on  
>>> the
>>> first
>>> of the 6 servers in the fork, at 27015.
>>>
>>> Cheers
>>>
>>> -----Original Message-----
>>> From: [EMAIL PROTECTED]
>>> [mailto:[EMAIL PROTECTED] On Behalf Of
>> localhost
>>> Sent: Sunday, November 09, 2008 4:47 PM
>>> To: Half-Life dedicated Linux server mailing list
>>> Subject: Re: [hlds_linux] -fork query issue s
>>>
>>>
>>> Hmm, didn't pick up on the "can't query them" aspect before.  I
>> certainly
>>> can with my own.
>>> Try running hlsw, typing in your IP, and appending :27016, 7, 8,  
>>> 9....
>> in
>>> sequence, until you get to about :30
>>>
>>> I should also point out that I've had servers "jump" ports on  
>>> restart.
>>>
>>> On Sun, 09 Nov 2008 08:25:58 -0700, "Kevin J. Anderson"
>>> <[EMAIL PROTECTED]> wrote:
>>>> My guess is that they want queries to always run through the master
>>>> server, since its controlling the forks.
>>>>
>>>> Could also be for simplified firewall rules for admins, etc.
>>>>
>>>> Kevin
>>>>
>>>> Saint K. wrote:
>>>>> Hi,
>>>>>
>>>>> Good guess! It is indeed on 27025! Thanks.
>>>>>
>>>>> It still doesn't explain thought why we can't query those other
>> servers
>>>> at
>>>>> the gameports their running on.
>>>>>
>>>>> Maybe VALVe can shed some light on how this thing works.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> -----Original Message-----
>>>>> From: [EMAIL PROTECTED]
>>>>> [mailto:[EMAIL PROTECTED] On Behalf Of
>>>> localhost
>>>>> Sent: Sunday, November 09, 2008 2:35 PM
>>>>> To: Half-Life dedicated Linux server mailing list
>>>>> Subject: Re: [hlds_linux] -fork query issue s
>>>>>
>>>>>
>>>>> Eliminating all the entries relating to the 5 servers you know  
>>>>> about,
>> I
>>>>> think your 6th is listening on 27025 or 27026.
>>>>> I'm not sure what's going on with the extra ports - it may be  
>>>>> related
>>> to
>>>>> htlv going by errors I get trying to start individual servers -  
>>>>> but
>>> it's
>>>>> the reason why some people aren't having much luck forking more  
>>>>> than
>>>> about
>>>>> 5 servers at a time
>>>>>
>>>>> On Sun, 9 Nov 2008 14:14:55 +0100, "Saint K."
>>> <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> What can we make of this?
>>>>>> udp        0      0 0.0.0.0:27008           0.0.0.0:*
>>>>>> 4859/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27009           0.0.0.0:*
>>>>>> 5067/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27010           0.0.0.0:*
>>>>>> 5033/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27015           0.0.0.0:*     <- L4D
>>> server
>>>>>> 4951/srcds_i486
>>>>>> udp      332      0 0.0.0.0:27016           0.0.0.0:*     <- L4D
>>> server
>>>>>> 4724/srcds_i486
>>>>>> udp      332      0 0.0.0.0:27017           0.0.0.0:*     <- L4D
>>> server
>>>>>> 4856/srcds_i486
>>>>>> udp      664      0 0.0.0.0:27018           0.0.0.0:*     <- L4D
>>> server
>>>>>> 4859/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27019           0.0.0.0:*     <- L4D
>>> server
>>>>>> 5067/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27020           0.0.0.0:*
>>>>>> 4951/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27021           0.0.0.0:*
>>>>>> 4724/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27022           0.0.0.0:*
>>>>>> 4856/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27023           0.0.0.0:*
>>>>>> 4859/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27024           0.0.0.0:*
>>>>>> 5067/srcds_i486
>>>>>> udp        0    428 0.0.0.0:27025           0.0.0.0:*
>>>>>> 5033/srcds_i486
>>>>>> udp     1660      0 0.0.0.0:27026           0.0.0.0:*
>>>>>> 5033/srcds_i486
>>>>>> udp     5312      0 0.0.0.0:26901           0.0.0.0:*
>>>>>> 4951/srcds_i486
>>>>>> udp     2656      0 0.0.0.0:26902           0.0.0.0:*
>>>>>> 4724/srcds_i486
>>>>>> udp     2656      0 0.0.0.0:26903           0.0.0.0:*
>>>>>> 4856/srcds_i486
>>>>>> udp        0      0 0.0.0.0:26904           0.0.0.0:*
>>>>>> 5067/srcds_i486
>>>>>> udp     2988      0 0.0.0.0:26905           0.0.0.0:*
>>>>>> 4859/srcds_i486
>>>>>> udp     2656      0 0.0.0.0:26906           0.0.0.0:*
>>>>>> 5033/srcds_i486
>>>>>> udp        0      0 0.0.0.0:26907           0.0.0.0:*
>>>>>> 4951/srcds_i486
>>>>>> udp     2656      0 0.0.0.0:26908           0.0.0.0:*
>>>>>> 4951/srcds_i486
>>>>>> udp        0      0 0.0.0.0:26909           0.0.0.0:*
>>>>>> 4724/srcds_i486
>>>>>> udp     2656      0 0.0.0.0:26910           0.0.0.0:*
>>>>>> 4856/srcds_i486
>>>>>> udp        0      0 0.0.0.0:26911           0.0.0.0:*
>>>>>> 5067/srcds_i486
>>>>>> udp     2988      0 0.0.0.0:26912           0.0.0.0:*
>>>>>> 4951/srcds_i486
>>>>>> udp        0      0 0.0.0.0:26913           0.0.0.0:*
>>>>>> 4859/srcds_i486
>>>>>> udp     2656      0 0.0.0.0:26914           0.0.0.0:*
>>>>>> 4856/srcds_i486
>>>>>> udp        0      0 0.0.0.0:26915           0.0.0.0:*
>>>>>> 5033/srcds_i486
>>>>>> udp        0      0 0.0.0.0:26917           0.0.0.0:*
>>>>>> 4856/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27005           0.0.0.0:*
>>>>>> 4951/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27006           0.0.0.0:*
>>>>>> 4724/srcds_i486
>>>>>> udp        0      0 0.0.0.0:27007           0.0.0.0:*
>>>>>> 4856/srcds_i486
>>>>>>
>>>>>> The rest of these ports are a mystery to me.
>>>>>>
>>>>>> I'd expect the 6th server to run off 27020, but nothing replies
>> there.
>>>> I
>>>>>> don't understand what 27020-27026 is used for either.
>>>>>>
>>>>>> Cheers
>>>>>> -----Original Message-----
>>>>>> From: [EMAIL PROTECTED]
>>>>>> [mailto:[EMAIL PROTECTED] On Behalf Of
>>>> localhost
>>>>>> Sent: Sunday, November 09, 2008 1:49 PM
>>>>>> To: Half-Life dedicated Linux server mailing list
>>>>>> Subject: Re: [hlds_linux] -fork query issue's
>>>>>>
>>>>>>
>>>>>> If you run netstat -nlpu | grep srcds:
>>>>>>
>>>>>> (numeric, listening, show programs, UDP)
>>>>>>
>>>>>> You should see all the UDP ports your 7 srcds processes are  
>>>>>> listening
>>>> on
>>>>>> (6
>>>>>> servers and the master).  Each will probably be listening on 3  
>>>>>> ports.
>>>> One
>>>>>> of them will be the actual game port.
>>>>>>
>>>>>> On Sun, 9 Nov 2008 13:12:50 +0100, "Saint K."
>>>> <[EMAIL PROTECTED]>
>>>>>> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> On our Linux machine we now use the -fork option to spawn the  
>>>>>>> L4D
>>>>>> servers.
>>>>>>> The problem here is we can externally only query port 27015. The
>>>> servers
>>>>>>> running on 27016, 27017, 27018 and 27019 don't respond on  
>>>>>>> external
>>>>>>> query's.
>>>>>>>
>>>>>>> The 6th server from the -fork option spawns at a random port,  
>>>>>>> not
>>>> 27020.
>>>>>> I
>>>>>>> can't find which port it runs off, although the CPU load  
>>>>>>> indicates
>>> the
>>>>>> 6th
>>>>>>> server is also being used.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>>
>> _______________________________________________
>> 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

_______________________________________________
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