Harondel J. Sibble wrote: > That seems to be the problem, googling, list archives and wiki > entries gives me conflicting info on the boot process of the mvp.
Well we are dealing with a phase that happens under the control of Hauppauge firmware, of which there are two major versions, and the behaviors had to be reverse engineered. And then mvpmc code that runs after. >> cause is that the mvpmc is ignoring next-server and tftp-server-name > > I've seen comments about the MVP boot process explicitly ignoring the next- > server directive in the archives, I think by Tom or Martin, can't remember. My memory is fuzzy on the specifics, but consider that I looked into the matter only from the perspective of H3 hardware. At the time I had no D3 boxes. I was trying to understand how it worked, and see if we could reduce setup requirements. For example, with an H3 box, it discovers the media server via broadcast UDP packets, which are responded to by the relay service. So if we require users to run this relay service, why also have them custom configure DHCP to provide a next-server? It's redundant. Unless you have a D3 box, which doesn't use the relay service. If you're dealing with D3 boxes, I'd recommend ignoring the stuff I wrote in the archives, and focus on what Martin said. -Tom ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
