I have a network of about 120 fast machines, which are able to run nightly to crunch. I'm running them with slitaz from network, so nothing on the machine has to be changed (except some disk space...). But daily the machines are used by other people with other OS.

I have an asymmetric internet connection (50 Mbps down/5 Mbps up). So I don't have any problem to get work to the machines and to calculate, but it's a problem to submit the results back to the server.

The biggest problem is climate prediction, which has files about 35 MB. And because all of the clients tries at the same time to send their big files, I have jam on the outgoing port. Some times there is nobody sending because ot the waiting timers.

Now I'd like to send all the results to my proxy before the bottleneck and use the connection the whole day to submit the results constantly to the server. So I need a Boinc Proxy or Boinc Relay.

Does anybody knows a solution for my problem. Of course, there is no money to paying for anything, but I'd like to put some time into a solution.

Thanks a lot!

You can use a normal proxy server with BOINC. I use Squid (rather dated on Windows but Linux versions are more up to date). You might need a bit of configuration stuff with it to limit it to 1 or 2 uploads at a time though.

---

MarkJ

Thank you for your advice. My problem is that the clients are not always online and the time they were online is not enough to send back all the results. So I'd like to use a relay server, store and sending back the results when the clients aren't available anymore.

I don't think I'm able to use squid, because squid doesn't play the Boinc server to the clients and not the clients to the servers... :-( I think I need a Boinc Relay. For Seti@home there was a Proxy server available, but not for boinc anymore. :-(

What you want is SuperHost, but sadly: The superhost idea has been proposed numerous times, but has not yet been implemented.

Problem

Large organisations wishing to run BOINC often don't want to open up their entire network to BOINC project servers, or allow unmanaged BOINC clients running on the network, potentially attached to unauthorised projects.
Solution

Promote one of the hosts to "superhost". All other hosts will only communicate with the superhost, and only the superhost requires Internet access.

But as said, not implemented yet.

---

NATE1: Did you use it?