<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">>>The slowest thing about resuming I find to be waiting for the DHCP server to do its stuff and finish the eth0 connection, takes<br>
about 2 seconds to resume and 10 seconds to get the eth0 connection again. I suppose using a static IP would speed that<br>
up....however I moved away from statics a long time ago....<br>
<br>
>Why not use static? DHCP makes sense if a machine is going to move from network to network<br>
<br>
</div>Agreed not the case here. I'll put it on the todo list, I will be interested to test what I've suggested however the benefit is<br>
only 10 seconds so other things will happen first.<br>
<div class="im"><br>
>or if you've got so many machines that keeping track of all the ips is a problem.<br>
<br>
</div>How many would one consider to be the threshold here? 20? 30? 50?<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br></div><div>A bit OT but does anyone else use Avahi / mDNS for automatic name resolution on their network? Then everything on the network is [hostname].local regardless of dynamic or static addressing. Since I also have Apple gear in the house it makes a lot of sense for me.</div>
<div><br></div><div><br></div><div><br></div></div>