[proxyTools-users] Re: [noCensorship] Re: DONE--Re: Re: LP

[wayne <wa...@ny...>]

> From: "gstmoderator" <gst...@ho...>
> To: <noc...@fr...>, <pro...@sf...>
> Subject: [noCensorship] Re: DONE--Re: Re: LP
> 
> I didnt know LP had the proxies built in so I thought I had to add them.
> thanks for clarifying.

Hosts.zip is the database. It decompresses to hosts.xml.
You can read it by hand(Internet Explorer, or a text editor), 
but extracting proxies with the specifications you need is best 
done using extractHosts.pl.
I generally keep it up to date, using the proxy lists posted in 
various groups and by testing the ones selected by LP for various 
configurations and ISPs.

> > I think that answers all your original questions, but I have a
> > couple:
> > 1) I'd like to confirm that LP works when you leave it alone and
> > just try to use it for (say) web browsing without adding your own
> > proxies. Did you ever get that far? If it doesn't work (and you're
> > still interested) please post some logs from the back end window.
> > 2) I'd like to confirm whether or not that window (or task bar
> > icon) actually appears when you use 'test/merge'. I recall a problem
> > reported on XP, but I thought it was fixed a long time ago. It would
> > only affect operation of 'test/merge'. I guess I'll have to do
> > this myself on an XP system, if I can find one.

I tested it on a Windows XP Pro workstation, and it worked fine.

> the window only opens on autoconfigure. when I get the chance I'll run it
> and post log for you.

Duh, that's right. The test results are displayed in the GUI log 
window - sorry about that.

> > > 1. open lp using saved config
> > > 2. put proxies in box from hat 141.150.149.247:80, 208.49.206.97:80,
> > > 204.196.215.9:80, 64.48.186.225:80, 208.218.142.13:80       Echo= 11687
> > > 3. push test/merge
> > > 4. localproxy2 window log
> > >
> > > This is localProxy Engine (the 'back end'), version: 4.214
> > > Loading configuration saved
> > > Waiting for the front end to connect ... connected
> > > Checking all layer 0 hosts for connectivity...
> > > Couldn't connect to 33 proxies
> >
> > Why so many?

On second thoughts ...
It looked to me like there were too many per layer, but 
this overall number is probably reasonable in a difficult 
environment like yours. LP should still work, but might require 
more training.

> > What config did you use (before the 'saved' one)?
> > There's no 'saved' config, until you save one.
> 
> auto. I thought LP chose a new proxy every time Internet 'call' to LP for
> proxy address. Does LP do that, or just search for the best proxies its
> already used.

At the time the back end runs it selects 10 proxies for each layer. 
The database is searched for the best ones for each service, 
commStrat, speed, reliability etc. No dynamic tests are done at 
this time.
As soon as the build is complete all the layer 0 proxies are tested 
to see if they are alive. None are discarded, but if they appear to 
be dead, they are demoted so that LP will not choose them as often.
In use, LP will occasionally try them again, but will mostly use 
the good ones. As you use it, LP will concentrate on the good ones 
more and more. If you save the config (use 'saved', or 'last'), this 
learned info is available as soon as LP starts up the next time.

[...]

> > With autoConfigure you should have been able to find a file
> > created called master.log with the log of what happened.
> 
> will it save in xml

Not the log file. There's no point.
The saved configs are all in xml.

> > But we're talking about test/merge.
> > Did anything appear on the task bar?
> 
> only in autoconfigure

See above. That's ok, the log is in the GUI log window.

[...]

> meant previous LP installation 10 months ago was .pl but exe seem more
> stable

Errk. The pl and exe are exactly the same.
But I managed to make some improvements in that 10 months :-)

[...]

> > > > > > 7) During the above tests, there are various files created and
> saved.
> > > > > > The easy way to find them is by modification/creation date. See if
> > > > > > they contain the proxies you expected. Let us know what happened.
> > > > >
> > > > > config-saved attachd
> > > >
> > > > Did you find any files created/modified?
> >
> > You still didn't look for these?
> 
> statproxy out files

That's a start :-)
No tests-auto.txt file? 
How could you miss this one?
Do you know how to find recently created/modified files?
These files tell you exactly what happened.

--
wa...@ny...
http://proxytools.sourceforge.net/