Is there any documentation on a site or even under bnetdocs that I've missed refering to 0x1C, 0x3C, and 0x10?
None of those packets are publicly documented on BnetDocs, no.
Quote from: Arta[vL] on May 01, 2003, 03:09 PM
None of those packets are publicly documented on BnetDocs, no.
Since your in control of BNetDocs (I assume), would those packets be something you may add in the future?
and wether or not you do, perhaps you could tell me where I could find something to get by for the time being? :P
You can find something by packetlogging and/or reverse engineering.
It's not hard, though, I figured out how they work, for the most part, from packetlogging.
If anyone has a link or something to some info about them, then by all means paste it plz. But I will go ahead and start trying it on my own. Perhaps someone could tell me a good packet sniffer/logger to download that's free and easy to set up and use?
Ethereal is your best bet, but it's not immediately obvious how to use it. I will tell you that 0x3C is almost certainly irellevent for whatever you're doing, and the other two aren't too hard to figure out.
Is it possible to download Ethereal already compiled?
If so, do you know the URL for it? heh
sorry for asking so much of ya
Quote from: Dugs on May 01, 2003, 04:10 PM
Is it possible to download Ethereal already compiled?
If so, do you know the URL for it? heh
sorry for asking so much of ya
http://www.google.com :P ;D
heh, ok thanks..
I searched before only to find source code, but didn't look that hard either. I got it downloading now tho, 56k
:(. I would still appriciate anything that would help me to learn what each of the packets contain and the responses for them. :P
http://www.ethereal.com/distribution/win32/
Perhaps you should start reversing?? I would say the best way to figure out what a packets purpose is, is to actually see how starcraft handles it. If you need a starting point i'm sure someone like adron, grok, or skywing can provide an address for you, or you could ask my brother (he doesn't use this community as often as he uses www.gamethreat.com or www.schackit.com community(ies)).
www.ethereal.com
"Sniffing the glue that holds together the internet!"
Quote from: Maddox on May 01, 2003, 07:57 PM
There are a lot more packet documentation on BnetDocs, but you have to be a "priviliged" user to view it. A lot of those packets are documented in other places publicly.
BnetDocs is the best I've found in a long time refering to documentation on packets. If you know a site that has other info on some of the packets not released to the public through bnetdocs, I'd appriciate tips on how to find it. A url would be a really good tip by the way. :P
Quote from: XTRB on May 03, 2003, 11:43 AMIf you know a site that has other info on some of the packets not released to the public through bnetdocs, I'd appriciate tips on how to find it.
http://botdev.valhallalegends.com
This site, run by Spht, contains a lot of information, as well as a heck of a lot more instructions and examples.
You know how Ethereal parses OSCAR and etc.? Do you think we could make one that parses b.net?
Quote from: St0rm.iD on May 03, 2003, 03:14 PMYou know how Ethereal parses OSCAR and etc.?
I've never used Ethereal.
Quote from: St0rm.iD on May 03, 2003, 03:14 PM
You know how Ethereal parses OSCAR and etc.? Do you think we could make one that parses b.net?
I have no idea how protocol parsers are implemented in Ethereal. They're not DLLs (judging by a quick glance in C:\Program Files\Ethereal). But I note the main executable, ethereal.exe, is 7.8mb. So maybe they're all compiled in the exe.
Ethereal is open source. If you're that interested in it, get the source, write the parser, recompile and enjoy. :)
Quote from: Yoni on May 03, 2003, 06:04 PM
Quote from: St0rm.iD on May 03, 2003, 03:14 PM
You know how Ethereal parses OSCAR and etc.? Do you think we could make one that parses b.net?
I have no idea how protocol parsers are implemented in Ethereal. They're not DLLs (judging by a quick glance in C:\Program Files\Ethereal). But I note the main executable, ethereal.exe, is 7.8mb. So maybe they're all compiled in the exe.
Ethereal is open source. If you're that interested in it, get the source, write the parser, recompile and enjoy. :)
you have to write a dissector; it's 1000x harder than it should be
if you want to do the world a favour, write a plugin to create "virtual" dissectors without compiling