0000: 27 00 1a 02  00 00 00 00  00 00 00 de  ad de af 00    '... .... .... ....
0010: 55 2a bc 72  fc c6 01 76  65 72 2d 49  58 38 36 2d    U*.r ...v er-I X86-
0020: 30 2e 6d 70  71 00 00                                0.mp q..

bnls server closed connection.


whats wrong with my packet?
do i need the timestamp, i just set it to zero? what is it anyways? i am on linux, so creating such a timestamp is not just a function call...
do i need to replace the "ver" with "lockdown" to match the filename?

thanks for any help

First:
Is that what you are sending to BNLS or what BNLS is sending you?

Second:
If that is what BNLS is sending you, What are you sending BNLS?

this is what i am sending to the bnls... 0x1a aka BNLS_VERSIONCHECKEX2
immediately after i send it bnls closes the connection.

Regarding the timestamp battle.net sends you this and you pass it along to the BNLS server.

Since your not sending all the required information BNLS cannot parse the information correctly and just disconnects you.

a) your productID of 0x02 is fine
b) your flags of 0x00 are fine as well.
c) you receive the timestamp from battle.net in packet 0x50
d) since your productID is 0x02, i assume you are trying to connect with Broodwar, that being said, why are you replacing the file it sends you with "ver-IX86-0.mpq"? send the original file battle.net sends you to bnls.
e) your "formula" for hashing is null. you must supply this in the last string you sent to bnls.

ah i found the problem, i was using version byte 0xd2 instead of 0xd3