L2Walker P2P BYPASS

[Lowfyr]

[pengpong]

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

[Lowfyr]

hey pengpong, keep up your work, I think the new bypass is not so handy like this one

perhaps you can get this method working again, that would be great

[apostolt]

Does this bypass work on private servers?How must i change the settings on tcpforward in order to connect to a private server?

[blahboy123]

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.

[steerk]

there iss an trojan and a sniffer inside the wpe packed version that hosted here on the side WHY ???

[lapo]

Originally posted by steerk@Jul 10 2005, 19:13
there iss an trojan and a sniffer inside the wpe packed version that hosted here on the side WHY ???

Becaust it IS a sniffer. Antivirus detects it as "hackingtool" It's not trojan.

[Lowfyr]

Originally posted by steerk@Jul 10 2005, 19:13
there iss an trojan and a sniffer inside the wpe packed version that hosted here on the side WHY ???