Re: Redsocks With Wanproxy
- Ali Jawad
- 2012-01-11 @ 20:33
Any input on this please ...
On Mon, Jan 9, 2012 at 2:09 AM, Ali Jawad <email@example.com> wrote:
> Hi I have a Wanproxy connection that speeds up a link between two remote
> WAN locations, Wanproxy listens on 0.0.0.0:80 as you all know not all
> devices support SOCKS and Wanproxy runs on SOCKS 5, so I want to redirect
> TCP connections to wanproxy so I can setup a SQUID proxy and VPN to
> redirect that traffic to Wanproxy, I did try tsocks and proxychains, those
> worked locally with Lynx but once SQUID or PPTPD entered the equation it
> stopped working.
> I am trying redsocks with the following config :
> local_ip = 127.0.0.1;
> local_port = 12345;
> // `ip' and `port' are IP and tcp-port of proxy-server
> // You can also use hostname instead of IP, only one (random)
> // address of multihomed host will be used.
> ip = 127.0.0.1;
> port = 80;
> and rest being default
> For Iptables I used
> 917 iptables -t nat -N REDSOCKS
> 918 iptables -t nat -A REDSOCKS -p tcp -j REDIRECT --to-ports 12345
> 921 iptables -t nat -A OUTPUT -p tcp -m owner --uid-owner alinux -j
> After that I switched to user alinux and did lynx www.whatimyip.com
> [alinux@CentOS54 darkk-redsocks-8839230]$ lynx www.whatimyip.com
> Looking up www.whatimyip.com first
> Looking up 127.0.0.1:12345
> Making HTTP connection to 127.0.0.1:12345
> Sending HTTP request.
> HTTP request sent; waiting for response.
> Alert!: Unexpected network read error; connection aborted.
> Can't Access `http://www.whatimyip.com/'
> Alert!: Unable to access document.
> lynx: Can't access startfile
> As you can see I got Alert!: Unexpected network read error; connection
> aborted, when I connect directly to the SOCKS proxy it works though. Please