Hi Cap.

I usually just use synaptic but since I've been have this problem with Boinc pinging my router all the time, I wanted to try another version.
I already tried a clean install of Boinc 7.0.27 it's made no differance, so I went and got this version in deb file format at least they can be installed with synaptic.

Hi SekeRob.

Looks like you are right,, when I shut down the client the router lights stopped. So now how do I fix this can I change it somewhere.
No I don't have any of those programs at all, how did the address get changed I installed the same as before Ubuntu crashed.
edit // I'd be most happy to not have to install boinc again,, I've now got 4 of the same rig on here as it is because we can't merge computers here.


Thanks.

Your right I meant manager, always mix those.

Tried putting in localhost nothing happened, then tried 127.0.0.1 manager shut down / disappeared completely.
I'm still running Boinc 7.0.27 form synaptic a.t.m. & I haven't used the remote_hosts.cfg so I'll see if I can find that file & change the i.p. if it's wrong.

This is interesting,

Your startup messages show that gui_rpc is authorized


But there is nothing in the gui_rpc_auth.cfg file?

You might try looking at the cc_config.xml file in the BOINC data directory and see what it has for gui_rpc configuration. From the cc_config configuration page

 <allow_remote_gui_rpc>0|1</allow_remote_gui_rpc>
    If 1, allow GUI RPCs from any remote host

If it is in there and set to 1 you might try changing to 0 and see what happens.

Not something I use so I am guessing, but it is worth a look.
Hope that helps.

That line is... carte blanche. "Any remote host" can issue RPC calls to the device. If you trust your environment to be knocked up tight behind unscalable firewall, then you're fine and it's convenient. No remote_hosts.cfg to maintain all your BOINC client IPs in.

As for the password, far as I remember the password gui_rpc_auth.cfg file of 7.0.27 in the official repository is blank, same as all the Gianfranco builds. I have a suspicion something is broken there since longer as that was also with 6.10 on Linux, as putting a password in stops any attempt to connect remote or local, by BOINCmgr or boinccmd.

Anyway we're straying way off the problem. P.P.L. needs to connect the boincmgr to the core client using localhost or 127.0.0.1. When that proposed entry is added to the remote_hosts.cfg [make sure to use sudo when editing] and client restarted boincmgr should be able to connect over the local IP and -not- over the LAN IP which is the issue [it does not do that by itself... the user did something]. Then, right bottom the boincmgr prints it's connected over... "Connected over localhost (7.0.27)" and no more constant router polling would happen. Guaranteed (as long as you don't remotely connect to that client ;>).

Oh and yes, 'hosts' is a mostly forgotten but very useful system file to store fixed IP addresses... for instance, add WCG IP and things go a tad faster since it wont have to interrogate the ISP/Internet DNS service, and even when the DNS service is down or polluted I get to connect, if WCG is up and connected. The file is in a subdir of ../etc/.., something which Windows has in common with Linux [shock and horror]. Using it all the time, since about 1985.