<div class="gmail_quote">On Fri, Jan 2, 2009 at 11:53 AM, Brian Wood <span dir="ltr"><<a href="mailto:beww@beww.org">beww@beww.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">On Friday 02 January 2009 10:49:17 Greg Woods wrote:<br>> The more I read this thread, the more convinced I am that it would be<br>> easier to just set up a DHCP server. <br></div>I agree. DHCP is very simple to set up, and it won't cause any problems for<br>
machines that don't use it.<br>...I prefer running a "real" DHCP server as opposed to one in a router or access<br>point - The embedded ones are just too limited, for example you can't pass<br>a "next server" parameter with most router dhcp servers.<br>
</blockquote>
<div>For my myth / home network I don't have particularly complex needs - but I find my Linksys wireless router, running the DD-WRT software more than meets my needs. It can allocate static addresses, do NAT so I can redirect ports from the outside to my myth server, etc. I find the DD-WRT software very stable - and does everything I need it to. (The stock Linksys software is terrible though - you can't even allocate a static address using its DHCP). All this for less than $50, and no headaches.</div>
</div>