F7 1e 2a 00 03 00 00 00 00 00 Dp......*.......
00 00 00 e0 17 01 00 00 00 5a 65 72 67 00 01 00 .........Zerg...
02 00 17 e0 c0 a8 01 64 00 00 00 00 00 00 00 00 .......d........
I cant really make heads or tails of this. Any ideas? I guess this is the format.
(Byte) '03'
(DWord) '00 00 00 00' [Appears to be Constant]
(DWord) '00 00 00 00' [Appears to be Constant]
(Word) 'E0 17' [Port 6112 {Reversed?}]
(DWord) '01 00 00 00' [Game Count 1,2,3,etc]
(String) '5a 65 72 67 00' [Account Name: Zerg]
(Word) '01 00' [Appears to be Constant]
(Word) '02 00' [Appears to be Constant]
(Word) '17 e0' [Port 6112]
(DWord) 'c0 a8 01 64' [Local IP: 192.168.1.100]
(DWord) '00 00 00 00' [Appears to be Constant]
(Dword) '00 00 00 00' [Appears to be Constant]
Where's the first 6 bytes?
I'm going to guesst they're of another packet...
The packet logs are from Ethereal and the bytes removed where the extra stuff bnet didnt send
i have this in my wc3-netcode-docs:
f7 | its wc3, after all ;P
1e | let me in!
2a 00 | 42 bytes long
ef 1f 00 01 | gameid
ff 2e 80 00 | timestamp(?)
00 | always(?) 0x00
e0 17 | hum, 0x17E0 is my port (6112)
01 00 00 00 | always(?) 0x01000000
6d |m
6f 6f 68 00 |ooh -> 'mooh' was my nickname in that lan-game
01 00 | always(?) 0x1000
02 00 | always(?) 0x2000
28 91 | wtv-port... // 17E1 in my lan (6113->my port)
c0 a8 01 25 |-> 192 168 001 037 => ip-address of the client
| and why the heck are the above 6 bytes in 'wrong' byte-order?
00 00 00 00 | always(?) 0x00000000
00 00 00 00 | always(?) 0x00000000
look at what i have tagged gameID...
wired that your timestamp (better: what i guess could be a timestamp) is 0x00000000
are you using linux? i get 0x00000000 with my boxes too if i recall correct...
this packet comes from wtv (probably with a windoze-using streamer)
but i am 100% sure that the u_int32_t following the length is the gameID (or gamecount as you call it)
in your packet it was your 3rd lan-game i suppose...
hope this helps.
p.s. oh, yes: hi forum, first post for me :)