Boinc-client can't access network when used with Gnome NetworkManager

[macbeth2]

I'm running boinc on fedora linux, and connect to the internet through an encrypted wireless network. At startup, the boinc-client service is started automatically and starts calculating. It can't access the network, though, since the wireless (with encryption key) is initialized by gnome networkmanager as a user logs in.

The problem is that even after I log in, and with the network active, boinc can't upload results or download new work. When looking at transfers in boinc manager, it keeps trying to upload, fails, and tries again after one minute. In messages, it reports that it can't resolve the hostname.

If I manually restart boinc-client after the network is active, then everything starts working.

[romw]

Could you try this private build which contains a bug fix which we think will resolve this issue: http://boinc.berkeley.edu/dl/boinc.060409.x86.sh

Thanks in advance.

[romw]

Are you using a distro specific version of BOINC?

Could you attach to a project other than WCG to test out the private drop? I noticed it was able to contact the reference server okay, which leads me to believe the first part of this worked and it was able to detect changes in the name servers.

I suspect that the second part to this equation, namely talking to WCG, is a product of the ca-bundle.crt file not being used. You could turn on the <http_debug/> option in cc_config.xml to verify.

[macbeth2]

Replying to romw:

Are you using a distro specific version of BOINC?

Yes, I was using the version that comes with fedora 10.

I suspect that the second part to this equation, namely talking to WCG, is a product of the ca-bundle.crt file not being used. You could turn on the <http_debug/> option in cc_config.xml to verify.

I copied ca-bundle.crt to the boinc data directory, and now it works. So the custom build effectively fixes the problem, thanks.

For some reason, the fedora version doesn't use the ca-bundle.crt file but still manages to communicate with WCG.

[romw]

This should be fixed in the latest 6.6+ releases