COPROXY

Quote:

Originally posted by GiYo@Aug 28 2005, 10:08 is it just me or were the attached scripts (paths) patched too?

Oo, how could they patch a path? i mean, how can u NOT walk tru those coords, and for the lol guy, first post totally screwed

I get Run-Time error 13
Type Mismatch when I try running a loaded path.

i dont get how to use this, help please



how do i send the packets? im confoosed.

how can the dove beeps????? is that possible?

hey guys... can u put the changed file of the server.dat coz i cant edit it.... plz help...

btw... im on eternity server

CO Proxy 1.2 Can't work now... on CO1... Bad connection... Log off automatically......

How to GET INTO BOT JAIL.... Someone help me pls...

YESSSSSSSSSS thANK u man I cant thank u enough for this.


PS guys if u wanna go to metzone or sumwhere fast cast divine hare and cyclone together it makes superspeed. :D :D :D

hmm does this work on co2... because i know for a fact that the servers running , but i cant get on when coproxy is on any help, it says the server is down error if that helps

does anyone know a hack for item creater or for like in gw u want to program it for to go back to tc when u rev?

My proxy program is doing the same thing as well "Bad Connection". All I can figure is the client is sending the server the client side connection port, then the server queries its own tcp/ip stack for the remote connection port and if they don't match BANG! not the most reliable of methods tho'. They could of course send OOB data to the client to detect a proxy on the next port number, but that would be a federal crime.

I doubt that the client tells the server what port it's on. IP Masquerading (read NAT) would fail for more than one client behind it. However, you can play conquer on multiple computers behind a NAT. Also, the RFC standard for NAT says nothing about what external port must be chosen for a connection. It is weird that you are getting "Bad Connection" problems. I have also been getting these recently with the actual CO client (and my bot, but that's a different story) so maybe it isn't the proxy's fault. If you would like, I could help you figure out what is going on. I also have an idea for a project somewhat like this. PM me if you're interested.

It seems to happen a lot when using a decrypting/re-encrypting proxy. Just a straight TCP redirector seems fine. The only other thing I can think of is some kind of extra sequence data buried in the protocol somewhere, So although when you are injecting and altering packets correctly (without the clients or server's knowledge) there may be some kind of data being sent from the client informing it where IT THINKS the key sequence should be, and if the server disagrees with that, bad connection....

still works for me
i dont think ive changed anything
bad connection is when you send the tick packet and its time values are greater than 15 seconds

that packet being 0x3f1 type 0x1b yea?

Funnily enough, it's stopped doing it now, been ok for a few days so I dunno.