Strange 0x0F?

[Deception]

I just recieved the BNCS packet 0x0F in this sequence when attempting to logon to Battle.net with W3XP.

[00:56:22] BNCS Sent 0x50
[00:56:22] BNCS Sent 0x25
[00:56:22] BNCS Received 0x0F  FF 0F 2A 00 05 00 00 00 00 00 00 00 FF FF FF FF 00 00 00 00 0D F0 AD BA 0D FF 25 08 00 98 4B E6 7B FF 50 E3 00 02 00 00 00 B7

Message data: ˜Kæ{ÿPã

What does this mean? Has anyone else ever seen this?

[Newby]

I've had stuff like that happen, where I'd receive a chat event in the middle of logging on.

How often does this occur?

[Arta]

When you say "in the middle of logging on", can you be more precise? Do you have a log of the whole session? Which messages occured before and after this one?

That SID_CHATEVENT looks malformed. There seems to be a valid SID_PING and the start of a SID_AUTH_INFO half way through it. Are you sure you don't have a bug in your netcode? If not, perhaps Battle.net does.

[tA-Kane]

I have never seen such occurances, and have not heard suggestions of such from ... reputable ... people. I would try going through your netcode and verifying that there's absolutely no way in hell that that packet is partly old data.

Also, a packetlog that was generated by a third party packetlogger would be a lot more convincing.

[Newby]

When you say "in the middle of logging on", can you be more precise? Do you have a log of the whole session? Which messages occured before and after this one?

I had gotten back 0x51 and I randomly got a good chat event; then, I disconnected and got IPBanned.

It happened a while ago, I don't have anything on it anymore. :/

[Blaze]

Deception, can you continue logging in succesfully after this?

[UserLoser.]

Did you just reconnect?  Looks possible that you received part of a message, then since SID_PING is the first message you received, your data handler is concatenating the halfway received message and he ping message (which it shouldn't).

Edit: typo

[Ban]

Did you just reconnect? Looks possible that you received part of a message, then since SID_PING is the first message you received, your data handler is concatnating the halfway received message and he ping message (which it shouldn't).

*connecting
*the
makes it such much easier to read UL

[warz]

Did you just reconnect? Looks possible that you received part of a message, then since SID_PING is the first message you received, your data handler is concatnating the halfway received message and he ping message (which it shouldn't).

*connecting
*the
makes it such much easier to read UL

1 entry found for Concatenating.
con·cat·e·nate    ( P )  Pronunciation Key  (kn-ktn-t, kn-)
tr.v. con·cat·e·nat·ed, con·cat·e·nat·ing, con·cat·e·nates
To connect or link in a series or chain.
Computer Science. To arrange (strings of characters) into a chained list.

adj. (-nt, -nt)
Connected or linked in a series.

[Ban]

My mistake, didn't take the time to see if it was a real word or not, just that it didn't look righ t:\