[PROXYPER] Personal Proxy can't use SQUID proxy

Don Davis djtech7 at yahoo.com
Fri Jan 15 05:39:02 EST 1999


I have successfully been running personal proxy at my work (build 280).
My work uses Squid/2.0.PATCH2 on a Solaris computer for the proxy.  I
have
recently been trying the new builds (300+) in hopes to convert my
network over
to the new faster clients.  Today I tried build 303 and here is the
results:


[01/15/99 13:31:50 UTC] Server 207.217.173.181 changed from state 0 to 1
[01/15/99 13:31:50 UTC] Server 207.217.173.181 changed from state 1 to 8
[01/15/99 13:31:52 UTC] server: Establishing handshake.
[01/15/99 13:31:52 UTC] server: Got handshake acknowledment.
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7ce4bc80:e0000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 request, iter 64.
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7d957c53:00000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7c8e8ae0:40000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7c7e95ad:50000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7c30a47a:d0000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7c0e7a05:20000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7c122292:20000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7cd68559:10000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7c702671:60000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7611d57b:f0000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7dc8deb1:00000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7d94bb9a:00000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7df5d69c:60000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7da37bbb:90000000, iter 1
[01/15/99 13:31:52 UTC] server: Queueing rc564 block
7c1c9f26:90000000, iter 1
[01/15/99 13:31:52 UTC] Server 207.217.173.181 is no longer connected
(reading).
[01/15/99 13:31:52 UTC] server: Closing server connection.
[01/15/99 13:31:52 UTC] server: Successfully put back 15 unsent blocks.
[01/15/99 13:36:00 UTC] Creating outgoing server connection.
[01/15/99 13:36:00 UTC] rc564 r=0/20, d=12152/3, 0.0 Mkeys/sec, tot=0
[01/15/99 13:36:00 UTC] desII r=0/20, d=0/100, 0.0 Mkeys/sec, tot=0
[01/15/99 13:36:01 UTC] Server 207.217.173.181 changed from state 0 to 1
[01/15/99 13:36:01 UTC] Server 207.217.173.181 changed from state 1 to 8
[01/15/99 13:36:02 UTC] server: Establishing handshake.

The relevent portion of my proxyper.ini is:
[KeyServer]
ipaddress=207.217.173.181
port=2064
connectperiod=30
connectivity=normal
;bindip=                        ; IP to talk out to keyserver from
uuehttpmode=2
httpproxy=obtained from network setup... don't peek =)
httpport=80
;httpid=

I have to use the IP for the key server address otherwise it always
resolves to 255.255.255.255
and packet fails validation.  I've tried all the uuehttpmodes but this
one should be the correct
one.  I know Jeff Lawson aka bovine at distributed.net has been working
on the recent build
trying to fix problems, but was wondering if this problem is being
looked into?  I'm going
to be setting up a new network here (40+ PII350's) and would love to
be able to use the newer
faster clients.  Please help!  

p.s. As you can see I made the mistake of converting to the new proxy
for a day and have a lot
of the new proxy completed buffers to dump.  Can I mail this somewhere?

_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

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



More information about the proxyper mailing list