I was merely commenting about using one DHCP server - I dont have a specific answer about having more than one DHCP server. Presumably, if they are on separate LANs (or separate subnets), having two DHCP wouldn;t be a problem.
On Wed, 11 May 2005, Mark Knecht wrote: > Thanks for the response. I don't quite follow though. Help me a > bit. It sounds like we've set up similar networks. Please excuse the > text description but my ASCII art is worse: > > The first line is hard wired: > > Cable_Modem == Wireless router/switch == 3 machines + diskless frontends > > The next set is also hard wired: > > Wireless bridge == local switch == Myth-backend & diskless frontend Are these two networks interconnected? if so, where? The switch? > In my case I want the Myth backend server to be the network server > that all the diskless frontends get their kernels from, but the > wireless router/switch has the existing DHCP server. I don't think I > can have two DHCP servers on the network and expect things to work > correctly. If your Myth-frontends are on a separate subnet using the backend as a DHCP server this should work. Putting the frontends behind the backend on a separate NIC interface could work. You could then make the DHCP server on the backend server listen only on that NIC and supply the front-ends with IPs. I would probably make sure the DHCP blocks given out by the two DHCP servers do not collide (most routers allow you to specify how big the IP block that DHCP uses is). > The Gentoo diskless HOWTO would tell me to make the Myth-backend > machine the DHCP server. However it's not on all the time so my other > machines wouldn't have addresses when they need to. Aah, that would be a problem yes. I assumed the backend would be on all the time (it is a *server* after all?). > Can I make the Wireless router be the DHCP server (it will give the > diskless frontend machine addresses if they ask) and then still expect > the diskless frontends to get their kernels from the Myth-backend > machine? Another less complicated option would be to assign static IPs to the frontends that the backend knows about and work without DHCP. > I don't understand the Etherboot/PXE boot process. Does the DHCP > server HAVE to be the machine the diskless ones get their kernels > from? Im assuming this is so the backend server knows its clients' IPs. I dont know if there is a way around that - Im not an expert on MythTV. -- -- [email protected] mailing list
