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

[gstmoderator <gst...@ho...>]

----- Original Message -----
From: "wayne" <wa...@ny...>
To: <noc...@fr...>; <pro...@sf...>
Sent: Monday, March 31, 2003 2:53 PM
Subject: [noCensorship] Re: DONE--Re: Re: LP


> > From: "gstmoderator" <gst...@ho...>
> > To: <noc...@fr...>, <pro...@sf...>
> > Subject: [noCensorship] DONE--Re: Re: LP
> >
> > wayne-
> >
> > thanks for your help. running JAP I was having same problem. Turns out
now
> > I'm on a LAN and locations to set my proxy were different. No problem.
> >
> > thanks again.
>
> I'm commenting below anyway.
> You (and others) might find it useful yet.
>
> Here's the overall summary of my comments below.
> You chose proxies which all failed on every test, for LP to
> 'test/merge'. As a result, it (correctly) didn't merge anything,
> and you didn't see them in the reloaded configuration.
>
> You would have been better off just letting LP do it's job.
> It has a database of thousands of proxies to choose from, and
> would have chosen ones which worked there.
> There is a common feeling that the user needs to tell LP what to
> do, but the truth is that it knows better than 99% of users, and
> what it doesn't know it learns after a bit of use.
>

I didnt know LP had the proxies built in so I thought I had to add them.
thanks for clarifying.

> 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.

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

>
>
> > From: "gstmoderator" <gst...@ho...>
> > To: <noc...@fr...>, <pro...@sf...>
> > Subject: [noCensorship] Re: LP
>
> [...]
>
> > 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?
> 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.

>
> > Don't panic, I can probably work ok without them
> >
> > LocalProxy is offering services on the following ports:
> > 10076:non-censoring HTTPS proxy
> > 10077:PROPFIND capable HTTP proxy
> > 10078:HTTP zapped advertisement proxy
> > 10079:proxy autoconfiguration
> > 10080:anonymous, non-censoring HTTP proxy - standard
> > 10081:localProxy control
> > 10082:non-censoring HTTP proxy - standard
> > 10119:Usenet news - panix
> > 11119:Usenet news - mozilla
> >
> >
> > For web browser proxy service, please configure your web browser
> >   http proxy entry to localhost:10082 and the
> >   https proxy entry to localhost:10076 now
> >
> > 5. localproxy log
> >
> > This is localProxy GUI (the 'front end'), version: 4.247
> > Proxies found in environment: none
> > I'm assuming this IP address is 192.168.1.101
> > I'm assuming this IP address is 192.168.1.101
> > Setting default config syria-scs-net
> > Starting localProxy engine with configuration: saved
> > start line: perl localProxy2.pl -x 0 -g -d 0 -c saved
> > running localProxy2.exe
>
> So the back end is running *before* you test the proxies.
>
> > Checking proxy capabilities ...
> > Extracting proxy strings, safeing, expanding/skipping ports,
> > validating, resolving, deduping...
> > 1 proxies to test (after processing)
> > ctrl-c to see results so far; double-ctrl-c to abort
> > Running test: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
> > 19 Results have also been written to file statProxy.2003.3.30.22.out
> >
> > statProxy v4.143 report from 192.168.1.101(syria-scs-net):
>
> This is the 'LAN' you were talking about.
> We're all on a LAN, of some sort, but yours is a private address
> lan.  This is special - packets to addresses like yours will never
> be routed acrosss the internet. For you to be able to talk to
> *anything* on the internet outside your lan, you must use a router
> of some sort (something with an address on your lan, an address
> on the real internet and the capability of switching packets
> between the two. Remote sites will think they are communicating
> with this router.
>
> In your case, your ISP's proxies are probably handling this
> for web browsing. Other services (your JAP access, for example)
> would be being provided by a NAT.
>
> BTW, 'syria-scs-net' is localProxy's guess at your ISP/firewall.
> It's done by looking at your address, and finding the best match
> in the firewalls database. Syria-scs-net is the first one it found,
> but there are millions of such addresses (those addresses are
> not routable on the internet, so they can be reused in different
> locations). No harm done, but wrong (in general) and confusing.
> I've changed it to indicate a private address in future versions.
>
> > 141.150.149.247 :80    FFFFFFFFFFFFF FFFFFF 1.2/?
>
> These results are all bad, so when these tests are complete,
> there is nothing of interest to localProxy (or you!), and
> nothing needs to be merged to your configuration file. MergeHosts
> will simply ignore any proxies where where *every* test fails.
>
> Port 80 looks like a bad choice for you - you need to test
> proxies on other ports. 3128 and 8080 are probably also blocked.
> Try this one: 24.129.32.175:9631
> Test it quickly by using:
> statProxy -t 0 24.129.32.175:9631
> If that passes ('P'), then do the localProxy 'test/merge' and
> you should find it in the config you specify. Note that this
> is unnecessary, because LP already knows about this proxy -
> it's in the database. See the summary above.
>
> [...]
>
> > Done ... writing results to tests-userSpecd.txt
> > MergeHosts.pl v4.48
> > merging tests-userSpecd.txt to config-saved.xml
> > (saving original config-saved.xml in config-saved.old.xml)
> > Test location firewall: syria-scs-net
> > Ignoring all test results (except uptime and socks) for any
> > hosts on port 80  - known transparent proxy
>
> [...]
>
> Nothing actually happened here - no results were worth saving!
> I've added a message to this effect.
>
> > This exe file was created with the evaluation version of Perl2Exe.
> > For more information visit http://www.indigostar.com
> > (The full version does not display this message with a 2 second delay.)
> > ...
> >
> >
> >
> > 6. none of proxies are then used during internet or when I close and
restart
> > LP using saved config (no error stats)
>
> None were merged to the config. This is expected.
>
> [...]
>
> > > Let's clarify:
> > > 1) you enter proxies into the field above 'test/merge new proxies'
> > > Or you leave the entries that are already there. Use the right format:
> > > proxy.xxx.com:8000, proxy2.yyy.etc:8999
> > > etc. (say).
> >
> > yes
> >
> > > 2) you click 'test/merge new proxies'
> >
> > yes
> >
> > > 3) a window opens (or appears on the task bar?). On XP, I think
> > > it should have a title containing the command used to run it.
> > > Warning, I don't have an XP system to test on, so I can't be
> > > precise here. This might be the area where the problem lies - the
> > > window/icon may not be appearing at all. I had some XP problems here
> > > before. If that's the case, I'll need to find an XP system.
> >
> > window opens if I run Autoconfigure instead of test/merge
>
> Hmm ... they are done in different ways, so that's interesting.
> 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

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

