firewall BOINC server possible ?
29 Mar 2005 16:23:37 UTC
Topic 188793
(moderation:
I was wondering if it is possible to have a machine with access to the internet feed EAH to machines that do not have access to the internet. Linux code would be perferable, if such exists .....
-thanks
Robert Somerville
firewall BOINC server possible ?
)
> I was wondering if it is possible to have a machine with access to the
> internet feed EAH to machines that do not have access to the internet. Linux
> code would be perferable, if such exists .....
Maybe its me, but I don't fully understand the network ? layout you are imaging.
A linux box can be used as router/firewall (ip-forwarding/masquerading). I did this until 3yrs ago (SuSE7.2). All the machines however have acces to the internet then through this router, so they could be served by E@H that way, i suppose.
John,
yeah , i suppose thats what a
)
yeah , i suppose thats what a sane person would do. Just had this crazy thought that a boinc_client, could have/support its own cluster, rather than just the machine its running on. Got to quit being so points greedy, i guess ....
Robert Somerville
> thought that a
)
> thought that a boinc_client, could have/support its own cluster, rather than
> just the machine its running on.
I've been thinking of an own cluster that way too, but as Boinc/E@H is very picky on processor/OS/hostID I do not see any configuration for now to handle this.
Also the big merlin cluster(linux, einstein@work team) has all the nodes listed.
John,
> I was wondering if it is
)
> I was wondering if it is possible to have a machine with access to the
> internet feed EAH to machines that do not have access to the internet. Linux
> code would be perferable, if such exists .....
>
> -thanks
>
No - it's not possible at present. It used to be possible to this with the old version of SETI@Home, but it got abused. Some individuals started replicating work across different machines and returning the same result several times from different hosts to bump up their credit and their ranking. The problem got so bad that the rankings were largely meaningless, and the science itself was starting to suffer.
When BOINC came along the developers tied down the security so that the machine that was issued the work had to return it. This meant that the central server had to do all the work issuing data, and that, in turn, meant no local queues. It's now not possible to fiddle with the process at all, unless you're very determined, and possibly not even then.
I was actually thinking more
)
I was actually thinking more along the lines of a "super boinc client" that would down load multiple WU from EAH and feed them out to one of our internal Linux clusters when the cluster CPUs were not being used for real work .
I may have a peek at the Boinc code, but procrastination will probably win out
And until the speed & validation problems for Linux WU runs improve ,the motivation factor will stay low, i'm afraid :-(
I have to wonder if anybody is REALLY looking into the Linux validation problem ????
Bruce ?? Bernd ???
Robert Somerville
> I was actually thinking
)
> I was actually thinking more along the lines of a "super boinc client" that
> would down load multiple WU from EAH and feed them out to one of our internal
> Linux clusters when the cluster CPUs were not being used for real work .
>
> I may have a peek at the Boinc code, but procrastination will probably win out
>
>
> And until the speed & validation problems for Linux WU runs improve ,the
> motivation factor will stay low, i'm afraid :-(
>
> I have to wonder if anybody is REALLY looking into the Linux validation
> problem ????
>
> Bruce ?? Bernd ???
>
>
>
Hi Robert !
This has not been completely thought out, so there may a few nasties which bring it to fall... However, I would investigate a solution along two different lines, depending on the applicable configuration :
1.
Use tinyproxy on one of the Linux systems - the 'head' server, and run standard boinc and any boinc apps thru this proxy.
2.
Use iptables and NAT on the head Linux server, and standard boinc client and apps on the systems you choose to.
Regards.
-rg-
> Hi Robert ! > > This has
)
> Hi Robert !
>
> This has not been completely thought out, so there may a few nasties which
> bring it to fall... However, I would investigate a solution along two
> different lines, depending on the applicable configuration :
>
> 1.
> Use tinyproxy on one of the Linux systems - the 'head' server, and run
> standard boinc and any boinc apps thru this proxy.
>
> 2.
> Use iptables and NAT on the head Linux server, and standard boinc client and
> apps on the systems you choose to.
>
> Regards.
>
> -rg-
>
Both of these ideas should work. I know that using a NAT router works, and others have used Proxies of different sorts.
BOINC WIKI