bungle wrote: > Both the router and the computer are set to give the MVP the same > address. If that's all it needs when it renews the lease, then I > don't know why it wouldn't work with either one.
If that's true, then why did you bother to set up a DHCP server? Because the wiki says to do so, right? The theory is that the mvpmc code is dependent on the "next-server" (siaddr) field being supplied via DHCP to determine the IP address of the server to TFTP the startup script (config file) from. My thought was that this is an unnecessary dependency, and in the thread "host used to download the config file" from last April on the developer list I argued mvpmc should be tweaked to eliminate it, getting rid of the requirement to run a custom configured DHCP server. But it was pointed out that this wouldn't work on older (pre-Flash) MVP hardware. I'm pretty sure it could be made to work using a bit of custom code to issue broadcast packets to find the TFTP server or the relay server. Of course this takes coding and testing effort. I think one of the priorities for the mvpmc project at this point should be refining the packaging of the code to eliminate as many dependencies and configuration steps. The problem is that there isn't a high motivation to fix these deficiencies, as anyone who is in a position to fix them (like myself) has already expended the effort on this setup, and has little to gain from simplifying it. The big question is whether mvpmc will last long enough to warrant these refinements, or whether the user base will start migrating to more capable hardware. > When doing a soft power on, it gives the status screen and a progress bar > and a bunch of tasks flash on the screen. Does anyone know what the first > task shown is? I haven't looked at the mvpmc code in that area, so I don't know. > Tom Metro wrote: >> But you should be able to telnet to it while mvpmc is still >> "powered down" ... > > Nope - it doesn't respond. I tried this morning and couldn't telnet > to it. The backend was up and I started DHCP and powered on the MVP > and got the crazy loop. I think perhaps this is unrelated to DHCP > and maybe something is timing out overnight. Your inability to telnet to the MVP seems to point even more so to a DHCP lease expiration problem. (I presume the MVP otherwise is responding to your input and not crashed. You say it tried to power up...) That you've started up the DHCP server prior to starting up mvpmc may not help, as that startup process doesn't trigger a DHCP request. The request would have happened back when the lease expired - overnight when the server was off. I'm not sure how often the DHCP client in mvpmc tries to refresh a lease that has failed to renew. It may be rather slow, like once an hour. -Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
