Receiving server info

[kung foo man]

A little collection:

Master server list:

$ echo -e "\xFF\xFF\xFF\xFFgetservers 117 full empty" | nc cod2master.activision.com -u 20710
ÿÿÿÿgetserversResponse
\Ù¬²q"\Ù¬²q#\°
                ëq1\l=pq \U[Ì\Uc\Dè§Úq \°
                                                ëq9\XÆvq9\EOF

RCON:

$ echo -e '\xff\xff\xff\xffrcon thyPassword status' | netcat -u 127.0.0.1 28933
ÿÿÿÿprint
map: dr_beatwater
num score ping guid   name            lastmsg address               qport rate
--- ----- ---- ------ --------------- ------- --------------------- ----- -----

getstatus

$ echo -e '\xff\xff\xff\xffgetstatus' | netcat -u 127.0.0.1 28933
ÿÿÿÿstatusResponse
\fs_game\dr_v4\g_antilag\1\g_gametype\zom\gamename\Call of Duty 2\mapname\dr_beatwater\protocol\117\shortversion\1.2\sv_allowAnonymous\0\sv_floodProtect\1\sv_hostname\^2K^3~^2DeathRun ^2Rounds ^3: ^23 ^3/ ^210 ^7killtube.org\sv_maxclients\15\sv_maxPing\0\sv_maxRate\0\sv_minPing\0\sv_privateClients\0\sv_punkbuster\0\sv_pure\1\sv_voice\0\pswrd\0\mod\1

getinfo

$ echo -e '\xff\xff\xff\xffgetinfo' | netcat -u 127.0.0.1 28933
ÿÿÿÿinfoResponse
\protocol\117\hostname\^2K^3~^2DeathRun ^2Rounds ^3: ^23 ^3/ ^210 ^7killtube.org\mapname\dr_beatwater\sv_maxclients\15\gametype\zom\pure\1\game\dr_v4\kc\1\hw\1\mod\1\voice\0\pb\-4598016

getchallenge

$ echo -e '\xff\xff\xff\xffgetchallenge' | netcat -u 127.0.0.1 28933
ÿÿÿÿchallengeResponse -1508048936

http://ftp.iinet.net.au/games/idstuf...ocs/server.txt
"getstatus" responds with all the info that qplug or qspy can see about the server and all connected players. Used for getting detailed information after the simple info query. It is sent along with a challenge string. The server will respond with a "getstatusResponse" packet.

"getinfo" responds with a short info message that should be enough to determine if a user is interested in a server to do a full status. It is also sent with a challenge string.

"getchallenge" returns a challenge number that can be used in a subsequent connectResponse command. We do this to prevent denial of service attacks that flood the server with invalid connection IPs. With a challenge, they must give a valid IP address. The server will respond with a "challengeResponse" packet.

"connect" is the first step in a client connecting to a server. You send the "connect" string followed by the infoString containing the protocol version of the client, the qport, the challenge string (obtained via getchallenge), and the userinfo.

"rcon" is a remote command to the server. It's sent as "rcon" followed by the server password, followed by the command string to be executed.