Posted: Mon Jan 01, 2007 9:19 am Post subject: WPE not reading game packets ?
Hello everyone,
Im somewhat new to hacking, basically in the stages of collecting tutorials and tools to use (which is increasingly difficult with dead links, disappearing sites, and millions of useless posts). Anyway back to my question:
I'm using WPE which I collected from curse-x website on an online game I had "assumed" was lightly protected, but when I target the game and hit play I get nothing, no packets sent/recieved, just dead air. I attached it to my browser and everything seemed to be reading just fine?
I figured it had some shield blocking me, but as far as I can tell there is none, I looked though filemon (I believe is the name) trying to see if any process was just being sneaky and stopping me, but I've come up with nothing I can tell. The worst thing about learning is being stumped before I even start...
If anyone has any ideas or a direction they could point me to it be much appreciated.
thang.ongameport. com/data/down.asp?mainValue=01&subValue=01_01
Here is the game if anyone would like to take a look.
p.s. sry it wont let me post urls yet. just delete the space between the . com
Joined: 09 Aug 2006 Posts: 146 Location: In your washing machine
Posted: Mon Jan 01, 2007 10:46 am Post subject:
make sure you got it on all types of packet send/receive functions
send,sendto,wsasend,wsasendto etc etc depending if you want to listen to reveived or sent packets
if that doesnt work, are you sure its hooked to the right process
and if it is the process most likely uses its own packet sending function, not the usual ones that come with the windows libraries _________________
Give a man a fish; you have fed him for today. Teach a man to fish; and you have fed him for a lifetime.
Dynamic memory is my playground..
Yes, you were right. WPE's interface is pretty user friendly and I had thought I had missed with most of the options on it.
At first I wondered if it did use it's own packet protocol, so I ended up hunting down another packet reader(s). These were reading the same packets winsock should have been able to pick up. So I went back and looked through WPE options (*sighs at how simple this turned out to be*). Turns out I didn't try clicking on the winsock functions drop down list, and change it to 2.0, and turn on the send/receive options there....
Thankyou for the answer, sry about the late reply.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum