[VB] UDP Header

[PaiD]

Does any1 have any information on the UDP Protocol Header?

[iago]

http://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/udp.html

This is based on RFC 768:
http://www.ietf.org/rfc/rfc0768.txt?number=768

[Grok]

http://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/udp.html

This is based on RFC 768:
http://www.ietf.org/rfc/rfc0768.txt?number=768

So, iago, now tell me why most well known ports are odd.  

[iago]

http://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/udp.html

This is based on RFC 768:
http://www.ietf.org/rfc/rfc0768.txt?number=768

So, iago, now tell me why most well known ports are odd.  

Because programmers are odd, and they wanted to feel comfortable.

[PaiD]

Ok thx for the sites but I was talking about Starcraft udp

[Adron]

Ok thx for the sites but I was talking about Starcraft udp

Perhaps you should've said so then? You can't expect a good answer if you don't ask a clear and well-formulated question.

The Starcraft UDP headers are very much like the D1 UDP headers. They're numbered and have seq and ack fields. There's a mechanism to request retransmission of lost packets. There's a packet class field, with separate numbering for each packet class. There's a packet type field, for packets like game ticks, join game, ping game, etc. There's a checksum of the packet contents, perhaps so it would be harder to fake packets, or to safeguard against corrupted packets on modem/IPX or similar.

[CodeMaster]

Very true, he said UDP and realizing this is not a Bot Dev forum. This is specfically a Visual Basic Programming forum, so what format of UDP he is referring to is a mystery without his directon.

[iago]

Very true, he said UDP and realizing this is not a Bot Dev forum. This is specfically a Visual Basic Programming forum, so what format of UDP he is referring to is a mystery without his directon.

Thanks for explaining my joke

[UserLoser.]

...
The Starcraft UDP headers are very much like the D1 UDP headers. They're numbered and have seq and ack fields. There's a mechanism to request retransmission of lost packets. There's a packet class field, with separate numbering for each packet class. There's a packet type field, for packets like game ticks, join game, ping game, etc. There's a checksum of the packet contents, perhaps so it would be harder to fake packets, or to safeguard against corrupted packets on modem/IPX or similar.

Perhaps you can elaborate some more on the format, along with checksum?

[Adron]

What more is there to say? I think I've covered most there is in it.. The checksum is a simple 16-bit one, nothing special, and it's calculated over the whole packet with the checksum spot zeroed out.

[iago]

It's CRC32.  No it isn't.

[UserLoser.]

What more is there to say? I think I've covered most there is in it.. The checksum is a simple 16-bit one, nothing special, and it's calculated over the whole packet with the checksum spot zeroed out.

Storm.dll address?

Edit: Changed location to address due to smart response

[Spht]

What more is there to say? I think I've covered most there is in it.. The checksum is a simple 16-bit one, nothing special, and it's calculated over the whole packet with the checksum spot zeroed out.

Storm.dll location?

That depends on where you installed the game.  For Starcraft, mine's in D:\Games\Starcraft\.

[iago]

What more is there to say? I think I've covered most there is in it.. The checksum is a simple 16-bit one, nothing special, and it's calculated over the whole packet with the checksum spot zeroed out.

Storm.dll location?

That depends on where you installed the game.  For Starcraft, mine's in D:\Games\Starcraft\.

haha, that was great.