Author | Message | Time |
---|---|---|
tA-Kane | Found this packet in one of the debugging logs one of my users sent to me. I'm wondering, has anyone else seen this packet? If so, do you have a clue as to its meaning? | May 9, 2004, 8:02 AM |
iago | Do you have a dump of it? That might help a little. | May 9, 2004, 8:43 AM |
tA-Kane | Directly from my debugging log:[quote][Main]Message: BnetWind.ConnBnet.UnsupportedPacket [No Status] [Message: 0000009B|00 00 00 00 00 00 07 00 00 00 00 67 00 00 00 00 00 20 11 BA 0D F0 AD BA 43 75 62 00 30 0A D0 00 01 03 95 00 00 00 01 00 00 00 04 00 00 00 05 A1 B1 C1 D3 00 00 00 00 00 00 00 00 06 00 9E 60 06 00 9E 74 00 FF 0F A7 00 12 00 00 A1 B1 C1 D3 A1 B1 C1 D3 00 32 59 40 A1 B1 C1 D3 A1 B1 C1 D3 BA 43 75 62 65 44 69 76 00 36 23 50 6E 00 54 68 65 72 65 20 61 72 65 20 63 75 72 72 00 00 00 05 00 00 00 00 00 00 00 56 00 3F CE 20 00 00 00 56 00 00 00 01 06 00 9B 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 35 7B 00 00 00 00 00 00 00 00 00 08 20 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00][/quote] [Main] is the thread id. Obviously the code's path (BnetWind window, ConnBnet socket, UnsupportedPacket event) comes next, then comes a status code (not used in this case), then a textual message. In the textual message, there's the packet ID (0000009B = 0x9B), a vertical bar to seperate a field, and then the packet data. I looked at the packet data for a few minutes, and I couldn't make sense out of it..., other than a few seemingly cut-off strings? | May 10, 2004, 10:23 PM |