Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 3
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 652 times and has 2 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Linux Client configuration behind firewall

Hi,

I've searched through all the forums and I am still having problems with this. I have a Linux box behind a firewall that I would like to get the client running on. I do have access to a proxy server to get out of the firewall, but every config that I've seen for this type of setup doesn't work.

How do I configure the client to contact the WCG server from a clean install?

Thanks for your time.

Jared
[Dec 8, 2005 9:34:45 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Alther
Former World Community Grid Tech
United States of America
Joined: Sep 30, 2004
Post Count: 414
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Linux Client configuration behind firewall

Have you tried to run BOINC yet? What is the actual problem you are seeing? Can you post the messages from the log? It uses standard ports that are normally open in a firewall (basically, if you can browse the web, you can run BOINC).
----------------------------------------
Rick Alther
Former World Community Grid Developer
[Dec 10, 2005 5:40:35 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
angry Re: Linux Client configuration behind firewall

I share your frustration and submitted this as BOINCzilla bug #415

I have attempted to get the combination of BOINC 5.x.x and WCG working on multiple systems and platforms behind an authenticating proxy with only one success. Although all of those same boxes have no trouble connecting to other projects over 4.x.x clients, 5.x.x has been incredibly frustrating on both Windows and Linux.

To make matters more frustrating, the error code changes from release to release. It started for me as error code -500, then -113, now -102 with client 5.2.13

My only working configuration (Linux) through an authenticating proxy was achieved by issuing this command in the CLI:

./boinc_cmd --set_proxy_settings (parameters)

Ever since I did that, whatever was not functional in the config went away and that box has been running happily ever since. This fix does not seem to work in windows however. I am not a programmer and know almost nothing about XML. If anyone needs additional info I would be willing to provide it. If you find anything out, please let us know.
[Dec 14, 2005 3:25:05 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread