Help setup RC5 on a network

[Jarhead]

Does anyone know how to make RC5 run on a home network?

I've got my main machine with a dial-up, and I just
snagged a two sets of wireless networking cards for
60.00 (hot deals forum-Warplink). Can I have multiple
machines dipping into the buff-in/buff-out at the same
time?

Help

 

[Viztech]

You bet Jarhead!

Share the distributed.net directory in the dial-up machine with full access. I would suggest that you use the 'remote buffers' and use option 3 for additional buffer level checking in the network machine.

There are several other ways to do this, but this should work nicely.

viz

 

[rexfalk]

I'm a rank newbie to this RC5 thing but I have 3 machines, a 500 and a 1000 PIII's and a 500 PIII notebook all set up on my home network sharing the internet connection using Winrout. I set up the RC5 client on each machine and they all work seperately.
Would letting them all work on the same set be better or just let them continue to work independently be better.

Rex

 

[dawks]

They all have to work separatly. What you can do, as said before, is have one client connect, and download a huge amount of work, then the other clients can eat keys from the first ones buffer. But no, you cannot have them work in unison(sp?)

 

[JonB]

Once I got Internet Connection Sharing running well, I switched my four home PCs to all take care of their own buffers. They just go out thru the router to DSL, so its available just about 24/7.

Before, when it was just one modem and my PC had to be running for access, I used a personal proxy for the other three.

Overall, there is no big difference in output one way or the other.

 

[JimMc]

The PProxy is worth the effort if you're running W2K, into stats, and want to monitor the output from your herd.

 

[Viztech]

Rex-

If the Winrout system is working OK for you, and your clients can all keep fed don't worry about changing to another system. Where the remote buffering can be an advantage is when the remote clients do not have Internet connectivity themselves like ICS or a NAT solution.

Where this will work well for Jarhead is the fact that he is on a dial up. The client on the dial up machine is the key since it can be set to use dial up detection mode to flush and/or force a dial up itself to flush when it is needed. Buffer sharing is really designed for a handfull of remote clients to share (argueably 6 or less) but I have had upwards of 12 clients flush with remote buffers with one machine with dial up detection enabled.

Personal proxies are a more advanced solution. I believe that Dnet recommends to only run these on Linux, Win NT or 2000 boxes for stability reasons. They do run on Win 9x/Me, but I only use this to flush/fetch buffers for my sneaker pproxy at the school. Like Jim mentioned, pproxies are great for monitoring the herd due to the logging they do and the personal stats programs that are available to read them.

The Dnet client has many wonderful advanced features. For more complete instructions, take a look at the advanced FAQs at the TeAm website.

viz

 

[rexfalk]

Thanks for all the recomendations ! I'm using a DirecPC (only kind of semi-broadband I can gt out here) and just let Winrout run and trigger the dial up for upload when one of the clients needs to flush it's buffer. It's working well so far.
I just wanted to see if there was a more efficient way to do it all.
Now I think I'm going to find some more NIC cards and see if I can get a couple of more older computers that are just sitting around doing nothing online and working.
I can see how this could quickly become a second addiction ;-)


Rex