BOINC GUI RPC over SSH tunnel

Message boards : Questions and problems : BOINC GUI RPC over SSH tunnel
Message board moderation

To post messages, you must log in.

AuthorMessage
dkbg

Send message
Joined: 28 Mar 12
Posts: 1
Canada
Message 43192 - Posted: 28 Mar 2012, 16:54:57 UTC
Last modified: 28 Mar 2012, 16:59:18 UTC

So I'm trying to connect to the BOINC client running on a computer on my LAN through an SSH tunnel for some added security. The BOINC manager connects just fine without any SSH tunnel (via the "Select computer..." option), but whenever I try to tunnel through SSH, it doesn't connect.

I've been forwarding port 31416 via an SSH LocalForward directive to the server (which appears to be the port BOINC is using for RPC communication despite 1043 being the officially registered port from what I've read) but whenever I try to connect, it attempts connection, then fails. I've also tried forwarding port 1043. In that case the BOINC manager GUI just hangs on "Connecting to localhost..." in the status bar.

Looking for any insight anyone might have.

EDIT: sorry, forgot to mention versions. The BOINC manager GUI is version 6.12.35 (running on Fedora 16). The BOINC daemon on the server (which is running Debian stable) is version 6.10.58 (using Debian's package).
ID: 43192 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15483
Netherlands
Message 43194 - Posted: 28 Mar 2012, 19:04:41 UTC - in response to Message 43192.  
Last modified: 28 Mar 2012, 19:07:26 UTC

I've been forwarding port 31416 via an SSH LocalForward directive to the server (which appears to be the port BOINC is using for RPC communication despite 1043 being the officially registered port from what I've read) but whenever I try to connect, it attempts connection, then fails.

I can't help you on the SSH tunnel problem, but will ask a developer if he knows (edit: he says he doesn't). On the port number, BOINC used to use 1043, but other programs would run interference using this port on Windows XP start-up. Most notorious were some Microsoft programs, such as MSN and Hotmail.

So the port number was changed to 31416, which is high enough in the list not to get interfered with.
ID: 43194 · Report as offensive
mpw

Send message
Joined: 18 Feb 13
Posts: 6
Germany
Message 47830 - Posted: 18 Feb 2013, 13:20:47 UTC - in response to Message 43194.  
Last modified: 18 Feb 2013, 13:46:51 UTC

This works quite nice for me:

1.) Make sure the boinc client does NOT run locally.

2.) Forward the port:

ssh -L 31416:localhost:31416 your.remote.host


3.) Make sure that the boinc client runs on the your.remote.host-machine

4.) Start boinc manager

=> Works for me.

This does not work, if a boinc client runs locally, as the port can't be forwarded then. You could look if you find a way to change the port of the boinc manager then like: NEWPORT:localhost:31416 your.remote.host. But I don't know there to change the port in the boinc manager.

I'm using this way to control my Raspberry Pi.
ID: 47830 · Report as offensive

Message boards : Questions and problems : BOINC GUI RPC over SSH tunnel

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.