[PROXYPER] Bug? Dupe source

David Taylor rc5 at xfiles.nildram.co.uk
Tue Mar 2 19:36:40 EST 1999


On Tue, 2 Mar 1999, Petr Novotny wrote:
> 
> Hi,

Hi

> reading through the logs of perproxy (build 304 on Linux) and client 
> (build 326 NT service) I have found the following oddity:
> 

Client connected..
Got blocks..
Updated random prefix...
Got more blocks...
Completed blocks

Now, this is the interesting part.

> 03/02/99 12:18:17,Creating outgoing server connection.
> 03/02/99 12:20:47,Error locating host us.v27.distributed.net
> 03/02/99 12:20:47,Server 0.0.0.0 changed from state 0 to 9
> 03/02/99 12:20:47,server: Closing server connection.

While the client was connected, the proxy tried to connect to a server.
Which failed, because you were offline and the DNS lookup didn't work.

The client finnishes submitting finishing blocks
Then disconnects

The client connects again (and gets ANOTHER randomprefix, sheesh)
Gets a block,
*then submits the same blocks*
Then disconnects

> 03/02/99 12:42:24,rc564 r=588/600, d=20/1, 1.3 Mkeys/sec, tot=344
> 03/02/99 12:42:24,desII r=0/20, d=0/1, 0.0 Mkeys/sec, tot=0

The proxy now have 20 blocks in its buffer, but 9 are in there twice.
Thats because the client submitted dup blocks.  The problem is shown
in the client log..
 
> 
> from the client (it's clock is one hour in advance):
> [Mar 02 13:26:23 UTC] Completed one RC5 block 88CF51F9:70000000 (1*2^28 keys)
>                       0.00:23:54.19 - [187,168.42 keys/sec]
> [Mar 02 13:26:23 UTC] Summary: 9 RC5 blocks 0.04:25:55.53 - [151.16 kkeys/s]
> [Mar 02 13:26:25 UTC] The perproxy says: "Linux alive and kicking"
> [Mar 02 13:26:25 UTC] Retrieved 10 blocks (10*2^28 keys) from server.

> [Mar 02 13:27:26 UTC] Flush::Bad packet acknowledgement.

THERE Is the problem.  The client receives a bad packet ack. That could
be because the server was at maxkeysdone, and was trying to connect to a
server, but I'm not sure. If this is the case, the proxy should
still accept blocks over maxkeysdone, otherwise its a bit stupid.


Then it does another block.
Connects to the server, and flushes the (same) blocks (plus the new one)

> 
> (From the ini settings, maxkeysdone=1 may be interesting; plus the 
> fact that the Internet connection was down till 12:43)

Those are probably the reasons, but you can't really fix it, just by
changing ini file settings..
 

-- 
David Taylor
E-Mail:	dtaylor at nildram.co.uk.spam
ICQ:	268004
[Remove .spam from e-mail to reply]

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



More information about the proxyper mailing list