<br><br><div class="gmail_quote">On Tue, May 15, 2012 at 4:58 PM, Kris B. <span dir="ltr"><<a href="mailto:krisbee@krisbee.com" target="_blank">krisbee@krisbee.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On Tue, May 15, 2012, at 03:41 PM, Eric Sharkey wrote:<br>
> On Tue, May 15, 2012 at 3:34 PM, Joseph Fry <<a href="mailto:joe@thefrys.com">joe@thefrys.com</a>> wrote:<br>
> > One thing to note, there is no reason to run dhcpd. Simply assign the<br>
> > adapter an address in the 169.254.x.x range... the HDHR will randomly pick<br>
> > an address in that range if it fails to get one from DHCP<br>
><br>
> If you're running dhcp, then the HDHR will boot faster, since it<br>
> doesn't have to wait for DHCP to fail.<br>
><br>
> That may not be a big reason, but it is a reason.<br>
><br>
> Eric<br>
> _______________________________________________<br>
<br>
</div>And oddly enough on mine, when I assigned it a static ip, about every<br>
three days it would just stop communicating unless I restarted it. Very<br>
inconvenient, and you never knew when it would stop communicating.<br>
<span class="HOEnZb"><font color="#888888"></font></span><br></blockquote></div><br>I am not suggesting that you assign an IP to the HDHR at all... statically or using DHCP. If the HDHR doesn't get a DHCP response, it will pick a random IP in the 169.254.x.x range (read up on Link Local addresses here: <a href="http://en.wikipedia.org/wiki/Link-local_address">http://en.wikipedia.org/wiki/Link-local_address</a>) This is true of most network devices today to conform with zero configuration networking (<a href="http://en.wikipedia.org/wiki/Zero_configuration_networking">http://en.wikipedia.org/wiki/Zero_configuration_networking</a>).<br>
<br>The advantages of doing this are several:<br>1. <u>no</u> configuration of the HDHR... <u>at all</u>... just plug it in<br>2. you may not need to do any configuration on the server either... depends upon your distro.<br>
2. no requirement that the server be on before the HDHR... it doesn't care, it's not using DHCP.<br>3. no need to worry about your server being connected to your LAN accidentally and issuing IP's to the rest of the network (done that before when I confused cables in rats nest on and a test lab dhcp server started issuing addresses to a~1000 node production LAN... not pretty)<br>
<br>The only disadvantage, as Eric stated, is it will take a minute or so longer after powering on the HDHR before it is addressable, however I never turn mine off... so that's what,a minute every few months?<br><br>
<br>