Endian problem in SOCKS support

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set up a socks proxy (e.g. ssh’s -D dynamic proxy)
2. Attempt to connect to a transmission daemon on the remote end using the 
normal port of 9091
3. Note that transmission-remote-gui attempts to connect to port 33571 instead.

9091 in hexadecimal is 0x2383
33571 in hexadecimal is 0x8323.

So the bytes of the port are being swapped around (or more likely *not* being 
swapped when they should be: x86 architecture is little-endian while network 
order is big-endian).

Original issue reported on code.google.com by ha...@hawkesnest.net on 5 Jul 2013 at 6:27

[GoogleCodeExporter]

I just noticed this now while attempting to connect from out of town via a ssh 
tunnel to my server at home. Saw the port move to 33571 when I kicked on 
verbosity on ssh during the tunnel session.

Any idea when this can be looked into?

Original comment by pyr0...@gmail.com on 22 May 2014 at 3:42

[GoogleCodeExporter]

It was working well for me through a socks5 proxy (shadowsocks) to connect 
remotely in Windows. Today I tried to use the same setting for the same server 
but under Ubuntu, and it failed. Your ticket helped me, I set the port to 33571 
(the actual port is 9091), transgui could connect again. So I think this is 
only an issue under Linux?

Original comment by HaT...@gmail.com on 11 Dec 2014 at 4:14

[GoogleCodeExporter]

Thanks for the workaround, this issue has been bothering me for well over a 
year.

Original comment by torkelat...@gmail.com on 6 Apr 2015 at 1:14