Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Dabble, but latest used are Fedora 13 and Ubuntu 10.4.1
Posts: 425
Rep:
BOINC won't connect to internet
Running Fedora Core 10 (2.6.27.29 kernel) and installed BOINC. Got the BOINC client and manager to talk to each other, but when I select a Boinc project to use, I get an error saying that it cannot connect to the internet. I've set www (port 80) as trusted in my firewall (standard Fedora 10 issue) but no change.
Any ideas? The BOINC people are suggesting a reinstall, but I'd like to see if I can tinker with the firewall first, since reinstalling BOINC won't change anything about my firewall.
Normally that port setting is for incoming to a local webserver. You need to allow outgoing to BOINC and then add 'ESTABLISHED' rule for return pkts.
Try posting your iptables
Distribution: Dabble, but latest used are Fedora 13 and Ubuntu 10.4.1
Posts: 425
Original Poster
Rep:
Quote:
Originally Posted by chrism01
Normally that port setting is for incoming to a local webserver. You need to allow outgoing to BOINC and then add 'ESTABLISHED' rule for return pkts.
Try posting your iptables
iptables -nvL
What port(S) does BOINC use?
I have no idea how to allow outgoing to boinc, nor how to add "established" as a rule for return packets.
Boinc, as I said, used port 80. That is what it says. No other ports are mentioned.
I have done nothing to change my iptables from whatever is the default when one sets up the default firewall as desktop and says that he is a "beginner." I am profoundly ignorant of internet security, and refuse to start screwing around with internet connections when I do not understand what is going on.
I may not owe my fellow internet users much, but I owe them the effort to not become a problem. Knowing that, what, precisely, is "iptables -nvL" going to tell you?
It tells us what your iptables (firewall) settings are ie which ports (services) are allowed to let data in, let it out, or even forward it (don't worry about forwarding).
It also says where to / from those ports can send to/listen to.
There are loads of tutorials for iptables eg http://www.linuxhomenetworking.com/w...Using_iptables .
Distribution: Dabble, but latest used are Fedora 13 and Ubuntu 10.4.1
Posts: 425
Original Poster
Rep:
Quote:
Originally Posted by chrism01
It tells us what your iptables (firewall) settings are ie which ports (services) are allowed to let data in, let it out, or even forward it (don't worry about forwarding).
It also says where to / from those ports can send to/listen to.
There are loads of tutorials for iptables eg http://www.linuxhomenetworking.com/w...Using_iptables .
I apologize. I was frustrated when I wrote my response.
I will get back to you in a bit with the information you asked for, but I can tell you right now that I will probably uninstall boinc before I screw around with iptables. I don't have the time to immerse myself in iptable lore, I've read too many posts here where people have compromised boxes because they played with iptables and got it wrong, and I am not going to have my system become a problem for others.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.