Speed Up WAN Link..Ideas needed

Thu Dec 22 13:53:28 PST 2011

Hi Juli
Any other info I can provide ?
Thanks

On Wed, Dec 21, 2011 at 12:02 AM, Ali Jawad <alijawad1 at gmail.com> wrote:

> Hi Juli
> I did try different codecs and monitored the client and server, the
> problem happens with xcodec after leaving it on for a while the client
> crashes, when I start it and browse anything it just keeps crashing. This
> stops to happen when I restart wanproxy on the server.
> Thanks
>
>
> On Tue, Dec 20, 2011 at 2:55 AM, Ali Jawad <alijawad1 at gmail.com> wrote:
>
>> Hi Juli
>> I will certainly try to track down the crash by using each codec alone
>> and both together and none, having said that can you please post a config
>> example of both working together, the example I am using from the site only
>> makes use of xcodec, I was able to use zlib but I am not sure how to
>> combine both to work. Another thing is that some of the users have
>> ipads/iphones and other devices that are not SOCKS friendly, any
>> suggestions on how to allow those devices to utilize the enhanced WAN link
>> ?
>> Regards
>>
>>
>> On Mon, Dec 19, 2011 at 10:45 PM, Juli Mallett <juli at clockworksquid.com>wrote:
>>
>>> On Mon, Dec 19, 2011 at 11:03, Ali Jawad <alijawad1 at gmail.com> wrote:
>>> > Hi
>>> > I have to note that I did do the testing with a partner at a different
>>> > physical location. My Linux laptop with FF and Chrome did not cause a
>>> crash,
>>> > his Chrome/FF and IE caused the crash. I will retest with him today
>>> and let
>>> > you know results. What is better to use in terms of speed zlib or
>>> xcodec ?
>>> > Regards
>>>
>>> At this point I would suggest not disabling either one.  XCodec does
>>> the deduplication that is at the heart of WAN Optimization — it
>>> remembers chunks of data across many connections to reduce the amount
>>> of data sent over the network.  zlib does ephemeral compression,
>>> taking the output of XCodec and compressing it using a standard
>>> compression algorithm.  The two work together quite well.  I would
>>> like to track down and fix the crash you saw.
>>>
>>> > On Mon, Dec 19, 2011 at 4:12 AM, Juli Mallett <juli at clockworksquid.com
>>> >
>>> > wrote:
>>> >>
>>> >> Neither of those errors is necessarily bad.  A lot of connections get
>>> >> closed that way.  The thing about the deflate stream not ending neatly
>>> >> is also not uncommon.  Were you able to access websites with that
>>> >> configuration?  It's the crash that you saw earlier that concerns me
>>> >> as long as everything else is working alright.
>>> >>
>>> >> On Sun, Dec 18, 2011 at 15:38, Ali Jawad <alijawad1 at gmail.com> wrote:
>>> >> > Hi
>>> >> > My initial settings are same as the
>>> >> >
>>> >> > Proxying over a WAN using SOCKS
>>> >> >
>>> >> > Example, in this example Zlib is not enabled and I get the error
>>> >> > mentioned
>>> >> > in the last emails, upon disabling xcodec and enabling zlib as in
>>> the
>>> >> > config
>>> >> > example "only relevant top part" I get this error :
>>> >> >
>>> >> >
>>> >> > Server
>>> >> >
>>> >> > create codec codec0
>>> >> > #set codec0.codec XCodec
>>> >> > #activate codec0
>>> >> >
>>> >> > set codec0.compressor zlib
>>> >> > set codec0.compressor_level 6
>>> >> > activate codec0
>>> >> >
>>> >> >
>>> >> > Client
>>> >> >
>>> >> > create codec codec0
>>> >> > #set codec0.codec XCodec
>>> >> > #activate codec0
>>> >> >
>>> >> > set codec0.compressor zlib
>>> >> > set codec0.compressor_level 6
>>> >> > activate codec0
>>> >> >
>>> >> >
>>> >> > I get this error :
>>> >> > 1324250995.222191 [/wanproxy/proxy/proxy0/connector] ERR: void
>>> >> > ProxyConnector::splice_complete(Event): Unexpected event:
>>> <Error>/104
>>> >> > [Connection reset by peer]
>>> >> > 1324250995.222342 [/zlib/deflate_pipe] ERR: virtual
>>> >> > DeflatePipe::~DeflatePipe(): Deflate stream did not end cleanly.
>>> >> >
>>> >> > When I commented out the activate codec line using the same config
>>> >> > copied
>>> >> > above I got this error :
>>> >> >
>>> >> > 1324251200.589366 [/wanproxy/proxy/proxy0/connector] ERR: void
>>> >> > ProxyConnector::splice_complete(Event): Unexpected event:
>>> <Error>/104
>>> >> > [Connection reset by peer]
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > On Mon, Dec 19, 2011 at 1:38 AM, Ali Jawad <alijawad1 at gmail.com>
>>> wrote:
>>> >> >>
>>> >> >> Hi
>>> >> >> Did svn up to 897 ..did make clean and called make, will update
>>> with
>>> >> >> results, if I get errors will disable zlib and report back as well.
>>> >> >> Regards
>>> >> >>
>>> >> >>
>>> >> >> On Mon, Dec 19, 2011 at 1:34 AM, Juli Mallett <
>>> juli at clockworksquid.com>
>>> >> >> wrote:
>>> >> >>>
>>> >> >>> I meant the binary on both the client and the server.
>>> >> >>>
>>> >> >>> To disable zlib, just comment out or remove the lines like these
>>> in
>>> >> >>> each codec configuration.
>>> >> >>>
>>> >> >>> set codec0.compressor zlib
>>> >> >>> set codec0.compressor_level 6
>>> >> >>>
>>> >> >>> But actually, it would probably be best for you to just update and
>>> >> >>> rebuild without changing your configuration.  Just do "svn up" at
>>> the
>>> >> >>> top level directory and do "make clean" and "make" in
>>> >> >>> programs/wanproxy.
>>> >> >>>
>>> >> >>> Thanks!
>>> >> >>> Juli.
>>> >> >>>
>>> >> >>> On Sun, Dec 18, 2011 at 14:28, Ali Jawad <alijawad1 at gmail.com>
>>> wrote:
>>> >> >>> > Hi
>>> >> >>> > First of all, let me express my appreciations for all the
>>> support
>>> >> >>> > and
>>> >> >>> > help,
>>> >> >>> > Open source products are the result of collaboration between the
>>> >> >>> > people
>>> >> >>> > who
>>> >> >>> > do the hard work like yourself, and people who make use of the
>>> >> >>> > creativity/productivity of people like yourself, that would be
>>> me
>>> >> >>> > :).
>>> >> >>> > So I
>>> >> >>> > do not mind doing some testing and debugging.
>>> >> >>> > Having said that, you want me to make clean and make recompile
>>> at
>>> >> >>> > the
>>> >> >>> > trunk
>>> >> >>> > level ? How to test without zlib/zcodec ? Removing parts of
>>> config ?
>>> >> >>> > The
>>> >> >>> > only binary I am using is wanproxy that I copied to /usr/sbin/
>>> did I
>>> >> >>> > miss
>>> >> >>> > something here ? What is the second binary ?
>>> >> >>> > Regards
>>> >> >>> >
>>> >> >>> > On Mon, Dec 19, 2011 at 1:24 AM, Juli Mallett
>>> >> >>> > <juli at clockworksquid.com>
>>> >> >>> > wrote:
>>> >> >>> >>
>>> >> >>> >> I thought I had fixed this problem.  You are using both zlib
>>> and
>>> >> >>> >> xcodec, right?  I do not understand how this error could still
>>> be
>>> >> >>> >> happening.  If you could try with only xcodec or only zlib,
>>> that
>>> >> >>> >> might
>>> >> >>> >> be helpful to me, so I know which component is in need of
>>> further
>>> >> >>> >> testing.
>>> >> >>> >>
>>> >> >>> >> Also, if you want to update the whole tree and rebuild both
>>> >> >>> >> binaries,
>>> >> >>> >> I've added some messages which should make it easier to tell
>>> which
>>> >> >>> >> PipeProducer subclass is doing the wrong thing here.
>>> >> >>> >>
>>> >> >>> >> Apologies for all the difficulty.  I want you to know that I
>>> have
>>> >> >>> >> been
>>> >> >>> >> testing this, and did originally see the problem you report
>>> here,
>>> >> >>> >> but
>>> >> >>> >> did find a way to fix it.  I have some work I need to do today
>>> that
>>> >> >>> >> I
>>> >> >>> >> do not want to disrupt, but I am hoping that later in my
>>> evening
>>> >> >>> >> (I'm
>>> >> >>> >> on the west coast of the US) I will be able to set up a few
>>> more
>>> >> >>> >> systems to use in testing, and see if I can trigger this bug.
>>> >> >>> >>
>>> >> >>> >> On Sun, Dec 18, 2011 at 05:21, Ali Jawad <alijawad1 at gmail.com>
>>> >> >>> >> wrote:
>>> >> >>> >> > Hi
>>> >> >>> >> > Client crashed when a page displayed flash, with following
>>> error
>>> >> >>> >> >
>>> >> >>> >> > 1324214230.331051 [/assert] EMERG: void
>>> >> >>> >> > PipeProducer::produce(Buffer*):
>>> >> >>> >> > Halting: Assertion (!output_eos_) failed at
>>> >> >>> >> > ../../io/pipe/pipe_producer.cc:109 in function void
>>> >> >>> >> > PipeProducer::produce(Buffer*).
>>> >> >>> >> > Aborted
>>> >> >>> >> >
>>> >> >>> >> > Regards
>>> >> >>> >> >
>>> >> >>> >> > On Sun, Dec 18, 2011 at 3:55 PM, Ali Jawad <
>>> alijawad1 at gmail.com>
>>> >> >>> >> > wrote:
>>> >> >>> >> >>
>>> >> >>> >> >> Hi July
>>> >> >>> >> >> I was able to make the connection work, it was a stupid
>>> mistake
>>> >> >>> >> >> on
>>> >> >>> >> >> my
>>> >> >>> >> >> side, the errors are less and performance is slightly
>>> better but
>>> >> >>> >> >> still
>>> >> >>> >> >> slow
>>> >> >>> >> >> I am getting these errors on client side now
>>> >> >>> >> >>
>>> >> >>> >> >> 1324212755.168570 [/wanproxy/proxy/proxy0/connector] ERR:
>>> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >> 1324212756.652634 [/wanproxy/proxy/proxy0/connector] ERR:
>>> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >> 1324212776.041883 [/wanproxy/proxy/proxy0/connector] ERR:
>>> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >> 1324212777.468335 [/wanproxy/proxy/proxy0/connector] ERR:
>>> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >>
>>> >> >>> >> >> On server side I am getting
>>> >> >>> >> >>
>>> >> >>> >> >> 1324184191.330804 [/wanproxy/proxy/proxy-socks0/connector]
>>> ERR:
>>> >> >>> >> >> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >> 1324184194.297132 [/wanproxy/proxy/proxy-socks0/connector]
>>> ERR:
>>> >> >>> >> >> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >> 1324184202.948238 [/wanproxy/proxy/proxy-socks0/connector]
>>> ERR:
>>> >> >>> >> >> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >> 1324184202.951848 [/wanproxy/proxy/proxy-socks0/connector]
>>> ERR:
>>> >> >>> >> >> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >> 1324184217.752559 [/wanproxy/proxy/proxy-socks0/connector]
>>> ERR:
>>> >> >>> >> >> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >> 1324184217.755806 [/wanproxy/proxy/proxy-socks0/connector]
>>> ERR:
>>> >> >>> >> >> void
>>> >> >>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:
>>> >> >>> >> >> <Error>/104
>>> >> >>> >> >> [Connection reset by peer]
>>> >> >>> >> >>
>>> >> >>> >> >>
>>> >> >>> >> >>
>>> >> >>> >> >> Regards
>>> >> >>> >> >>
>>> >> >>> >> >> On Sun, Dec 18, 2011 at 3:06 AM, Juli Mallett
>>> >> >>> >> >> <juli at clockworksquid.com>
>>> >> >>> >> >> wrote:
>>> >> >>> >> >>>
>>> >> >>> >> >>> Very strange.  Can you send the client and server
>>> >> >>> >> >>> configurations?
>>> >> >>> >> >>>  I'm
>>> >> >>> >> >>> guessing that connect is failing because the ports are
>>> >> >>> >> >>> mismatched
>>> >> >>> >> >>> or
>>> >> >>> >> >>> similar, but I can't be sure.  It would also be helpful if
>>> you
>>> >> >>> >> >>> could
>>> >> >>> >> >>> telnet from the client to the port the server is supposed
>>> to be
>>> >> >>> >> >>> listening on, to verify that there are no firewalling
>>> issues
>>> >> >>> >> >>> involved.
>>> >> >>> >> >>>
>>> >> >>> >> >>> On Sat, Dec 17, 2011 at 15:21, Ali Jawad <
>>> alijawad1 at gmail.com>
>>> >> >>> >> >>> wrote:
>>> >> >>> >> >>> > Hi Juli
>>> >> >>> >> >>> > Did checkout to version 895 on both machines and did the
>>> >> >>> >> >>> > following
>>> >> >>> >> >>> > on
>>> >> >>> >> >>> > both
>>> >> >>> >> >>> > machines as well , make clean in programs/wanproxy, make,
>>> >> >>> >> >>> > copy
>>> >> >>> >> >>> > wanproxy
>>> >> >>> >> >>> > file
>>> >> >>> >> >>> > to /usr/sbin/ then launch
>>> >> >>> >> >>> >
>>> >> >>> >> >>> > /usr/sbin/wanproxy -c /etc/wanproxy.conf
>>> >> >>> >> >>> >
>>> >> >>> >> >>> > On the client I get
>>> >> >>> >> >>> >
>>> >> >>> >> >>> > 1324163928.337113 [/wanproxy/proxy/proxy0/listener] INFO:
>>> >> >>> >> >>> > Listening
>>> >> >>> >> >>> > on:
>>> >> >>> >> >>> > [0.0.0.0]:3300
>>> >> >>> >> >>> > 1324163928.337732 [/event/thread] INFO: Starting event
>>> >> >>> >> >>> > thread.
>>> >> >>> >> >>> > 1324163930.640914 [/wanproxy/proxy/proxy0/connector]
>>> INFO:
>>> >> >>> >> >>> > Connect
>>> >> >>> >> >>> > failed:
>>> >> >>> >> >>> > <Error>/0 [Success]
>>> >> >>> >> >>> > 1324163931.393061 [/wanproxy/proxy/proxy0/connector]
>>> INFO:
>>> >> >>> >> >>> > Connect
>>> >> >>> >> >>> > failed:
>>> >> >>> >> >>> > <Error>/0 [Success]
>>> >> >>> >> >>> > 1324163932.144333 [/wanproxy/proxy/proxy0/connector]
>>> INFO:
>>> >> >>> >> >>> > Connect
>>> >> >>> >> >>> > failed:
>>> >> >>> >> >>> > <Error>/0 [Success]
>>> >> >>> >> >>> > 1324163932.919439 [/wanproxy/proxy/proxy0/connector]
>>> INFO:
>>> >> >>> >> >>> > Connect
>>> >> >>> >> >>> > failed:
>>> >> >>> >> >>> > <Error>/0 [Success]
>>> >> >>> >> >>> > 1324163933.906755 [/wanproxy/proxy/proxy0/connector]
>>> INFO:
>>> >> >>> >> >>> > Connect
>>> >> >>> >> >>> > failed:
>>> >> >>> >> >>> > <Error>/0 [Success]
>>> >> >>> >> >>> > 1324163934.677630 [/wanproxy/proxy/proxy0/connector]
>>> INFO:
>>> >> >>> >> >>> > Connect
>>> >> >>> >> >>> > failed:
>>> >> >>> >> >>> > <Error>/0 [Success]
>>> >> >>> >> >>> > 1324163935.459671 [/wanproxy/proxy/proxy0/connector]
>>> INFO:
>>> >> >>> >> >>> > Connect
>>> >> >>> >> >>> > failed:
>>> >> >>> >> >>> > <Error>/0 [Success]
>>> >> >>> >> >>> >
>>> >> >>> >> >>> >
>>> >> >>> >> >>> > And the browser is not working when setting socks to use
>>> >> >>> >> >>> > wanproxy
>>> >> >>> >> >>> > client.
>>> >> >>> >> >>> > Anything I missed here ?
>>> >> >>> >> >>> >
>>> >> >>> >> >>> > Thanks
>>> >> >>> >> >>> >
>>> >> >>> >> >>> > On Sun, Dec 18, 2011 at 2:02 AM, Ali Jawad
>>> >> >>> >> >>> > <alijawad1 at gmail.com>
>>> >> >>> >> >>> > wrote:
>>> >> >>> >> >>> >>
>>> >> >>> >> >>> >> Hi
>>> >> >>> >> >>> >> The problem happened on the latest trunk that I donwload
>>> >> >>> >> >>> >> just
>>> >> >>> >> >>> >> after
>>> >> >>> >> >>> >> your
>>> >> >>> >> >>> >> latest email, I will checkout trunk, clean and make and
>>> send
>>> >> >>> >> >>> >> output.
>>> >> >>> >> >>> >> Thank agains
>>> >> >>> >> >>> >> Regards
>>> >> >>> >> >>> >>
>>> >> >>> >> >>> >>
>>> >> >>> >> >>> >> On Sun, Dec 18, 2011 at 12:27 AM, Juli Mallett
>>> >> >>> >> >>> >> <juli at clockworksquid.com>
>>> >> >>> >> >>> >> wrote:
>>> >> >>> >> >>> >>>
>>> >> >>> >> >>> >>> First, update to latest trunk since I fixed the issues
>>> >> >>> >> >>> >>> you've
>>> >> >>> >> >>> >>> reported so
>>> >> >>> >> >>> >>> far.
>>> >> >>> >> >>> >>>
>>> >> >>> >> >>> >>> Then could you go to programs/wanproxy on the client,
>>> "make
>>> >> >>> >> >>> >>> clean",
>>> >> >>> >> >>> >>> and then send all of the output of "make" to the list?
>>> >> >>> >> >>> >>>
>>> >> >>> >> >>> >>> Thanks!
>>> >> >>> >> >>> >>> Juli.
>>> >> >>> >> >>> >>>
>>> >> >>> >> >>> >>> On Sat, Dec 17, 2011 at 13:23, Ali Jawad
>>> >> >>> >> >>> >>> <alijawad1 at gmail.com>
>>> >> >>> >> >>> >>> wrote:
>>> >> >>> >> >>> >>> > Hi Juli
>>> >> >>> >> >>> >>> > Thanks for the continous help, I have one on the
>>> latest
>>> >> >>> >> >>> >>> > trunk,
>>> >> >>> >> >>> >>> > but
>>> >> >>> >> >>> >>> > the
>>> >> >>> >> >>> >>> > client I get errors while compiling the trunk on, the
>>> >> >>> >> >>> >>> > problem is
>>> >> >>> >> >>> >>> > related to
>>> >> >>> >> >>> >>> > this it seems  "result of make in programs/wanproxy/"
>>> >> >>> >> >>> >>> >
>>> >> >>> >> >>> >>> >>> cc1plus: warnings being treated as errors
>>> >> >>> >> >>> >>> >>> ../../io/socket/simple_server.h: In instantiation
>>> of
>>> >> >>> >> >>> >>> >>> ‘SimpleServer<TCPServer>’:
>>> >> >>> >> >>> >>> >>> proxy_listener.h:10:   instantiated from here
>>> >> >>> >> >>> >>> >>> ../../io/socket/simple_server.h:12: warning: ‘class
>>> >> >>> >> >>> >>> >>> SimpleServer<TCPServer>’ has virtual functions but
>>> >> >>> >> >>> >>> >>> non-virtual
>>> >> >>> >> >>> >>> >>> destructor
>>> >> >>> >> >>> >>> >>> proxy_listener.h:10: warning: ‘class
>>> ProxyListener’ has
>>> >> >>> >> >>> >>> >>> virtual
>>> >> >>> >> >>> >>> >>> functions
>>> >> >>> >> >>> >>> >>> but non-virtual destructor
>>> >> >>> >> >>> >>> >>> make: *** [proxy_listener.o] Error 1
>>> >> >>> >> >>> >>> >
>>> >> >>> >> >>> >>> > On Sun, Dec 18, 2011 at 12:12 AM, Juli Mallett
>>> >> >>> >> >>> >>> > <juli at clockworksquid.com>
>>> >> >>> >> >>> >>> > wrote:
>>> >> >>> >> >>> >>> >>
>>> >> >>> >> >>> >>> >> Hi Ali,
>>> >> >>> >> >>> >>> >>
>>> >> >>> >> >>> >>> >> Thanks for pointing out the problems with
>>> >> >>> >> >>> >>> >> -Wnon-virtual-dtor —
>>> >> >>> >> >>> >>> >> I
>>> >> >>> >> >>> >>> >> fixed
>>> >> >>> >> >>> >>> >> those just now.
>>> >> >>> >> >>> >>> >>
>>> >> >>> >> >>> >>> >> You need to have the client and server running the
>>> same
>>> >> >>> >> >>> >>> >> version.
>>> >> >>> >> >>> >>> >>  The
>>> >> >>> >> >>> >>> >> protocol has changed considerable from 0.7.2 to
>>> today,
>>> >> >>> >> >>> >>> >> and
>>> >> >>> >> >>> >>> >> you
>>> >> >>> >> >>> >>> >> should
>>> >> >>> >> >>> >>> >> not mix the two.
>>> >> >>> >> >>> >>> >>
>>> >> >>> >> >>> >>> >> That said, I think you may have some other problem
>>> with
>>> >> >>> >> >>> >>> >> the
>>> >> >>> >> >>> >>> >> errors
>>> >> >>> >> >>> >>> >> you're seeing; I don't think the mix of versions
>>> would
>>> >> >>> >> >>> >>> >> explain
>>> >> >>> >> >>> >>> >> it.
>>> >> >>> >> >>> >>> >> Still, if you would update both to trunk and report
>>> any
>>> >> >>> >> >>> >>> >> issues
>>> >> >>> >> >>> >>> >> you
>>> >> >>> >> >>> >>> >> encounter back, I'll try to fix them as soon as
>>> >> >>> >> >>> >>> >> possible.
>>> >> >>> >> >>> >>> >>  If
>>> >> >>> >> >>> >>> >> you
>>> >> >>> >> >>> >>> >> continue to experience issues, I'll set up a CentOS
>>> VM
>>> >> >>> >> >>> >>> >> to
>>> >> >>> >> >>> >>> >> test
>>> >> >>> >> >>> >>> >> everything myself before asking you to do so again.
>>> >> >>> >> >>> >>> >>
>>> >> >>> >> >>> >>> >> Sorry about the continued difficulty.  I usually try
>>> >> >>> >> >>> >>> >> very
>>> >> >>> >> >>> >>> >> hard
>>> >> >>> >> >>> >>> >> to
>>> >> >>> >> >>> >>> >> make
>>> >> >>> >> >>> >>> >> sure users have a seamless experience of building
>>> and
>>> >> >>> >> >>> >>> >> using
>>> >> >>> >> >>> >>> >> WANProxy.
>>> >> >>> >> >>> >>> >> Once this is all resolved, I'll put out a release
>>> >> >>> >> >>> >>> >> tarball,
>>> >> >>> >> >>> >>> >> too.
>>> >> >>> >> >>> >>> >>
>>> >> >>> >> >>> >>> >> Thanks,
>>> >> >>> >> >>> >>> >> Juli.
>>> >> >>> >> >>> >>> >>
>>> >> >>> >> >>> >>> >> On Sat, Dec 17, 2011 at 05:44, Ali Jawad
>>> >> >>> >> >>> >>> >> <alijawad1 at gmail.com>
>>> >> >>> >> >>> >>> >> wrote:
>>> >> >>> >> >>> >>> >> > Right now using latest trunk for server, and
>>> latest
>>> >> >>> >> >>> >>> >> > tgz
>>> >> >>> >> >>> >>> >> > for
>>> >> >>> >> >>> >>> >> > client
>>> >> >>> >> >>> >>> >> >  I am
>>> >> >>> >> >>> >>> >> > getting this error
>>> >> >>> >> >>> >>> >> >
>>> >> >>> >> >>> >>> >> > [root at CentOS54 programs]# /usr/sbin/wanproxy -c
>>> >> >>> >> >>> >>> >> >  /etc/wanproxy.conf
>>> >> >>> >> >>> >>> >> > 1324129297.168662 [/wanproxy] INFO: WANProxy 0.7.2
>>> >> >>> >> >>> >>> >> > 1324129297.169621 [/wanproxy] INFO: Copyright (c)
>>> >> >>> >> >>> >>> >> > 2008-2011
>>> >> >>> >> >>> >>> >> > WANProxy.org.
>>> >> >>> >> >>> >>> >> > 1324129297.170510 [/wanproxy] INFO: All rights
>>> >> >>> >> >>> >>> >> > reserved.
>>> >> >>> >> >>> >>> >> > 1324129297.171419 [/wanproxy/config] INFO:
>>> Configuring
>>> >> >>> >> >>> >>> >> > WANProxy.
>>> >> >>> >> >>> >>> >> > 1324129297.173140 [/io/system] INFO: Starting IO
>>> >> >>> >> >>> >>> >> > system.
>>> >> >>> >> >>> >>> >> > 1324129297.173861 [/event/thread] INFO: Starting
>>> event
>>> >> >>> >> >>> >>> >> > thread.
>>> >> >>> >> >>> >>> >> > 1324129319.092574
>>> [/wanproxy/proxy/proxy0/connector]
>>> >> >>> >> >>> >>> >> > INFO:
>>> >> >>> >> >>> >>> >> > Connect
>>> >> >>> >> >>> >>> >> > failed:
>>> >> >>> >> >>> >>> >> > <Error>/0 [Success]
>>> >> >>> >> >>> >>> >> > 1324129319.895308
>>> [/wanproxy/proxy/proxy0/connector]
>>> >> >>> >> >>> >>> >> > INFO:
>>> >> >>> >> >>> >>> >> > Connect
>>> >> >>> >> >>> >>> >> > failed:
>>> >> >>> >> >>> >>> >> > <Error>/0 [Success]
>>> >> >>> >> >>> >>> >> > 1324129320.699028
>>> [/wanproxy/proxy/proxy0/connector]
>>> >> >>> >> >>> >>> >> > INFO:
>>> >> >>> >> >>> >>> >> > Connect
>>> >> >>> >> >>> >>> >> > failed:
>>> >> >>> >> >>> >>> >> > <Error>/0 [Success]
>>> >> >>> >> >>> >>> >> > 1324129321.499178
>>> [/wanproxy/proxy/proxy0/connector]
>>> >> >>> >> >>> >>> >> > INFO:
>>> >> >>> >> >>> >>> >> > Connect
>>> >> >>> >> >>> >>> >> > failed:
>>> >> >>> >> >>> >>> >> > <Error>/0 [Success]
>>> >> >>> >> >>> >>> >> >
>>> >> >>> >> >>> >>> >> >
>>> >> >>> >> >>> >>> >> > On Sat, Dec 17, 2011 at 4:33 PM, Ali Jawad
>>> >> >>> >> >>> >>> >> > <alijawad1 at gmail.com>
>>> >> >>> >> >>> >>> >> > wrote:
>>> >> >>> >> >>> >>> >> >>
>>> >> >>> >> >>> >>> >> >> If I go to the programs/wanproxy and just make
>>> there
>>> >> >>> >> >>> >>> >> >> I
>>> >> >>> >> >>> >>> >> >> get
>>> >> >>> >> >>> >>> >> >>
>>> >> >>> >> >>> >>> >> >> cc1plus: warnings being treated as errors
>>> >> >>> >> >>> >>> >> >> ../../io/socket/simple_server.h: In
>>> instantiation of
>>> >> >>> >> >>> >>> >> >> ‘SimpleServer<TCPServer>’:
>>> >> >>> >> >>> >>> >> >> proxy_listener.h:10:   instantiated from here
>>> >> >>> >> >>> >>> >> >> ../../io/socket/simple_server.h:12: warning:
>>> ‘class
>>> >> >>> >> >>> >>> >> >> SimpleServer<TCPServer>’ has virtual functions
>>> but
>>> >> >>> >> >>> >>> >> >> non-virtual
>>> >> >>> >> >>> >>> >> >> destructor
>>> >> >>> >> >>> >>> >> >> proxy_listener.h:10: warning: ‘class
>>> ProxyListener’
>>> >> >>> >> >>> >>> >> >> has
>>> >> >>> >> >>> >>> >> >> virtual
>>> >> >>> >> >>> >>> >> >> functions
>>> >> >>> >> >>> >>> >> >> but non-virtual destructor
>>> >> >>> >> >>> >>> >> >> make: *** [proxy_listener.o] Error 1
>>> >> >>> >> >>> >>> >> >>
>>> >> >>> >> >>> >>> >> >>
>>> >> >>> >> >>> >>> >> >> On Fri, Dec 16, 2011 at 3:21 PM, Juli Mallett
>>> >> >>> >> >>> >>> >> >> <juli at clockworksquid.com>
>>> >> >>> >> >>> >>> >> >> wrote:
>>> >> >>> >> >>> >>> >> >>>
>>> >> >>> >> >>> >>> >> >>> Hi Ali,
>>> >> >>> >> >>> >>> >> >>>
>>> >> >>> >> >>> >>> >> >>> The problems you encountered should be fixed in
>>> >> >>> >> >>> >>> >> >>> Subversion.
>>> >> >>> >> >>> >>> >> >>>  Can
>>> >> >>> >> >>> >>> >> >>> you
>>> >> >>> >> >>> >>> >> >>> please provide the errors you encountered?  Most
>>> >> >>> >> >>> >>> >> >>> commonly,
>>> >> >>> >> >>> >>> >> >>> the
>>> >> >>> >> >>> >>> >> >>> problem
>>> >> >>> >> >>> >>> >> >>> is missing libuuid-dev or similar package, at
>>> least
>>> >> >>> >> >>> >>> >> >>> on
>>> >> >>> >> >>> >>> >> >>> Linux
>>> >> >>> >> >>> >>> >> >>> systems.
>>> >> >>> >> >>> >>> >> >>>
>>> >> >>> >> >>> >>> >> >>> Thanks!
>>> >> >>> >> >>> >>> >> >>> Juli.
>>> >> >>> >> >>> >>> >> >>>
>>> >> >>> >> >>> >>> >> >>> On Wed, Dec 14, 2011 at 06:56, Ali Jawad
>>> >> >>> >> >>> >>> >> >>> <alijawad1 at gmail.com>
>>> >> >>> >> >>> >>> >> >>> wrote:
>>> >> >>> >> >>> >>> >> >>> > Hi
>>> >> >>> >> >>> >>> >> >>> > I tried to install latest src code but did
>>> only
>>> >> >>> >> >>> >>> >> >>> > run
>>> >> >>> >> >>> >>> >> >>> > in to
>>> >> >>> >> >>> >>> >> >>> > problems
>>> >> >>> >> >>> >>> >> >>> > during compiling, but 0.7.2 did not face any
>>> >> >>> >> >>> >>> >> >>> > issues,
>>> >> >>> >> >>> >>> >> >>> > did
>>> >> >>> >> >>> >>> >> >>> > you
>>> >> >>> >> >>> >>> >> >>> > face
>>> >> >>> >> >>> >>> >> >>> > problems with websites opening during that
>>> error ?
>>> >> >>> >> >>> >>> >> >>> > Regards
>>> >> >>> >> >>> >>> >> >>> >
>>> >> >>> >> >>> >>> >> >>> > On Wed, Dec 14, 2011 at 3:39 PM, Diego
>>> Woitasen
>>> >> >>> >> >>> >>> >> >>> > <diego at woitasen.com.ar>
>>> >> >>> >> >>> >>> >> >>> > wrote:
>>> >> >>> >> >>> >>> >> >>> >> On Tue, Dec 13, 2011 at 6:17 PM, Juli Mallett
>>> >> >>> >> >>> >>> >> >>> >> <juli at clockworksquid.com> wrote:
>>> >> >>> >> >>> >>> >> >>> >>> Hi Ali,
>>> >> >>> >> >>> >>> >> >>> >>>
>>> >> >>> >> >>> >>> >> >>> >>> On Tue, Dec 13, 2011 at 13:08, Ali Jawad
>>> >> >>> >> >>> >>> >> >>> >>> <alijawad1 at gmail.com>
>>> >> >>> >> >>> >>> >> >>> >>> wrote:
>>> >> >>> >> >>> >>> >> >>> >>>> and on the client I am getting
>>> >> >>> >> >>> >>> >> >>> >>>>
>>> >> >>> >> >>> >>> >> >>> >>>> 1323524646.018556
>>> >> >>> >> >>> >>> >> >>> >>>> [/wanproxy/proxy/proxy0/connector]
>>> >> >>> >> >>> >>> >> >>> >>>> ERR:
>>> >> >>> >> >>> >>> >> >>> >>>> void
>>> >> >>> >> >>> >>> >> >>> >>>> ProxyConnector::splice_complete(Event):
>>> >> >>> >> >>> >>> >> >>> >>>> Unexpected
>>> >> >>> >> >>> >>> >> >>> >>>> event:
>>> >> >>> >> >>> >>> >> >>> >>>> <Error>/32
>>> >> >>> >> >>> >>> >> >>> >>>> [Broken pipe]
>>> >> >>> >> >>> >>> >> >>> >>>> 1323524690.407944 [/assert] EMERG: void
>>> >> >>> >> >>> >>> >> >>> >>>> PipeProducer::produce(Buffer*): Halting:
>>> >> >>> >> >>> >>> >> >>> >>>> Assertion
>>> >> >>> >> >>> >>> >> >>> >>>> (!output_eos_)
>>> >> >>> >> >>> >>> >> >>> >>>> failed at
>>> ../../io/pipe/pipe_producer.cc:109 in
>>> >> >>> >> >>> >>> >> >>> >>>> function
>>> >> >>> >> >>> >>> >> >>> >>>> void
>>> >> >>> >> >>> >>> >> >>> >>>> PipeProducer::produce(Buffer*).
>>> >> >>> >> >>> >>> >> >>> >>>> Aborted
>>> >> >>> >> >>> >>> >> >>> >>>
>>> >> >>> >> >>> >>> >> >>> >>> Thanks.  Several other users have reported
>>> this,
>>> >> >>> >> >>> >>> >> >>> >>> but I
>>> >> >>> >> >>> >>> >> >>> >>> have
>>> >> >>> >> >>> >>> >> >>> >>> not
>>> >> >>> >> >>> >>> >> >>> >>> been
>>> >> >>> >> >>> >>> >> >>> >>> able to reproduce it.  I will redouble my
>>> >> >>> >> >>> >>> >> >>> >>> efforts
>>> >> >>> >> >>> >>> >> >>> >>> to
>>> >> >>> >> >>> >>> >> >>> >>> reproduce.
>>> >> >>> >> >>> >>> >> >>> >>>
>>> >> >>> >> >>> >>> >> >>> >>>> On Tue, Dec 13, 2011 at 3:06 AM, Ali Jawad
>>> >> >>> >> >>> >>> >> >>> >>>> <alijawad1 at gmail.com>
>>> >> >>> >> >>> >>> >> >>> >>>> wrote:
>>> >> >>> >> >>> >>> >> >>> >>>>> Hi
>>> >> >>> >> >>> >>> >> >>> >>>>> Browsers are FF 4.x and 3.x on Windows and
>>> >> >>> >> >>> >>> >> >>> >>>>> Linux,
>>> >> >>> >> >>> >>> >> >>> >>>>> I
>>> >> >>> >> >>> >>> >> >>> >>>>> also
>>> >> >>> >> >>> >>> >> >>> >>>>> tried
>>> >> >>> >> >>> >>> >> >>> >>>>> IE8,
>>> >> >>> >> >>> >>> >> >>> >>>>> the config is the same one given in the
>>> >> >>> >> >>> >>> >> >>> >>>>> examples,
>>> >> >>> >> >>> >>> >> >>> >>>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>> OS
>>> >> >>> >> >>> >>> >> >>> >>>>> is
>>> >> >>> >> >>> >>> >> >>> >>>>> CentOS
>>> >> >>> >> >>> >>> >> >>> >>>>> 5.6
>>> >> >>> >> >>> >>> >> >>> >>>>> 64bit.
>>> >> >>> >> >>> >>> >> >>> >>>>> Regards
>>> >> >>> >> >>> >>> >> >>> >>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>> On Mon, Dec 12, 2011 at 12:48 AM, Juli
>>> Mallett
>>> >> >>> >> >>> >>> >> >>> >>>>> <juli at clockworksquid.com> wrote:
>>> >> >>> >> >>> >>> >> >>> >>>>>> Thanks for the feedback.  I don't think I
>>> >> >>> >> >>> >>> >> >>> >>>>>> will
>>> >> >>> >> >>> >>> >> >>> >>>>>> need
>>> >> >>> >> >>> >>> >> >>> >>>>>> access,
>>> >> >>> >> >>> >>> >> >>> >>>>>> but
>>> >> >>> >> >>> >>> >> >>> >>>>>> I
>>> >> >>> >> >>> >>> >> >>> >>>>>> may
>>> >> >>> >> >>> >>> >> >>> >>>>>> need more configuration information to
>>> >> >>> >> >>> >>> >> >>> >>>>>> reproduce.
>>> >> >>> >> >>> >>> >> >>> >>>>>>  What
>>> >> >>> >> >>> >>> >> >>> >>>>>> OS
>>> >> >>> >> >>> >>> >> >>> >>>>>> is
>>> >> >>> >> >>> >>> >> >>> >>>>>> WANProxy
>>> >> >>> >> >>> >>> >> >>> >>>>>> running on?  Can you send your
>>> configuration?
>>> >> >>> >> >>> >>> >> >>> >>>>>>  What
>>> >> >>> >> >>> >>> >> >>> >>>>>> browser
>>> >> >>> >> >>> >>> >> >>> >>>>>> is
>>> >> >>> >> >>> >>> >> >>> >>>>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>>> client?
>>> >> >>> >> >>> >>> >> >>> >>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>> Thanks!
>>> >> >>> >> >>> >>> >> >>> >>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>> On Sun, Dec 11, 2011 at 13:44, Ali Jawad
>>> >> >>> >> >>> >>> >> >>> >>>>>> <alijawad1 at gmail.com>
>>> >> >>> >> >>> >>> >> >>> >>>>>> wrote:
>>> >> >>> >> >>> >>> >> >>> >>>>>>> Hi
>>> >> >>> >> >>> >>> >> >>> >>>>>>> Thanks for the help so far, I might be
>>> able
>>> >> >>> >> >>> >>> >> >>> >>>>>>> to
>>> >> >>> >> >>> >>> >> >>> >>>>>>> give
>>> >> >>> >> >>> >>> >> >>> >>>>>>> you
>>> >> >>> >> >>> >>> >> >>> >>>>>>> access
>>> >> >>> >> >>> >>> >> >>> >>>>>>> to
>>> >> >>> >> >>> >>> >> >>> >>>>>>> check it out if needed, as for now no
>>> IPV6,
>>> >> >>> >> >>> >>> >> >>> >>>>>>> sites
>>> >> >>> >> >>> >>> >> >>> >>>>>>> like
>>> >> >>> >> >>> >>> >> >>> >>>>>>> cnn
>>> >> >>> >> >>> >>> >> >>> >>>>>>> youtube etc
>>> >> >>> >> >>> >>> >> >>> >>>>>>> Regards
>>> >> >>> >> >>> >>> >> >>> >>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>> On Mon, Dec 12, 2011 at 12:34 AM, Juli
>>> >> >>> >> >>> >>> >> >>> >>>>>>> Mallett
>>> >> >>> >> >>> >>> >> >>> >>>>>>> <juli at clockworksquid.com> wrote:
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> This seems very strange.  Which sites?
>>>  Do
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> you
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> have
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> IPv6
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> connectivity?
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>  If you don't have IPv6 connectivity, I
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> wonder
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> if
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> that
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> might
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> be
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> problem, and we might need some way to
>>> tell
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> WANProxy
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> to
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> use
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> IPv4
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> only.
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>  If you have specific examples that
>>> likely
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> will
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> make
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> it
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> easier
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> for me
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> to reproduce and fix.
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> Thanks & sorry to hear about your
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> difficulty,
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> Juli.
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> On Sun, Dec 11, 2011 at 12:04, Ali
>>> Jawad
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> <alijawad1 at gmail.com>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>> wrote:
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> Hi
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> I completed the setup, but some sites
>>> open
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> and
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> some
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> not,
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> some
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> sites
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> need to be reloaded a few times for
>>> it to
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> work,
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> I.e.
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> CSS
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> does
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> not load
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> etc.
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> Any ideas ?
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> Regards
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> On Mon, Dec 5, 2011 at 12:27 AM, Juli
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> Mallett
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>> <juli at clockworksquid.com> wrote:
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> Hi Ali,
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> If you already have the SOCKS example
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> configured,
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> then
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> you
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> should be
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> able to use your browser or operating
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> system's
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> proxy
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> configuration to
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> tell it to use SOCKS for HTTP or FTP
>>> or
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> whatever
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> protocols
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> you
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> need.
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> If you have trouble finding this and
>>> tell
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> us
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> what
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> OS
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> and
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> browser or
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> other software you're using I'm sure
>>> one
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> of
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> us
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> can
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> help
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> you
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> get the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> information you need!
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> Thanks,
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> Juli.
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> On Sun, Dec 4, 2011 at 03:26, Ali
>>> Jawad
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> <alijawad1 at gmail.com>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>> wrote:
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> Hi
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> I did setup wanproxy in
>>> client/server
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> mode
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> as
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> per
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> Proxying over a
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> WAN using SOCKS example in
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> http://wanproxy.org/examples.shtml
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> . Here
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> is the issue
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> I do have a server in Asia which is
>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> client
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> and
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> a
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> server
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> in the USA
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> which is the wanproxy server, I want
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> traffic
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> for
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> browsing
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> to
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> pass
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> through the wanproxy link and from
>>> there
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> on
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> fetch
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> sites I
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> need in
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> the states and send them back after
>>> that
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> through
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> WAN
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> link
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> to the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> client server which sends them to
>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> browser
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> of
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> client
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> in my LAN.
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> Is this something WAN proxy does ?
>>> Do I
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> need to
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> do
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> additional
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> stuff ?
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> Such as setting up SQUID on wanproxy
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> server
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> or
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> client
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> server
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> ? Is any
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> ip forwarding needed ? What
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> configuration
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> should I
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> use
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> on
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> browsers
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> ?
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> I am sorry for the long list of
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> questions,
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> but
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> I
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> am
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> sure
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> it
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> will come
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> in handy for people who research the
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> topic
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> online
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> "once
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> answered that
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> is :)"
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> Thanks !
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> _______________________________________________
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> wanproxy mailing list
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>> wanproxy at lists.wanproxy.org
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> >> >>> >> >>> >>> >> >>> >>>>>>>>>>>
>>> http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org
>>> >> >>> >> >>> >>> >> >>> >>>
>>> _______________________________________________
>>> >> >>> >> >>> >>> >> >>> >>> wanproxy mailing list
>>> >> >>> >> >>> >>> >> >>> >>> wanproxy at lists.wanproxy.org
>>> >> >>> >> >>> >>> >> >>> >>>
>>> >> >>> >> >>> >>> >> >>> >>>
>>> >> >>> >> >>> >>> >> >>> >>>
>>> >> >>> >> >>> >>> >> >>> >>>
>>> >> >>> >> >>> >>> >> >>> >>>
>>> http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org
>>> >> >>> >> >>> >>> >> >>> >>
>>> >> >>> >> >>> >>> >> >>> >> Hi,
>>> >> >>> >> >>> >>> >> >>> >>  I had that error with the 0.7.2 release. I'm
>>> >> >>> >> >>> >>> >> >>> >> using
>>> >> >>> >> >>> >>> >> >>> >> the
>>> >> >>> >> >>> >>> >> >>> >> latest
>>> >> >>> >> >>> >>> >> >>> >> code
>>> >> >>> >> >>> >>> >> >>> >> from subversion and I haven't seen the error
>>> >> >>> >> >>> >>> >> >>> >> again.
>>> >> >>> >> >>> >>> >> >>> >>
>>> >> >>> >> >>> >>> >> >>> >> Regards,
>>> >> >>> >> >>> >>> >> >>> >>  Diego
>>> >> >>> >> >>> >>> >> >>> >>
>>> >> >>> >> >>> >>> >> >>> >> --
>>> >> >>> >> >>> >>> >> >>> >> Diego Woitasen
>>> >> >>> >> >>> >>> >> >>
>>> >> >>> >> >>> >>> >> >>
>>> >> >>> >> >>> >>> >> >
>>> >> >>> >> >>> >>> >
>>> >> >>> >> >>> >>> >
>>> >> >>> >> >>> >>
>>> >> >>> >> >>> >>
>>> >> >>> >> >>> >
>>> >> >>> >> >>
>>> >> >>> >> >>
>>> >> >>> >> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>
>>> >> >>
>>> >> >
>>> >
>>> >
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wanproxy.org/pipermail/wanproxy-wanproxy.org/attachments/20111223/65057e26/attachment-0005.htm>