guys lets make a packet sniffer...

Hello guys,
We all know that packet hacks EXIST... invisible, bypass errors and etc...
So lets for a group and make a packet sniffer for crossfire... i know people who can tell us how the decrypt and such things... I have info about login packet and i am interested in making bypass for banned acc, region info, and such things... BUT we need a proxy to catch the packets edit them and then release them...

the normal way of the packets id : MyClient ---> Server ---> MyClient

...so we need an ap that does this:

MyClient ---> MyDotNetproxy (c# or vb, idk on what else to make it) ---> Server ---> MyDotNetproxy (c# or vb, idk on what else to make it) ---> MyClient

understand ?
post your ideas here and lets make it like a ONE TEAM...

and i think that the game wont lagg bcs... you proxy is very close and the connection will remain fast

-You can hook into WinAPI functions.
-A "general" packet sniffer is harder, because you have to hook into some network card stuff or hook into some functions with drivers.
You can't create a driver with Visual Studio Express unless you find some plugins for it.
-If you want to make a proxy, you first have to change the URL of version.ini to the URL of a modified one with a different game server IP and change the lobby server IPs in the incoming login packet and change the game server IPs. You should create multiple Sockets, else you won't longer know which connection is for which server.
CrossFire uses UDP for the game servers and TCP for the lobby and login server.

I have been making pcaps of short cf sessions so i can exam the packet structure and stuff so i can work on a project that isnt a hacking one. I didnt know your login id and password are sent across the internet in plain text and the server sends packets with server info everytime you try to login in; which also sends along someones IGN which i though had something to do with the login id but they have no connection, atm they just seem like random usernames. I havent gotten much into the packets but i have been noticing patterns and such. my next step is to record these sessions so i can watch them to try to better figure out whats going on.

you know anything at kernel mode?