Message boards :
Questions and problems :
BOINC can't access internet, open firewall, no proxy.
Message board moderation
Author | Message |
---|---|
Send message Joined: 17 Dec 08 Posts: 4 |
Hi, this is my first post. I'm pretty impressed with boinc, but it seems I have a problem I can't quite figure out. I've searched through some of the other treads here, but don't see a similar one. I'm running BOINC 6.2.15 on Fedora 10. I installed it from the package manager, and set up the daemon according to the BOINC wiki. The problem is that it cannot access the net, even with the firewall turned completely off. I do have a router, but because I have BOINC running on a different computer that works fine, I haven't changed any of its settings. When I first fire up the boinc manager it connects properly to the local host, and presents the "attach to project" wizard. Because I signed up with gridrepublic I usually close that one and go to the "attach to project manager" screen. After putting in the g.r. url, the manager tries to connect and then shows a "Network communication failure" screen. The thing that stumps me is that this screen comes up regardless of the firewall settings. I added entries for ports 80, 443, and 31416, but it still fails, and it fails even if the firewall is turned off. I don't use a proxy. The only things I can think of are that it might be some weird Linux thing I haven't figured out, or it might be the boinc version. 6.2.15 has (pre-release) in the title bar. The whole thing is pretty strange to me. Why would the only version in my repository be so new? I would rather not install an older version manually (I'm no guru). So any advice? I appreciate the help. |
Send message Joined: 17 Dec 08 Posts: 4 |
Yes, I can access the internet. I use a wired connection for this computer (but it is a wireless router). |
Send message Joined: 17 Dec 08 Posts: 4 |
thanks! I can't believe I missed that article. I'll test this out next time I'm at that computer. also, sorry about the late replies, pretty busy recently. |
Send message Joined: 17 Dec 08 Posts: 4 |
Yep, this was the problem. Everything seems to be working fine now, so I added that line to the network config. I'm sure there won't be any issues, but I'll double check on the next reboot. Thanks again for the help! Time to get crunching! |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.