<div class="gmail_quote">On Sat, Aug 1, 2009 at 9:14 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 08/01/2009 09:04 PM, Jim Stichnoth wrote:<br></div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
coexist on the same network? I would prefer the home router to handle<br>
most DHCP requests and the Linux server to handle just the PXE-related<br>
requests for this frontend, so that e.g. my wife doesn't lose DHCP for<br>
her laptop computer when the Linux server is down.<br>
</blockquote>2. Can the DHCP service in a home router and a Linux DHCP/PXE server<br>
<br></div>
Having two DHCP servers on the same network is problematic, and most routers don't have enough bits exposed to set up things like pxe booting. There may be ways around it, but not any that I'm personally aware of.<div class="im">
<br></div></blockquote></div><br>For the DHCP server on the network, the best bet is if you can run a custom firmware on your router.. I run Tomato on mine, and it works great with the pxe configuration.<br><br>Prior to the router w/ tomato, I just ran dhcpcd on my myth server, and disabled it on the router. In a lot of cases that's more reliable than the stock firmware implementation on the router.<br>
<br>You really cannot run two dhcp servers on the same network... <b>bad </b>stuff happens.<br>