Question about packet analysers / sniffers

Hello.

I have a totally noob question about packet analysers/sniffers for silkroad.

Can they be used on client-end only, for example on private servers for development purposes (programming an auto target), or they only work when using inside the server machine?

I mean cause you gotta specificy the ip/port for proxying the game, is it possible to do it at the client side?

Quote:

Originally Posted by LuigiChase Hello. I have a totally noob question about packet analysers/sniffers for silkroad. Can they be used on client-end only, for example on private servers for development purposes (programming an auto target), or they only work when using inside the server machine? I mean cause you gotta specificy the ip/port for proxying the game, is it possible to do it at the client side?

Yes, that's where it all started. Filters are just an extension of the proxies we used to sniff and inject packets with. They're made to work with multiple connections instead of a single connection to the host. Now the proxies a built into the bot itself rather than being a separate application like phConnector or nuConnector back in the days.

You'll still need to redirect the client to the [Only registered and activated users can see links. Click Here To Register...] on your local machine either by patching [Only registered and activated users can see links. Click Here To Register...] using [Only registered and activated users can see links. Click Here To Register...] (can't find the binary anymore) or IPInput.
You can also detour on WSAConnect as for example [Only registered and activated users can see links. Click Here To Register...] and other loaders are doing with their redirect features.

Quote:

Originally Posted by DaxterSoul Yes, that's where it all started. Filters are just an extension of the proxies we used to sniff and inject packets with. They're made to work with multiple connections instead of a single connection to the host. Now the proxies a built into the bot itself rather than being a separate application like phConnector or nuConnector back in the days. You'll still need to redirect the client to the [Only registered and activated users can see links. Click Here To Register...] on your local machine either by patching [Only registered and activated users can see links. Click Here To Register...] using [Only registered and activated users can see links. Click Here To Register...] (can't find the binary anymore) or IPInput. You can also detour on WSAConnect as for example [Only registered and activated users can see links. Click Here To Register...] and other loaders are doing with their redirect features.

Interesting! Thanks for the reply and all the info.

I initially had the question because all the videos I could find of people using sniffers or packet readers was done inside the server.

So let me see if I got it right, the ip/port used on the proxy will be the ones I patch, not the original server ones. Does this work on any pserver?

Thanks mate!

You patch the client to connect to 127.0.0.1 on a port specified by the proxy config and in there you also have to enter the address of the private servers gateway server which you overwrote with the 127.0.0.1.

It might not work on all pservers some employ things that will prevent you from doing these things. As it'll trigger their bot detection.