Perproxy setup

[paleseptember]

Finally got my new computer for work, but it's loaded up with McAfee, which thinks dnetc is a virus and deletes the files before I can install them.

So, downloaded the DOS version, joy of joys, McAfee allows it to run.

Unfortunately, the DOS version has no networking support, nor does it appear to recognise multicore systems. My plan was to use a personal proxy to get the workunits.

So, I can extracted the DOS client into four separate directories:
C:/DC/dnet1
C:/DC/dnet2
C:/DC/dnet3
C:/DC/dnet4

and downloaded the perproxy client, and put that into
C:/DC/dnetproxy/

I've grabbed IronBit's .ini file from http://www.free-dc.org/forum/showpos...7&postcount=39
and changed only the uuehttpmode=2 option and put in my firewall/proxy details.

[KeyServer]
ipaddress=pproxy.free-dc.org
;ipaddress=us.v29.distributed.net
port=2064
connectperiod=600
connectivity=normal
;bindip= ; IP to talk out to keyserver from
uuehttpmode=2
; 0=normal,1=uue,2=http,3=http+uue
; 4=socks4,5=socks5,6=genproxy,7=genproxy+uue
httpproxy=proxy.uow.edu.au
httpport=8080
httpid=**taken from DNETC.ini-encrypted username/pwd**

[ports]
;listenaddress= ; IP to accept clients on
port=2064
;port2=23 ; must be root for ports < 1000
;port3=80
;testport=3064
timeout=30

[console]
logfileconsole=
;logfileconsole=Console
;logfileconsolerotation=monthly
logfileconsolerotation=daily
;consoleverbosity="stats keyblock server timestamp buffers"
consoleverbosity="general stats keyblock server client buffers timestamp attention errlow errsevere"
timestampflags=130

[rc564]
logfilekeyblock=pproxyrc5
logfilekeyblockrotation=daily
minkeysready=10
maxkeysready=20
maxkeysdone=3
contestclosed=1

[rc5-72]
logfilekeyblock=pproxyrc572
logfilekeyblockrotation=daily
minkeysready=100
maxkeysready=200
maxkeysdone=3

[desII]
logfilekeyblock=pproxydes
logfilekeyblockrotation=daily
minkeysready=10
maxkeysready=20
maxkeysdone=3

[ogr]
logfilekeyblock=pproxyogr
logfilekeyblockrotation=daily
minkeysready=10
maxkeysready=20
maxkeysdone=3
contestclosed=1

[ogrp2]
logfilekeyblock=pproxyogrp2
logfilekeyblockrotation=daily
minkeysready=10000
maxkeysready=20000
maxkeysdone=3

[csc]
logfilekeyblock=pproxycsc
logfilekeyblockrotation=daily
minkeysready=10
maxkeysready=20
maxkeysdone=3

[misc]
proxymessage="My Wonderful Personal Proxy!"
pidfile=rc5desproxy.pid
statusperiod=60
periodicperiod=120
;logfilecompressor=logcompressor.sh

[ignoredip]

[allowedip]

The problem is, I don't know how to setup my clients to talk to the proxy.

My DNETC.ini looks like

[parameters]
id=benmaloney@yahoo.com

[display]
progress-indicator=auto-sense

[networking]
firewall-type=http
firewall-host=proxy.uow.edu.au:8080
firewall-auth=****
autofindkeyserver=no
keyserver=*:2064;localhost

[misc]
project-priority=OGR-P2,RC5-72=0

[buffers]
alternate-buffer-directory=C:/DC/dnetproxy/

I don't know what else I should try.

[IronBits]

That one is easy
change this: keyserver=*:2064;localhost
to this: keyserver=*:2064;pproxy.free-dc.org

http://stats3.free-dc.org/dnet/ogr/byemail.html - OGR
http://stats3.free-dc.org/dnet/rc572/byemail.html - RC5

or, if you don't want to use Bok's proxy server,
change this: autofindkeyserver=no
to this: autofindkeyserver=Yes

[paleseptember]

Sorry, didn't work >.<

I think because I'm using the DOS version (apparently no networking support), I can't directly connect to a keyserver, which is why I'm trying to use my own proxy server, and get my clients to just get their workunits from this local machine.

I think I've got the proxyper setup okay. I now have files
ppdone.r72
ppogrin.ogr
ppogrin.p2
ppogrout.ogr
ppogrout.p2
pprc5in.rc5
pprc5out.rc5
ppready.r72

in my dnetproxy directory.

Do I need to tell my client the number of the buffer files? The expected names are buff-in.ogf, etc?

Thanks in advance

(Stupid McAfee, I could make this work on my old machine!)

[IronBits]

You could always dump McAfee, it's not that good anyways...
AVG Free is Highly rated! top 4 here: http://anti-virus-software-review.toptenreviews.com
There are many others to choose and use...

http://www.download.com/AVG-Anti-Vir...-10320142.html

There was a thread someplace where dnet tried to appease the company to get an exemption, but they won't cooperate, so speak with your wallet, erm, rather don't, maybe they will get the message finally, or not.

Found it: http://n0cgi.distributed.net/cgi/dne...?user=mikereed

Dear friends,

We have recently been in communication with a number of vendors of anti-virus
software, regarding their false detections of dnetc. Many of them have been
brought around to our point of view that dnetc is benign, peaceful and able to
happily co-exist on a busy workstation. Our attempts to bring McAfee around to
our point of view have failed, despite our best efforts.

We would like to re-open hailing frequencies with McAfee and we need your help
to do this. On their site is a page describing dnetc as a 'potentially unwanted
program'. You can see it here:- http://vil.nai.com/vil/content/v_100867.htm

At the side of the page is a link 'Rate This Potentially Unwanted Program'. We
would like as many of you as possible to visit the page and let McAfee know
that dnetc should not be detected.

We remain grateful for your continued support and enthusiasm.
Moo! ]:8)

[paleseptember]

IT services only delivered the computer to me this morning. I'm rather reluctant to start disabling all the programs just yet.

How do the PS3 owners get their clients to talk to their personal proxy? I think it's the client trying to fetch the buffer file that I'm having stupid issues with.

I guess my other option is just to fetch and flush via email

[IronBits]

On the clients
change this: keyserver=*:2064;localhost
to this: keyserver=*:2064;192.168.0.123 (where you change it to the IP address of the computer running the pproxy server.)
If the pproxy server is on the local computer as well, then that should work fine and the clients don't need to be setup to go thru any corp. proxy server.

The pproxy server will need to go through the corp proxy firewall to fetch and flush work from/to the outside world and that's where the
change this: keyserver=*:2064;localhost
to this: keyserver=*:2064;pproxy.free-dc.org
comes into play.

If you are running your own pproxy server on that computer as well, you can use the regular dnet clients, and not worry about DOS stuff.

*cough* a new computer with crap software pre-installed *cough*

I run a pproxy server on my old trusty mac mini, which fed all 10 PS3s just fine