Piecing together information here, it seems to be fixed on Windows server, but still broken on most or all Linux servers.
Milton Ngan wrote: > We had a fix in, but it appears to not have addressed the whole issue. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Nicholas > Hastings > Sent: Tuesday, November 17, 2009 10:30 AM > To: Half-Life dedicated Linux server mailing list > Subject: Re: [hlds_linux] L4D2 rcon query > > Milton, > > Can you tell us if Valve has acknowledged the rcon response issue on > linux l4d2 servers and plans on fixing it sometime in the near future? > > Milton Ngan wrote: > >> Netcon works, but the disadvantage is that you get console spew that can >> potentially get mixed in with your responses. There isn't a clear response >> format. (e.g a prompt or end of message character). >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of David A. >> Parker >> Sent: Tuesday, November 17, 2009 9:56 AM >> To: Half-Life dedicated Linux server mailing list >> Subject: Re: [hlds_linux] L4D2 rcon query >> >> What about using the netcon for each server instead of rcon? (Just >> throwing ideas out, I haven't actually tried anything using netcon >> remotely yet). >> >> - Dave >> >> Jay Deiman wrote: >> >> >>> Ronny Schedel wrote: >>> >>> >>>> The protocol: >>>> http://developer.valvesoftware.com/wiki/Server_Queries >>>> >>>> Scroll down for samples. >>>> >>>> >>> Great info, but it still doesn't change the fact that rcon over tcp to >>> the server ports doesn't work. Here's a little debug info from a script >>> I wrote using the docs at >>> http://developer.valvesoftware.com/wiki/Source_RCON_Protocol >>> >>> -------------------------------- >>> $ ./rcon.py -c status janus.splitstreams.com:27021 xxxxxxx >>> >>> reqid: 2094234817 >>> >>> SENDING: '\x11\x00\x00\x00\xc1|\xd3|\x03\x00\x00\x00xxxxxx\x00\x00' >>> >>> RECV (10): '\xc1|\xd3|\x00\x00\x00\x00\x00\x00' >>> >>> RECV (10): '\xc1|\xd3|\x02\x00\x00\x00\x00\x00' >>> >>> reqid: 954561615 >>> >>> SENDING: '\x10\x00\x00\x00Ot\xe58\x02\x00\x00\x00status\x00\x00' >>> >>> RECV (10): 'Ot\xe58\x00\x00\x00\x00\x00\x00' >>> -------------------------------- >>> >>> The server authenticates me and even responds to the status command, it >>> just give me back an empty null terminated string. >>> >>> Compare the above to l4d1: >>> >>> -------------------------------- >>> $ ./rcon.py -c status janus.splitstreams.com:27016 xxxxxxx >>> >>> reqid: 1811805914 >>> >>> SENDING: '\x11\x00\x00\x00\xda\xf6\xfdk\x03\x00\x00\x00xxxxxx\x00\x00' >>> >>> RECV: '\xda\xf6\xfdk\x00\x00\x00\x00\x00\x00' >>> >>> RECV: '\xda\xf6\xfdk\x02\x00\x00\x00\x00\x00' >>> >>> reqid: 929550210 >>> >>> SENDING: '\x10\x00\x00\x00\x82\xcfg7\x02\x00\x00\x00status\x00\x00' >>> >>> RECV: '\x82\xcfg7\x00\x00\x00\x00hostname: MF L4D 1\nversion : 1.0.1.6 >>> 4023 secure (unknown)\nudp/ip : 209.98.155.113:27016 [ public same >>> ]\nos : Linux Dedicated\nmap : >>> l4d_hospital01_apartment\nplayers : 0 humans, 0 bots (4 max) >>> (hibernating) (unreserved)\n\n# userid name uniqueid connected ping loss >>> state rate adr\n#end\n\x00\x00' >>> >>> >>> -------------------------------- >>> >>> If A2S queries are working, that's great, but rcon should be fixed >>> nonetheless. Rcon is used by some (including me) for more than just >>> getting current players. >>> >>> Jay Deiman >>> >>> >>> >> >> > > _______________________________________________ > 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
