[PROXYPER] Version 313?

DHS dx7 at earthlink.net
Sat Feb 12 16:54:57 EST 2000

Thanks Jeff,
   You have brightened half of the mystery. Yes, I did notice that this
parameter is in the [keyserver] section, but I raised the query on the
belief that something subtle might be going on. Maybe not and I need to look

   I sent no proxy console log entries, because when the clients declare a
"network error with the proxy", and the proxy is running in the "lurk" mode,
the msg syntax is displayed only on the client's live console. Nothing is
written to the client's log file. Only way I have to show this would be a
screen capture when the error happens with the proxy set to extreme
verbosity (statusperiod=</=30). My normal status period value is 600.

   Yes, I agree that if the proxy is key-depleted, the clients should act
much the same way. And, they do when I allow the proxy to go much beyond 24
hours without cycling my proxies buffers. In this case, however, the proxy
is quite full of fresh work to pass out, but simply does not communicate
when the client comes to transact business. The behavior did not seem to
make any sense. For now, only a Local selection is fully operational. But,
I'll look further.

Thanks again,

-----Original Message-----
From: Jeff Lawson <jlawson at bovine.net>
To: proxyper at lists.distributed.net <proxyper at lists.distributed.net>
Date: Saturday, February 12, 2000 16:20 PM
Subject: Re: [PROXYPER] Version 313?

>On Sat, 12 Feb 2000, DHS wrote:
>> Yes, the Version 313 PerProxy is a very good improvement. I am
>> pleased with the expanded parameter explanation in the readme.txt file.
>> Several of my concerns have been answered.
>> I do have a question. I have read several times the section explaining
>> "connectivity" of the PProxy:
>> connectivity=x    ;x=Normal, Lurk, LurkOnly
>> Is this parameter dealing with connectivity between the:
>> a)Client and PProxy?
>> b)PProxy and KeyServer (via dial-up, ISP, and web)?
>> The explanation seems to suggest b), but whenever I select "Lurk" all
>> communication between the Clients and the PProxy terminates and the
>> indicate network errors in the console log view. (no mention of network
>> error appears in the Client's log file.) All Clients are set for
>> on a "private network."
>The option affects the connectivity between your proxy and the upstream
>server.  That is why it is grouped under the [KeyServer] section, which
>indicates that it relates specifically to that.
>If your proxy does not have any blocks available for your clients when
>they connect, then that may be the cause of the errors that you are
>The connectivity mode does not affect HOW the proxy connects to the
>keyserver, only when.
>You do not indicate what messages you see in your proxy console output.
>> The "Normal" selection is the only choice that allows communication
>> the PProxy and the Clients. Three of the Clients are version 2.8005.455.
>> Client is version 2.8004.450.
>> Possibly contributing factors:
>> --Black Ice Defender runs on the same machine as the PProxy and one
>> --The Clients do not use the "behind a firewall" settings. (?)
>> --All machines have TCP/IP running, but unbound from the NIC's.
>> --NetBIOS is defeated.
>> --The NIC's are bound to NetBEUI to allow local printer and file sharing.
>> --All machines run M$ W95 OSR2.1 (no USB)
>Jeff Lawson   http://www.bovine.net/   http://www.cs.hmc.edu/~jlawson/
>Jeffrey_Lawson at alumni.hmc.edu  jlawson at bovine.net  bovine at distributed.net
>Programmer, Developer, Mascot, Founder of the largest computer on earth!
>Don't waste those cycles!  Put them to use!  http://www.distributed.net/
>To unsubscribe, send 'unsubscribe proxyper' to
majordomo at lists.distributed.net

To unsubscribe, send 'unsubscribe proxyper' to majordomo at lists.distributed.net

More information about the proxyper mailing list