Yes, and you can control BOINC from console with the boinccmd tool that comes with BOINC. Also there is the great BOINCTUI [Text User Interface] for console which allows to watch and control all your running hosts on a (W)LAN, Linux, Windows, does not matter.

Thanks for that, Thargor.

Yes those are the 2 critical files to connect remotely. Ideally all your hosts have the same copy of those 2 files which makes connecting and maintenance simple, all with the same password, or no password as my Ubuntu Repo copy comes with.

Mind you, there's the issue of DHCP and variable IPs. I've overcome that by pre-assigning IPs from the router switch to each known MAC [No guests can connect to hotspot without my intervention even if they could make out the router password].

You could tell BOINC to allow connect from any device [If you feel save and behind a good NAS/Firewall structure that's the simplest]. That requires to put <allow_remote_gui_rpc>1</allow_remote_gui_rpc> in a third file named cc_config.xml.

Just wanted to post an update, your guy's steps worked perfectly. I now have a pretty beefy server running this. It was pretty much idol for 22 hours a day so I am happy to know that it is being put to good use.