Any way to connect via Localhost?

[Beitarist]

anyone know a way?

need it for some tests

[Power_Stunner]

on your own server?

[Beitarist]

Originally Posted by Power_Stunner

on your own server?

lol on hanin ><

[Kool_Savage]

hack the root (hanin).
intall kal online there.
start the luncher.
be happy^^

[Beitarist]

i cant belive i expected to get answer in this noob forum ><

[Alfonzo]

how u want connect to hanin as localhost?cO
u have to host the server to connect as localhost

[Beitarist]

Originally Posted by Alfonzo

how u want connect to hanin as localhost?cO
u have to host the server to connect as localhost

some project test...
anyways thats the only thing i need

what i mean is that insted login to server ip i connect to localhost
example insted login Bango i will connect localhost

[ChocoDuo]

You can inject a DLL that intercepts WSAConnect from Ws2_32.dll
and modify the pSockAddr->sin_addr param to connect to your localhost rather than the kal server.
This is how I've done it to connect to a local python script which acts as a proxy between kal and the server.

**edit**
to clear up what i mean by pSockAddr->sin_addr

the second param to WSAConnect is of type 'const struct sockaddr*', cast this to 'sockaddr_in*' to access the field sin_addr

[Beitarist]

Originally Posted by ChocoDuo

**edit**
to clear up what i mean by pSockAddr->sin_addr

the second param to WSAConnect is of type 'const struct sockaddr*', cast this to 'sockaddr_in*' to access the field sin_addr

i cant understand ur clear up :P
i will try to understand it when i back from work

but thx if it work ^^

[BenKiu]

only make fake dsn in your pc ;> and change to localhost (Network config.)

[ChocoDuo]

dsn is a dns typo? I'm not sure if this would work as kal attempts to connect directly to an IP, wont this will bypass any local DNS as the ip has already been resolved? (no idea about this though, never done something like this =)

Regarding my method, I'll try clear it up more.
WSAConnect has the following (C) prototype:

int WINAPI WSAConnect(SOCKET s, const struct sockaddr* name, int namelen, LPWSABUF lpCallerData, LPWSABUF lpCalleeData, LPQOS lpSQOS, LPQOS lpGQOS)
(from the win sdk)

the pararm 'name' contains connection information specific to the the socket type.
The socket type used in this case is AF_INET (internet) so we can cast 'name' from sockaddr* to the sockaddr_in* to access connection info specific to AF_INET connections i.e. IP and port.

And so, through the horrible syntax necessary to set the bytes of the ip address you can do this:

sockaddr_in* pSockAddr = (sockaddr_in*)name;
pSockAddr->sin_addr.S_un.S_un_b.s_b1 = 127;
pSockAddr->sin_addr.S_un.S_un_b.s_b2 = 0;
pSockAddr->sin_addr.S_un.S_un_b.s_b3 = 0;
pSockAddr->sin_addr.S_un.S_un_b.s_b4 = 1;

and then pass on the parameters to the original WSAConnect function ^^