<div class="gmail_quote">On Wed, Dec 2, 2009 at 1:05 PM, Thomas Rieff <span dir="ltr"><<a href="mailto:trieff@greencaremankato.com">trieff@greencaremankato.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 lang="EN-US">
<div>
<p class="MsoNormal"><span><b><font size="2" face="Arial" color="black"><span style="font-size: 10pt;">Are there any basic guidelines for assigning ip
address to various devices on the internal network???</span></font></b></span></p></div></div></blockquote><div>Here's what I do. It's a little complex and "wasteful" but that hardly matters on a private range.<br>
<br>I use 10.x.0.0/16 for my private networks, where x is usually 10 for my home network, and maybe a 20 for a "guest" wireless network if I have one configured.<br><br>Within <a href="http://10.10.0.0/16">10.10.0.0/16</a>, I use the 3rd octet as a sort of type designator.<br>
<br>Routers live at 10.10.254.x<br>Wireless APs get 10.10.253.x<br>Servers live at 10.10.240.x<br>Fixed-address workstations get 10.10.10.x<br>DHCP clients get 10.10.1.x<br><br>There are some other categories, but I forget them. Specifics are basically a matter of preference anyway, but the overall system has worked well for me.<br>
</div></div>