I can\'t attach my boinc client to the climateprediction project.
I\'m in the University and behind a proxy-server and firewall. Does that matter for boinc?

I get the following output:
<pre>
$ ./boinc_4.02_i686-pc-linux-gnu -attach_project
Enter the URL of the project: http://climateprediction.net
You should have already registered with the project
and received an account key by email.
Paste the account key here: MY_ACCOUNT_ID
2004-08-09 16:08:39 [---] Starting BOINC client version 4.02 for i686-pc-linux-gnu
2004-08-09 16:08:39 [http://climateprediction.net/] Project prefs: using your defaults
2004-08-09 16:08:39 [http://climateprediction.net/] Host ID not assigned yet
2004-08-09 16:08:39 [---] No general preferences found - using BOINC defaults
2004-08-09 16:08:39 [---] CPU scheduler starvation imminent; requesting more work
2004-08-09 16:11:48 [http://climateprediction.net/] Master file fetch failed
2004-08-09 16:11:48 [http://climateprediction.net/] Master file fetch failed
BOINC couldn\'t get main page for http://climateprediction.net/.
Please check the URL and try again.
2004-08-09 16:11:48 [http://climateprediction.net/] Resetting project
2004-08-09 16:11:48 [http://climateprediction.net/] Detaching from project
</pre>

I tried with an environment variable HTTP_PROXY. I also set the proxy in the client_state.xml. But I always get the same error.
Or is the URL wrong? Or is it another problem?

I have a similar problem with one machine behind a firewall.
Can you reach http://climateprediction.net from a web browser?
Does it respond to pings?

From a web browser, it is no problem to reach http://climateprediction.net

But to pings, it does not respond.
<pre>
$ ping climateprediction.net
PING climateprediction.net (137.108.64.33) 56(84) bytes of data.

--- climateprediction.net ping statistics ---
174 packets transmitted, 0 received, 100% packet loss, time 172994ms
</pre>
I do not have any problems at home (to pings, the server does not respond even from home - so that should be no problem). It would be very sad if I can't use the power of the machines inside the university...

As I have seen right now, the boinc client is listening on a tcp port.
<pre>
tcp 0 0 0.0.0.0:31416 0.0.0.0:* LISTEN 2129/boinc_4.02_i68
</pre>
This port will be blocked by the firewall for sure. Does anybody know a workaround?

_____________________________________________________________
Phantasie ist wichtiger als Wissen, denn Wissen ist begrenzt. (Albert Einstein)

We've gotten the proxy to work using the environment variables. A ping to our servers may not work as I don't think we are letting ping packets through. I can't imagine BOINC is listening to any ports since it's just straight HTTP/port 80 calls?

I tried with many different settings now. And I found a working one.
If I set the env variable HTTP_PROXY to http://proxy.unibe.ch (without port), then it works.
If I find some time, I will try with some more settings.
But the output of netstat is still a bit confusing:
<pre>
# netstat -lnpt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:31416 0.0.0.0:* LISTEN 15050/boinc_4.02_i6
</pre>


_____________________________________________________________
Phantasie ist wichtiger als Wissen, denn Wissen ist begrenzt. (Albert Einstein)

&gt; As I have seen right now, the boinc client is listening on a tcp port.
&gt; <pre>
&gt; tcp 0 0 0.0.0.0:31416 0.0.0.0:* LISTEN
&gt; 2129/boinc_4.02_i68
&gt; </pre>
&gt; This port will be blocked by the firewall for sure. Does anybody know a
&gt; workaround?
&gt;

Port 31416 is for separate gui, and if you're not using either -allow_remote_gui_rpc or has a separate file "remote_hosts" the client will only accept connections from localhost.

Connecting to scheduling-servers &amp; downloading/uploading is through port 80, so if you can browse you should also have the opportunity to use BOINC.

<p>in the client_state.xml search for<br>
<br>
&lt;proxy_info&gt;<br>
...<br>
&lt;/proxy_info&gt;<br>
<br>
edit the proxy lines and add the tag &lt;use_http_proxy/&gt; <br>
<br>
now it should look similarly like this:<br>
<br>
&lt;proxy_info&gt;<br>
&lt;use_http_proxy/&gt;<br>
&lt;socks_version&gt;4&lt;/socks_version&gt;<br>
&lt;socks_server_name&gt;&lt;/socks_server_name&gt;<br>
&lt;socks_server_port&gt;80&lt;/socks_server_port&gt;<br>
&lt;http_server_name&gt;proxy.test.com&lt;/http_server_name&gt;<br>
&lt;http_server_port&gt;80&lt;/http_server_port&gt;<br>
&lt;socks5_user_name&gt;&lt;/socks5_user_name&gt;<br>
&lt;socks5_user_passwd&gt;&lt;/socks5_user_passwd&gt;<br>
&lt;http_user_name&gt;&lt;/http_user_name&gt;<br>
&lt;http_user_passwd&gt;&lt;/http_user_passwd&gt;<br>
&lt;/proxy_info&gt;</p>

.mostly harmless
jeamy
http://www.jeamy.com/