Yep - there certainly is.
//
// packet number in seq ___ ____ total number of packets
// | |
// -pkt split- -32 bit id- | | - normal pkt start -
// FE FF FF FF 07 02 00 00 0 2 FF FF FF FF 6C <data>
// FE FF FF FF 07 02 00 00 1 2 <data>
If the data returned doesn't fit into a single datagram, the server will
split the data, indicated by the first four bytes being "FE FF FF FF"
instead of "FF FF FF FF". The next four bytes are some kind of ID (correct
me if I'm wrong on that Alfred) which I use in my code to identify the
packets that need to be reassembled. The next 4 bits is the part number
(zero based) and the following 4 bits is the total number of bytes in the
sequence. So, in the example above, the first line is the first part of 2,
and the second line is the second part of 2.
Once you've reassambled the data, it looks just like any other HL packet.
Good luck.
Terry
Author of the not so excellent ServerInfo ;-)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kris
Sent: Sunday, February 01, 2004 11:33 AM
To: [EMAIL PROTECTED]
Subject: [hlds_apps] HLDS RCON fragmented UDP
Is there any way to detect that a hlds rcon udp packet reply is fragmented
or not?
Doing an 'rcon status' on large servers returns two packets, the first one
16 bytes and the second one 1400 bytes, and the full reply is created by
putting the first packet on the end of the second one. Can it not be changed
so that fragmented rcon replies work in the same way as fragmented
rules-query replies (where there is a different header)?
Cheers,
Kris.
Author of the excellent K-query. : www.kquery.com
___
/__/|
| |:|
| |:|
__| |:|
/__/\_|:|____
\ \:\/:::::/
\ \::/~~~~
\ \:\
\ \:\
\__\/
_______________________________________________
hlds_apps mailing list
[EMAIL PROTECTED]
http://list.valvesoftware.com/mailman/listinfo/hlds_apps
