probably you're not interested anymore in this, since there's a new workaround, but i want give you a short update on my work:
I'm able to log in with 10.4.7 to my private server aswell to official servers (i only modified some memory values, i don't need to install a loopback device, nor run tcptunnel...)
So far the good news, the bad news is that i get disconnected from the gameserver after a couple of secs
But i'm still working on it... nobody knows how long the new workaround will work
Ok, guys...here is what happens in case people are confused about the process.
Step 1: Loopback adapter
Loopback adapter is a way of saying, if you are going to this address...don't and go back to the localhost instead. For example, we set the loopback adapter to be the korean game server. This means that anytime some program tries to contact the gameserver, they get rerouted back to your local machine. Since the program doesn't do the encryption thing when connecting to the korean server, we can bypass the 'verify fail' error.
Step 2: Port forwarding
What we did in step 1 is useless, if we do nothing once the program gets rerouted back to the local machine. Your local machine doesn't have a server running, so it can't do anything. So, what TCP tunnel does is that it listens on a certain port (2106) and as soon as it sees that connection, it forwards it to the US server. The L2walker thinks its connecting to the korean server, but we 'rereoute' it back to the US server.
Step 3: WPE Pro
OK, well we sent the info to US server, but the problem is that Korean and US servers are on different protocols. Since L2walker thinks its connecting to the Korean server, it uses the korean server protocol automatically (regardless of whats specified in the INI). However, we don't want that and there is no way to change this value in L2walker itself. So what we do is get a program called WPE pro and tell it to 'listen' to what l2walker is doing, and when it tries to send the Korean protocol, change it to the US protocol. That's all it does.
So the L2walker is still 'thinking' its using the Korean protocol, but we modify the data BEFORE and AFTER it gets to/reaches L2walker.
Conclusion: WPE Pro did not change your password smile.gif. These tools are only usually used by Network Administrators, and were never meant for the layman.
l2walker IG for l2dreams with bypass HELP!! 07/28/2010 - Lin2 Exploits, Hacks, Bots, Tools & Macros - 5 Replies can anyone post new links for new l2walker in l2dreams Still Verify Fail !!
ANY HERO ??
L2Walker Ingame Bypass 02/19/2010 - Lin2 Exploits, Hacks, Bots, Tools & Macros - 53 Replies i got ingame walker 1.50/1.51 working after the verify changes using xen's verify emulator. follow the guide below and u have at least ingame walker again :happy:.
1) you need the verify emulator made by xen, but i think any other will do it also. if you dont have it yet you can get it here:
http://rapidshare.de/files/9040358/L2W_All.EXE.ht ml
Also you might want to download the newest version of l2walker, for that look at http://www.towalker.com/
direct links:...
L2Walker 1.6.0 bypass 11/22/2005 - Lin2 Exploits, Hacks, Bots, Tools & Macros - 9 Replies The idea is to create a tunnel and trick l2walker auth system with that.
I had no luck with it since instructions are in thai or something like that.
Can you pls help me to understand how this crack work?
EDIT: ok, I read more deeply through the threads and I found out that you knew about this already. So I'm sorry for the oldness of the trick.
Since you could make this work, can you explain me in English how the stuff works?
Thx in advance for help.
RE-EDIT: I got that stuff working...
