Proxying over a WAN using SOCKS

Juli Mallett juli at
Mon Apr 11 03:18:55 PDT 2011

On Mon, Apr 11, 2011 at 03:04, Carlos Becker
<f0877e61f2f879f5a1244afbbc63a01c at> wrote:
> Hello,
> On this page in the second example
> "Proxying over a WAN using SOCKS" on which port does the SOCKS server listen on ?

That's not as simple a question as it sounds like :)  Because we want
all of the traffic that goes over the proxy to be compressed, what we
do is compress the connection between the local proxy and the remote
proxy.  In the example, the local proxy listens on port 3300.  This is
what you'd configure a SOCKS client to connect to.

What happens then is that data that arrives on port 3300 is compressed
and sent to port 3301 on the remote proxy.  The remote proxy then
decompresses it and sends it to its local port 3302, which is where
the actual SOCKS proxy is listening.

So really, the SOCKS proxy listens on port 3302 on the remote (server)
proxy.  The local (client) proxy listens on port 3300.  Traffic coming
in port 3300 on the local proxy appears on port 3302 of the remote
proxy, at which point it connects onward to the destination specified
by the SOCKS client (e.g. your browser, IRC client, whatever.)

I hope that makes sense.  If it doesn't, please let me know and I will
try to explain it a different way or provide a small diagram or

> Is there any detailed/illustraded documentaion about wanproxy around ?

Not really.  You're welcome to write some :)

More information about the wanproxy mailing list