123bob
11-01-2007, 08:08 PM
I'm trying to use Boincview on the farm now. All the computers are fully contained on the LAN side of a Linksys router, on the home network. All devices are peers on this network, with a 48 port HP switch handling the amount of ports needed
I had tried to setup Boincview using the computer name of the managing computer, "el-machino-2". This was typed into the "remote_hosts.cfg" file per the instructions. The client machine could not resolve the hostname. Not surprising since there is no DNS server for it. I manually typed in the IP of the host machine and it found it OK. On the Boincview host side, I manually typed in all the IPs of the client machines since it also couldn't resolve the client computer names.
Everything was just peachy, with Boincview displaying the status of the entire farm on one screen. Cool. I was feeling pretty geeky until we had a power fail this afternoon. :mad: Well, guess what, when the power came back on, Boincview could no longer find the clients since they all got reassigned new addresses from the DHCP server on the router. I knew this was a risk in my setup. Now I gotta fix it.
The first option I can come up with is to kill DHCP and assign static IP addys to the entire LAN. Bummer since this presents the maintenance associated with it.
What I'd really like to do is to make the router serve as the DNS. It knows all the machine names and what dynamic IP it assigned, so it should be able to do it right? Not! My old linksys has some feature called Dynamic DNS which requires you to open an account on some DNS outfit on the WAN side of things. I don't think that would be ideal. I do not anticipate needing access to my farm from the WAN side. Or, am I being short-sighted? What are the security risks of doing this?
How do you guys handle this? Is there a router available that can do DNS? A program on the host PC? Or do you just use static IP?
Thanks for the help. Boincview is really cool, and I could get used to it real fast if I can overcome this setup issue.
Regards,
Bob
I had tried to setup Boincview using the computer name of the managing computer, "el-machino-2". This was typed into the "remote_hosts.cfg" file per the instructions. The client machine could not resolve the hostname. Not surprising since there is no DNS server for it. I manually typed in the IP of the host machine and it found it OK. On the Boincview host side, I manually typed in all the IPs of the client machines since it also couldn't resolve the client computer names.
Everything was just peachy, with Boincview displaying the status of the entire farm on one screen. Cool. I was feeling pretty geeky until we had a power fail this afternoon. :mad: Well, guess what, when the power came back on, Boincview could no longer find the clients since they all got reassigned new addresses from the DHCP server on the router. I knew this was a risk in my setup. Now I gotta fix it.
The first option I can come up with is to kill DHCP and assign static IP addys to the entire LAN. Bummer since this presents the maintenance associated with it.
What I'd really like to do is to make the router serve as the DNS. It knows all the machine names and what dynamic IP it assigned, so it should be able to do it right? Not! My old linksys has some feature called Dynamic DNS which requires you to open an account on some DNS outfit on the WAN side of things. I don't think that would be ideal. I do not anticipate needing access to my farm from the WAN side. Or, am I being short-sighted? What are the security risks of doing this?
How do you guys handle this? Is there a router available that can do DNS? A program on the host PC? Or do you just use static IP?
Thanks for the help. Boincview is really cool, and I could get used to it real fast if I can overcome this setup issue.
Regards,
Bob