Being my first post here, and being lazy I'll just introduce myself by saying: Hello World! (hoping 1 person finds that funny)
Anywho, I think I'll need a packet sniffer to 'listen' to messages I recieve in channel on Diablo II (trying the LEAST detectable methods). Tried searching and only found Ethereal repeatedly. I need something smaller, like a SIMPLE DLL to work with.
I already played around with Ethereal and PlasticSniffer, both returned bits and pieces of the message, but I don't understand how to 'decode' the packets from them?
I'm hoping I won't be a bother to you, I've used so many programs originating from VL (Chewbacca Bot is my all time FAVORITE bot) all I can say is thank you.
WPE Pro (http://skull.newrelic.net/downloads/uploads/packet%20logger.zip) should work fine for you as a packet logger.
Also BNetDocs (http://bnetdocs.valhallalegends.com) Is a good site to learn about packets.
~-~(HDX)~-~
Ethereal uses "PCap" (Packet Capture -- the Windows version is called WinPCap). It's a packet-capturing utility/library that you can use.
WPE PRO
Quote from: hismajesty[yL] on December 23, 2004, 09:40 AM
WPE PRO
/me points to my link....
Its wpe pro, simple to use just like he wants, just click the program u wana log, and hit play. Not that had.
~-~(HDX)~-~
the site for WPE would be www.fly.to/mtc
Quote from: HdxBmx27 on December 23, 2004, 10:22 AM
Quote from: hismajesty[yL] on December 23, 2004, 09:40 AM
WPE PRO
/me points to my link....
Its wpe pro, simple to use just like he wants, just click the program u wana log, and hit play. Not that had.
~-~(HDX)~-~
Use better naming.
Isn't AutoIt what people use to make pindlebots?
WPE Pro is easy to use. I stopped using errrr barely even used, Ethereal because I could seem to get rid of that dang header thingy that accompanied the packets I recieved
Instead of recieving the regular BNCS packet header + packet I would recieve a bunch of bull crap then the BNCS packet header + packet.
Quote from: Sorc.Polgara on December 23, 2004, 08:31 PMInstead of recieving the regular BNCS packet header + packet I would recieve a bunch of bull crap then the BNCS packet header + packet.
I like how you refer to the TCP/IP header as "bull crap". I'd like to think it has its uses.
Quote from: EpicOfTimeWasted on December 23, 2004, 08:53 PM
Quote from: Sorc.Polgara on December 23, 2004, 08:31 PMInstead of recieving the regular BNCS packet header + packet I would recieve a bunch of bull crap then the BNCS packet header + packet.
I like how you refer to the TCP/IP header as "bull crap". I'd like to think it has its uses.
errr my fault, I mean "bull crap" as in, I don't need it for packet logging what I trying to packet log.
how do i exclude it from the packet logging?
Quote from: Sorc.Polgara on December 23, 2004, 09:16 PM
Quote from: EpicOfTimeWasted on December 23, 2004, 08:53 PM
Quote from: Sorc.Polgara on December 23, 2004, 08:31 PMInstead of recieving the regular BNCS packet header + packet I would recieve a bunch of bull crap then the BNCS packet header + packet.
I like how you refer to the TCP/IP header as "bull crap". I'd like to think it has its uses.
errr my fault, I mean "bull crap" as in, I don't need it for packet logging what I trying to packet log.
how do i exclude it from the packet logging?
There should be a function to follow tcp stream or something similar that will display the raw contents of the tcp stream in a nice format.