BOINC on remote host

maxll
maxll
Joined: 18 Mar 05
Posts: 2
Credit: 219,015
RAC: 0
Topic 188927

How can i connect BOINC-manager (v. 4.25 Win32) to BOINC-client on remote host. I cant do that, when i try to connect (File/Select computer...) to remote BOINC, "GUI RPC request from non-allowed address *.*.*.*" shows up in BOINC log-messages on remote host.

Whats wrong, or what i have to do?

BamBam
BamBam
Joined: 22 Jan 05
Posts: 4
Credit: 42,122
RAC: 0

BOINC on remote host

> How can i connect BOINC-manager (v. 4.25 Win32) to BOINC-client on remote
> host. I cant do that, when i try to connect (File/Select computer...) to
> remote BOINC, "GUI RPC request from non-allowed address *.*.*.*" shows up in
> BOINC log-messages on remote host.
>
> Whats wrong, or what i have to do?
>
Hi Maxll,

you have to start the boinc client with the option -allow_remote_gui_rpc, than you can connect the client from an other host.

BamBam

maxll
maxll
Joined: 18 Mar 05
Posts: 2
Credit: 219,015
RAC: 0

-allow_remote_gui_rpc Ok,

-allow_remote_gui_rpc
Ok, thanks, it works.

Next question: what can i do if BOINC-client started as service?

BamBam, Congratulations with BOINC-100thousands :)

Keck_Komputers
Keck_Komputers
Joined: 18 Jan 05
Posts: 376
Credit: 5,744,455
RAC: 0

Create a text file in the

Create a text file in the BOINC directory called 'remote_hosts.cfg'. Place IP addresses or host names one per line for each host you wish to access from in this file. You will have to restart the client.

BOINC WIKI

BOINCing since 2002/12/8

John McLeod VII
John McLeod VII
Moderator
Joined: 10 Nov 04
Posts: 547
Credit: 632,255
RAC: 0

> Create a text file in the

Message 10361 in response to message 10360

> Create a text file in the BOINC directory called 'remote_hosts.cfg'. Place IP
> addresses or host names one per line for each host you wish to access from in
> this file. You will have to restart the client.
>
This file goes on the computer that will be controlled.

gravywavy
gravywavy
Joined: 22 Jan 05
Posts: 392
Credit: 68,962
RAC: 0

RE: > Create a text file in

Message 10362 in response to message 10361

Quote:
> Create a text file in the BOINC directory called 'remote_hosts.cfg'. Place IP
> addresses or host names one per line for each host you wish to access from in
> this file. You will have to restart the client.
>
This file goes on the computer that will be controlled.

OK, my next question is the use of the Password field of the File/Select Computer dialogue box. Is this a windows password (supposing the client is on a windows box)? Or is it a BOINC password and if so, how do I specify the password?

~~gravywavy

Blank Reg
Blank Reg
Joined: 18 Jan 05
Posts: 228
Credit: 40,599
RAC: 0

Access control for GUI

Access control for GUI RPC
Since GUI RPCs can control the BOINC client (e.g. attaching/detaching projects) it is important to protect your BOINC client from unauthorized control. There are two levels of protection:
You can associate a password with the client; GUI RPCs must be authenticated with this password.
You can restrict RPCs to a limited set of hosts.
Password protection
If you place a password in a file gui_rpc_auth.cfg in your BOINC directory, GUI RPCs must be authenticated using the password.
Remote host restriction
By default the core client accepts GUI RPCs only from the same host.
You can allow remote hosts to control a core client in two ways:
If you run the client with the -allow_remote_gui_rpc command line option, it will accept connections from any host. This is not recommended unless the host is behind a firewall that blocks the GUI RPC port (1043).
You can create a file remote_hosts.cfg in your BOINC directory containing a list of allowed DNS host names or IP addresses (one per line). Those hosts will be able to connect. The remote_hosts.cfg file can have comment lines that start with either a # or a ; character as well.

gravywavy
gravywavy
Joined: 22 Jan 05
Posts: 392
Credit: 68,962
RAC: 0

RE: Access control for GUI

Message 10364 in response to message 10363

Quote:
Access control for GUI RPC
...

many thanks for the prompt reply (under 30mins!) and as a bonus you answered my next question as well - the port number to open in a firewall (1043).

The password is essential in my case as I will be installing BOINC on a directly-connected server (ie one with a public IP address), my usual form of access is from inside a LAN, and I did not want to give everyone else on my LAN access to my BOINC client! I will limit the IP to the public IP address of our LAN's firewall, which keeps most of the world out, and use the password to keep out my neighbours.

~~gravywavy

Blank Reg
Blank Reg
Joined: 18 Jan 05
Posts: 228
Credit: 40,599
RAC: 0

All that is known is in the

All that is known is in the WIKI and more will be revealed as time passes....;0)

John McLeod VII
John McLeod VII
Moderator
Joined: 10 Nov 04
Posts: 547
Credit: 632,255
RAC: 0

RE: RE: Access control

Message 10366 in response to message 10364

Quote:
Quote:
Access control for GUI RPC
...

many thanks for the prompt reply (under 30mins!) and as a bonus you answered my next question as well - the port number to open in a firewall (1043).

The password is essential in my case as I will be installing BOINC on a directly-connected server (ie one with a public IP address), my usual form of access is from inside a LAN, and I did not want to give everyone else on my LAN access to my BOINC client! I will limit the IP to the public IP address of our LAN's firewall, which keeps most of the world out, and use the password to keep out my neighbours.


If the controlling computer is on the LAN, use the IP of that computer, and all should be good. The password is stored in cleartext in the file, but it only controlls access to BOINC. Make certain that you limit access to the BOINC directory - possibly to a BOINC specific user that has no rights anywhere else.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.