Server Help :: View topic - Undocumented Packets.

Server Help

Trash Talk - Undocumented Packets.

Doc Flabby - Fri Feb 02, 2007 1:21 pm
Post subject: Undocumented Packets.

Now correct me if i'm wrong but packets 0x00 0x10 and 0x00 0x11 are not documented anywhere. I've looked though the packet descriptions a number of times.

They appear to be part of the core-protocol. I'd love to know what they are for. Anyone got any ideas?

I recorded them in this sequence. They occur when continuum connects to a zone. 0x01 is the first packet continuum sends to the server (that isnt a ping)

Code: Show/Hide

Client --> Server

Core Protocol 0x01 (login packet)

[packet type] [client encrpytion key] [encrption type] (11=continum)
00 01 b2 2f 73 84 11 00

Server --> client

[packet type] [????? ] [????? ] [???? (01 = vie maybe? ]
00 10 9a 00 bc cf 06 00 3e c9 01 00

Client --> Server

[packet type] [(same as above)] [? ??? ]
00 11 9a 00 bc cf 01 00

Everything after the 0x00 0x11 packet is encrpyted.

CypherJF - Fri Feb 02, 2007 5:15 pm
Post subject:

Are you trying to connect to a SSC biller zone?

Doc Flabby - Fri Feb 02, 2007 5:18 pm
Post subject:

These packets appear on connection to both SSC and non-SSC zones. i'm not sure if they appear when connecting to a ASSS zone i think the ones i tried were all subgame zones.

CypherJF - Fri Feb 02, 2007 6:39 pm
Post subject:

I expect there to be some undocumented packet to let the client know it's coming from the "authorized" SSC biller.

Doc Flabby - Fri Feb 02, 2007 7:18 pm
Post subject:

There is but these packets arn't it

The values of the fields change and it doesnt seem to matter if its a SSC Biller zone or any other biller. What i suspect is the SSC biller packets come later on. Im more interested in these packets as no one has documented them. They must do something lol.

Mine GO BOOM - Fri Feb 02, 2007 7:58 pm
Post subject:

Code: Show/Hide

/* check if a buffer is a connection init packet */
#define IS_CONNINIT(buf) \
( \
(buf)->d.rel.t1 == 0x00 && \
( \
(buf)->d.rel.t2 == 0x01 || \
(buf)->d.rel.t2 == 0x11 \
/* add more packet types that encryption \
* module need to know about here */ \
) \
)

Right inside of net.c, they are specifically for Continuum encryption, which is why they are not bothered with in documentation on ASSS wiki. Look where it is used. I could help more, but I promised not to.

Bak - Fri Feb 02, 2007 8:36 pm
Post subject:

looks like 00 10 is the continuum equivilent of 00 02, and 00 11 is the ack.

Doc Flabby - Sat Feb 03, 2007 5:55 am
Post subject:

thanks. i was couldn't work out why there wasn't the 00 02 packet, makes sence now if its a cont specific thing.