I am, for a laugh, having a go at setting up the default Upper Case BOINC project.

I have created the BOINC Server on VMWare

See Computing with BOINC



I have a Linux virtual server on a windows XP box

I can connect to and run the Uppercase Project using my normal BOINC Manager from another computer on my LAN ( http://192.168.x.x/test/ )

How do I do the same from another computer on the internet? ( http:// ????? )

Just curious...

---

Join TeamACC

Sometimes I think we are alone in the universe, and sometimes I think we are not. In either case the idea is quite staggering.

I have been running an OpenSolaris virtual machine on my Linux box using VirtualBox. Both BOINC client and SETI app are by Dotsch. Apart from the fact that every time SuSE sends me a kernel upgrade for security reasons the virtual machine refuses to start and I have to reload VirtualBox, the SETI app is about four time slower than the optimized app I am using on the Linux box, which has the Opteron 1210 CPU at 1.8 GHz. The reason I started experimenting on virtual machines is that at CERN they are working on a CERN Virtual Machine able to run the LHC@home app on all platforms. It should be presented at the BOINC workshop in London this month's end by dr.Ben Segal of CERN, who has asked me to give him my private email address, so that we could exchange our experiences.
Tullio

---

You need to run a service such as dyndns.org and open your firewall to forward HTTP requests to that virtual server. Chances are good that you won't be able to do that because most ISPs block incoming HTTP traffic. If you can figure it out, sometimes using HTTPS instead will work.

I like this quick start tutorial to get a BOINC server up. I would ultimately prefer separate RPM packages for each component with unified configuration files. Similar to the way SETI separates each daemon, I would like separate daemon processes to run but be able to work together out of the box.

@tullio
CERN Virtual machine, do you mean like the BOINC Wrapper, eg yoyo@home


@DJStarFox
Are you saying it might be impossible/difficult for me to directly contact my computer/server via the internet, because ISPs block incoming HTTP traffic, is this the same for Remote Assistance etc

---

Join TeamACC

Sometimes I think we are alone in the universe, and sometimes I think we are not. In either case the idea is quite staggering.

Are you saying it might be impossible/difficult for me to directly contact my computer/server via the internet, because ISPs block incoming HTTP traffic, is this the same for Remote Assistance etc

Yes. Not the same as Remote Assistance.

All I know is this:
Virtual Machines
Tullio

---

@DJStarFox
Are you saying it might be impossible/difficult for me to directly contact my computer/server via the internet, because ISPs block incoming HTTP traffic, is this the same for Remote Assistance etc

most ISp's block incomming port 80 (web server) as well as other server ports
I doubt that boinc is using the ports of other services IE rpc uses port 31416

FYI
your posting this in the seti@home number crunching forum Why?
If you Try the boinc forums there might be more help there

Cheers

---

Depends how the machine is connected to the internet.

If you have a typical SoHo (small office / home office) router, you needs to find "Open Ports setup" (or words to that effect), and tell it which local IP address you want the BOINC requests (on port 80) to be forwarded to - that'll be the IP address of the virtual machine, that you're already using for the internal testing.

Your router's "Online Status" (or equivalent) page will give you your currently-assigned public or WAN address. Once you know that, you can test with http://ppp.qqq.rrr.sss/test

The next question depends on whether you've got a 'static' or 'dynamic' IP address assigned to your internet access account. Some ISPs (like PlusNet) always give you a static IP address - it never changes, so you can go on using ppp.qqq.rrr.sss for ever. But the cheapskates (like BT) give you a dynamic address, and charge extra for static. That's where DYNDNS comes in - you can register for an account, and provided you keep updating it as your public IP address changes (not often - just when the router drops the connection, or there's a power cut), you can use the http:// address assigned by DYNDNS and always find your own router.

I don't know of any ISP that wouldn't let you do that sort of thing, at least on an occasional basis - it's often used for home automation (call home and run a hot bath before you arrive...) or security/CCTV. ISPs might object if you set up a full home server and offered downloads, using a lot of bandwidth, on a cheap home DSL account.

most ISp's block incomming port 80 (web server) as well as other server ports
I doubt that boinc is using the ports of other services IE rpc uses port 31416

BOINC only uses port 31416 for communication between the core client and the manager - two different processes, which typically both run inside the same machine (although a manager on one machine can communicate that way with a client on another machine).

Kinhull is trying to mimic the communications between a boinc client and a boinc server - that happens on http port 80 (or more rarely https port 443 - WCG uses that, I think).

Thanks for the info guys, I'll see what happens, though I don't have a router, just a DSL modem and an ethernet LAN hub

---

Join TeamACC

Sometimes I think we are alone in the universe, and sometimes I think we are not. In either case the idea is quite staggering.

Thanks for the info guys, I'll see what happens, though I don't have a router, just a DSL modem and an ethernet LAN hub

In that case, it's going to be difficult to route any incming calls from the internet to the virtual BOINC server.

Are you sure it's a modem, not a router? If there's ethernet involved, routing would be more normal - even if the same box can double as a modem with a USB port. You mentioned that you can access internally on 192.168.x.x/test - that sounds very much like a router-managed LAN to me.

What's the output from IPCONFIG /ALL on your internet access machine? (may want to send by PM, rather than sanitising it all for posting here).

In that case, it's going to be difficult to route any incming calls from the internet to the virtual BOINC server.

Are you sure it's a modem, not a router? If there's ethernet involved, routing would be more normal - even if the same box can double as a modem with a USB port. You mentioned that you can access internally on 192.168.x.x/test - that sounds very much like a router-managed LAN to me.

What's the output from IPCONFIG /ALL on your internet access machine? (may want to send by PM, rather than sanitising it all for posting here).

Hi Richard,

Yet again you are right, my modem does have some routing capabilities

I believe I have set it up so I can access my 'BOINC Project' from the internet, will have to check this though.

On my modems internal configuration page, there is a connectivity check button, when I do a check it says my Default Gateway address is fine but cannot connect to DNS 1 or DNS 2 addresses, not sure if this is a problem as I can acces the internet fine.

If all goes well, I just have to learn how to program, think of a really interesting science problem, and then create my own BOINC project! - How hard can it be?

kinhull

---

Join TeamACC

Sometimes I think we are alone in the universe, and sometimes I think we are not. In either case the idea is quite staggering.

@ Robert Ribbeck

thanks for your PM:

this is NOT BOINC
15 Aug 2010 6:33:37 UTC
please go to the BOINC newsgroups
THIS IS SETI@Home not boinc
We have little to to tell you about how to run boinc as a project
THEY ARE NOT US

Yes I know SETI@Home is not BOINC, but it is the largest BOINC project, with the largest number of people with the computer skills

You may have little to tell me, but others may have more, certainly at the simple level I require at this stage.

I will be going to the BOINC newsgroups, as I have (thanks to those who replied with advice and info) gotten off first base with setting up a project.

---

Join TeamACC

Sometimes I think we are alone in the universe, and sometimes I think we are not. In either case the idea is quite staggering.

You could configure one of your machiens so that you can remote into it via something such as VNC. Then from that machine would could access your other machiens or VMs. Another option would require that your router let you configure some forwarding things. So you could come in on xxx.xxx.xxx.xxx:1234 and be forwarded to 192.168.1.1:31416.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[