[rc5] Trouble with Bovine RC5 client networking through proxy

Frederick W. Wheeler wheeler at ipl.rpi.edu
Thu Oct 2 11:31:07 EDT 1997


Hello,

I am trying to run the Bovine RC5 V2 client from behind a firewall,
but am having some trouble making network connections.  Below, I'm
listing all information that might be pertinant with the hope that
someone can point out a mistake in my setup.  I have read the
directions and FAQ several times, and experimented with many different
configurations.  I did manage to retrieve a block from a server once,
details below.

Thanks,
Fred Wheeler

**  COMPUTER TYPE AND OS

  % uname -a
  SunOS ilium 4.1.3_U1 1 sun4m

**  CLIENT DOWNLOADED FROM rc5.distributed.net

  rc5v2b4-sunos413-sparc.tar.gz

**  NETSCAPE PROXY CONFIGURATION

  I am able to Netscape to anywhere on the Internet.

  Netscape Version 3.0

  Click: Options -> Network Preferences ->Proxies -> View

    --------------------------------------------
    |   Manual Proxy Configuration             |
    |   --------------------------             |
    |   FTP Proxy:        nsproxy    Port:  80 |
    |   Gopher Proxy:     nsproxy    Port:  80 |
    |   HTTP Proxy:       nsproxy    Port:  80 |
    |   Security Proxy:   nsproxy    Port:  80 |
    |   WAIS Proxy:       nsproxy    Port:  80 |
    |   No Proxy for:                          |
    |                                          |
    |   SOCKS Host:                  Port:1080 |
    --------------------------------------------

  SOCKS Host field is blank, if I delete the "1080", it just comes
  back later.

**  PRESENT CLIENT CONFIG

  % rc5v2 -config
  
  RC5 v2.004 client - a project of distributed.net
  Copyright distributed.net 1997
  Visit http://www.distributed.net/ for more information
  
  CLIENT CONFIG MENU
  ------------------
  1)  Email to report as [default:rc5 at distributed.net] ==> wheeler at ipl.rpi.edu
  2)  Blocks to Buffer [default:5] ==> 5
  3)  Blocks to complete in run [default:0] ==> 0
  4)  Hours to complete in a run [default:0] ==> 0
  5)  Keys per timeslice - for Macs etc [default:65536] ==> 65536
  6)  Level of niceness to run at [default:0] ==> 0
  7)  File to log to [default:] ==> rc5v2.log
  8)  Network communication mode [default:1] ==> 4
  9)  Preferred KeyServer Proxy
       [default:rc5proxy.distributed.net] ==> rc5proxy.distributed.net
  11)  Local HTTP proxy address
       [default:wwwproxy.corporate.com] ==> nsproxy
  12)  Local HTTP proxy port [default:80] ==> 80
  0)  Quit and Save
  Choice --> 0

**  PRESENT CLIENT rc5v2.ini FILE

  % cat rc5v2.ini
  [parameters]
  id=wheeler at ipl.rpi.edu
  threshold=5
  count=0
  hours=0
  timeslice=65536
  niceness=0
  logname=rc5v2.log
  firemode=4
  keyproxy=rc5proxy.distributed.net
  httpproxy=nsproxy
  httpport=80

**  ERROR MESSAGES

  Here are some lines of output from rc5v2 showing the network
  error messages:
  
  | [10/02/97 08:40:27 GMT] Block: 6C1F35:70000000 being processed
  | [10/02/97 08:40:27 GMT] 0 Blocks remain in file buff-in.rc5
  | .....10%.....20%.....30%.....40%.....50%.....60%.....70%.....80%.....90%....
  | [10/02/97 09:54:51 GMT] Completed block 6C1F35:70000000 (268435456 keys)
  |                         01:14:24.49 - [60126.76 keys/sec]
  | Network::Error Read failed 23/0
  | PutBuffer Error
  | Network::Error Read failed3/0
  | Unable to fetch more blocks, generating random block.
  | Please look into correcting your network problems as soon as possible.
  | [10/02/97 09:54:53 GMT] Block: 462107:90000000 being processed
  | [10/02/97 09:54:53 GMT] 0 Blocks remain in file buff-in.rc5
  | .....10%.....20%.....30%.....40%.....50%.....60%.....70%.....80%.....90%....
  | [10/02/97 11:09:23 GMT] Completed block 462107:90000000 (268435456 keys)
  |                         01:14:30.87 - [60040.88 keys/sec]
  | The proxy says: "And Now For something completely different (alpaca.llamas.net)"
  | Network::Error Read Failed 27/0
  | The proxy says: "UNIX forever! (rc5unix.wwiv.org)"
  | Network::Error Read Failed 27/0
  | The proxy says: "Welcome to my nightmare. (x162-50.chem.umn.edu)"
  | Network::Error Read Failed 27/0
  | Network::Error Read failed 23/0
  | PutBuffer Error
  | Network::Error Read failed3/0
  | Unable to fetch more blocks, generating random block.
  | Please look into correcting your network problems as soon as possible.

**  RELEVANT PART OF THE FAQ?

  This is vague, but is this part of the FAQ mean that my problem is
  known, and might get fixed?

  | Why do I keep getting Network errors?
  | 
  | This problem is being resolved at this time. The v2 clients will
  | generate random blocks when needed, if a network connection cannot be
  | forged. This may be caused because of poor conditions on the internet,
  | or because you are behind a firewall (especially if you are behind a
  | firewall, if you are able to not send or recieve blocks at all).

**  SLIGHTLY DIFFERENT CONFIGURATION THAT WORKED ONCE

  I tries setting my Preferred KeyServer Proxy to rc5.slacker.com
  and managed to retrieve 1 block.  This was successful once in several
  tries.

  CLIENT CONFIG MENU
  ------------------
  1)  Email to report as [default:rc5 at distributed.net] ==> wheeler at ipl.rpi.edu
  2)  Blocks to Buffer [default:5] ==> 5
  3)  Blocks to complete in run [default:0] ==> 0
  4)  Hours to complete in a run [default:0] ==> 0
  5)  Keys per timeslice - for Macs etc [default:65536] ==> 65536
  6)  Level of niceness to run at [default:0] ==> 0
  7)  File to log to [default:] ==> 
  8)  Network communication mode [default:1] ==> 4
  9)  Preferred KeyServer Proxy
       [default:rc5proxy.distributed.net] ==> rc5.slacker.com
  11)  Local HTTP proxy address
       [default:wwwproxy.corporate.com] ==> nsproxy
  12)  Local HTTP proxy port [default:80] ==> 80
  0)  Quit and Save
  Choice --> 0
  % rc5v2 -update
  
  RC5 v2.004 client - a project of distributed.net
  Copyright distributed.net 1997
  Visit http://www.distributed.net/ for more information
  
  The proxy says: "Welcome to Slacker Central!  (rc5.slacker.com)"
  <
  [10/01/97 21:15:03 GMT] Retrieved 1 block(s) from server
  Update completed.

**  END
----
To unsubscribe, send email to majordomo at llamas.net with 'unsubscribe rc5' in the body.



More information about the rc5 mailing list