BOINC Tasks - finding other computers on network?

[DrPop]

I'm sure that works fine, I mean now that I see how it works, it's like a Boinc Manager on steroids

Z's way was just easy for me since he posted the cc_config. Works pretty good from what I can tell so far. Now just to see if the rule I setup works!

[Fire$torm]

I'm sure that works fine, I mean now that I see how it works, it's like a Boinc Manager on steroids

Z's way was just easy for me since he posted the cc_config. Works pretty good from what I can tell so far. Now just to see if the rule I setup works!

OK, just be aware that the allow_remote_gui_rpc will open up the client to any machine that can find it. So it is a potential security risk especially since BOINC uses the RPC communication protocol. RPC is horribly insecure ---> http://technet.microsoft.com/en-us/l.../cc751166.aspx

[Bryan]

If you decide to only allow certain IP addresses to control your machines then you can configure it that way. The only problem is you have to have FIXED IP addresses so that the computers don't change when they connect to your network (ie no DHCP). You can either do that modifying the IPv4 on each network card or using the MAC addresses on your router.

I use this (fixed IP) on my machines and like F$ I have BTasks setup on each computer because I tie into them via a VNC. I usually only have it running on a single machine but it is installed and ready to go on any of them. That way if I lose a machine I can tie into another one and control any machine from it.

[Fire$torm]

Sorry I forgot something. Bryan's post reminded me.....

I used my ISP's supplied router to give each system on my network a static it. It should take you like ten minutes to do the same. That way you do not have to configure the systems individually.

If you need a guide to help you take a look at Portforward's repository of router guides (Here)

[zombie67]

Blah, blah, blah, security, blah, etc. If you are behind a modern router, you're fine.

Back on topic, DrPop, let me guess how it feels to see all your tasks in one manager...KING DICK! Holy crap! Why has no one told me about this before?! THIS is how it's done!! You can so easily se where there are issues that need attention without checking on each machine one at a time. Oh, and be sure to expand on the colors. I use (say) vivid green for running tasks, medium green for waiting tasks, and light green for unstarted tasks. A similar scheme but blue, for GPU tasks. And bright red for suspended, and eror tasks. Now you actually control your BOINC world.

[DrPop]

It is pretty cool to see all the computers' tasks from one rig, that's for sure! This thing ought to come bundled with the BOINC download!

I like the idea of the color scheme, that sounds very useful. Now we just need an Android and iOS apps that tie into it so we can check out how things are running when away... I suppose if you wanted to get crazy you could do a log-me-in session from the Central rig running BOINC Tasks.

[Mumps]

It is pretty cool to see all the computers' tasks from one rig, that's for sure! This thing ought to come bundled with the BOINC download!

I like the idea of the color scheme, that sounds very useful. Now we just need an Android and iOS apps that tie into it so we can check out how things are running when away... I suppose if you wanted to get crazy you could do a log-me-in session from the Central rig running BOINC Tasks.

Umm, have you checked out the "WWW" option on BoincTasks? You can set up your machine running BoincTasks to listen for a web connection and display what BoincTasks would normally be displaying on the local computer. It won't let you control your hosts, but it will let you see the status...

[Slicker]

OK, just be aware that the allow_remote_gui_rpc will open up the client to any machine that can find it. So it is a potential security risk especially since BOINC uses the RPC communication protocol. RPC is horribly insecure ---> http://technet.microsoft.com/en-us/l.../cc751166.aspx

BOINC doesn't actually use Microsoft's RPC calls. Instead, it uses a TCP connection on port 31416 and send/receives XML. The data is not encrypted. Some BOINC info can be accessed without authentication but commands that change preferences, join or detach from projects etc. require authentication. The password is hashed prior to authenticating and the hash is not reusable from one connection to the next.

However, if you open port 31416 to the Internet, someone could do a brute force attack and eventually guess your password since BOINC does not lock anything down after a given number of invalid login attempts.

[Fire$torm]

BOINC doesn't actually use Microsoft's RPC calls. Instead, it uses a TCP connection on port 31416 and send/receives XML. The data is not encrypted. Some BOINC info can be accessed without authentication but commands that change preferences, join or detach from projects etc. require authentication. The password is hashed prior to authenticating and the hash is not reusable from one connection to the next.

However, if you open port 31416 to the Internet, someone could do a brute force attack and eventually guess your password since BOINC does not lock anything down after a given number of invalid login attempts.

Really? I'm a little surprised as any docs I've read about BOINC communications says it does. Or is that on the localhost?

[artemis8]

Thank you so much. Now I can control all three computers from one now too