only in autoconfigure
>
> > > 4) in that window, you should be able to watch statProxy testing your
> > > proxies. If it closes too quickly, you probably gave it a bad proxy
> > > format. If the reason is not obvious, I suggest you run statProxy
> > > by itself in a command window with the proxy format you used to see
> > > what error is reported.
> >
> > see above--no errors
> >
> > > 5) the merge of these results to a config are done back in the GUI
> > > (by calling mergeHosts).
> > >
> > > I'll wait to hear what the log window contains.
> >
> > like I said, I've run LP on XP though it was .pl not .exe.
>
> You said you ran the LP exe (see your comment a few lines down).
> No matter though, the whole 'problem' appears to be your bad
> choice of proxies to test.
> Basically, LP knew better than you :-)
> See my summary above.

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

>
> [...]
>
> > > > > 5) Which LP are you using (version number, executable or source)?
> > > >
> > > > 4.247 exe I think
> > >
> > > Damn, that makes things difficult.
> > >
> > > > > 6) You might be able to run the GUI window (localProxy.pl or .exe)
> > > > > with debug turned on - later versions only.
> > > > >
> > > > > 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
>
> [...]
>
> > thanks again
>
> --
> wa...@ny...
> http://proxytools.sourceforge.net/
> ===8>============== noCensorship community ===============
> List's webpage: http://www.freelists.org/webpage/nocensorship
> List's archive: http://www.freelists.org/archives/nocensorship
> To unsubscribe: noc...@fr... with 'unsubscribe' in
the SUBJECT field.
> Moderator's email: noc...@fr...
> ===8>============== noCensorship community ===============
>
>
>