?Protocol byte?

[PaiD]

um This is a newb question but still what is Protocol byte?

Code Select Expand

SEND -> Protocol byte (01)
SEND -> SID_AUTH_INFO (0x50)
RECV <- SID_PING (0x25)
RECV <- SID_AUTH_INFO (0x50)
SEND -> SID_PING (0x25) [Optional]
SEND -> SID_AUTH_CHECK (0x51)
RECV <- SID_AUTH_CHECK (0x51)
SEND -> SID_LOGONRESPONSE (0x29)
RECV <- SID_LOGONRESPONSE (0x29)
SEND -> SID_UDPPINGRESPONSE (0x14) [Game Specific: SEXP/STAR/W2BN]
SEND -> SID_ENTERCHAT (0x0A)

I think it is just a null right?

Edit: null*

[Eibro]

A byte sent from C->S notifying the server of the protocol used by the client. I believe 0x01 is binary, while 0x03 is chat.

[haZe]

0x02 is ftp.

[tA-Kane]

/me wonders if there's a "server" protocol byte

[Arta]

Elaborate?

[tA-Kane]

Well, actually, I don't think it's so much an "if" as a "how does it work", but...

The idea behind my question is that the servers obviously connect to eachother, how close to the game-client protocol is the server protocol? And, more deviously, how hard would it be to connect yourself to Battle.net as a server?

I suppose some of these might be better asked/answered privately, to keep out of the wrong hands. Wouldn't want Blizzard to take some sort of unforseen neo-nazi action...

[Banana fanna fo fanna]

I'll venture a guess and say that they use UDP broadcast on the local LAN, behind firewall.

[Yoni]

My guess is that they only accept LAN IPs, or IPs from some list, as servers.